Higher ping in close areas

supernoms

Honorable
Nov 22, 2013
2
0
10,510
Hi, im having an issue in whihc my ping times to servers close to me are high, about 30-40 ms higher than they use to be. I was wondering if anyone could hlep me understand why.

Below is multiple tracerts to a northen california server in which i use to get 40 ms to, i now get around 90. I live in Kitimat B.C. using city west internet.






Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Austen>tracert 8.17.250.40 -t

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.

C:\Users\Austen>tracert 8.17.250.40

Tracing route to host.colocrossing.com [8.17.250.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 7 ms conn1-69-176-173.citywest.ca [69.176.173.1]
3 11 ms 11 ms 19 ms 177.65.244.24.scpe.citywest.ca [24.244.65.177]
4 15 ms 15 ms 11 ms 1.65.244.24.scpe.citywest.ca [24.244.65.1]
5 19 ms 18 ms 19 ms 205.250.84.210
6 84 ms 83 ms 87 ms VCTABC01DR01.bb.telus.com [154.11.10.114]
7 80 ms 80 ms 98 ms as18779-egihosting.any2ix.coresite.com [206.223.
143.169]
8 76 ms 78 ms 80 ms 173.245.71.178
9 76 ms 83 ms 78 ms host.colocrossing.com [8.17.250.40]

Trace complete.

C:\Users\Austen>tracert 8.17.250.40

Tracing route to host.colocrossing.com [8.17.250.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 11 ms conn1-69-176-173.citywest.ca [69.176.173.1]
3 15 ms 12 ms 12 ms 177.65.244.24.scpe.citywest.ca [24.244.65.177]
4 10 ms 11 ms 20 ms 1.65.244.24.scpe.citywest.ca [24.244.65.1]
5 656 ms 594 ms 500 ms 205.250.84.210
6 85 ms 87 ms 84 ms VCTABC01DR01.bb.telus.com [154.11.10.114]
7 82 ms 83 ms 74 ms as18779-egihosting.any2ix.coresite.com [206.223.
143.169]
8 81 ms 79 ms 78 ms 173.245.71.178
9 79 ms 79 ms 83 ms host.colocrossing.com [8.17.250.40]

Trace complete.

C:\Users\Austen>tracert 8.17.250.40

Tracing route to host.colocrossing.com [8.17.250.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 10 ms 11 ms conn1-69-176-173.citywest.ca [69.176.173.1]
3 12 ms 12 ms 9 ms 177.65.244.24.scpe.citywest.ca [24.244.65.177]
4 13 ms 9 ms 12 ms 1.65.244.24.scpe.citywest.ca [24.244.65.1]
5 18 ms 18 ms 20 ms 205.250.84.210
6 85 ms 83 ms 83 ms VCTABC01DR01.bb.telus.com [154.11.10.114]
7 80 ms 79 ms 88 ms as18779-egihosting.any2ix.coresite.com [206.223.
143.169]
8 77 ms 80 ms 78 ms 173.245.71.178
9 88 ms 78 ms 80 ms host.colocrossing.com [8.17.250.40]

Trace complete.

C:\Users\Austen>

C:\Users\Austen>
 
Solution
There really is not much wrong in this trace. There is a increase in the latency between hop 5 and hop 6. Everything past hop 6 appears to be at the destination location since the latency is similar and everything before hop 5 is someplace pretty close to your house.

If your complaint is that it should not take a extra 60ms in that hop its hard to say, you would have to know the actual locations of the routers in hop 5 and hop 6. Even if you would there is nothing you can do. This is completely within telus network. Neither you or the far end server owner buy service directly from telus so they will not even talk to you.. If anyone has any agreement with them it would be your ISP.

There really is not much wrong in this trace. There is a increase in the latency between hop 5 and hop 6. Everything past hop 6 appears to be at the destination location since the latency is similar and everything before hop 5 is someplace pretty close to your house.

If your complaint is that it should not take a extra 60ms in that hop its hard to say, you would have to know the actual locations of the routers in hop 5 and hop 6. Even if you would there is nothing you can do. This is completely within telus network. Neither you or the far end server owner buy service directly from telus so they will not even talk to you.. If anyone has any agreement with them it would be your ISP.

 
Solution