O Canada! > Canadian > TekSavvy > Pings ranging between 500-800

Pings ranging between 500-800

Hello Raptor,

Could you post your pings here and a set of trace routes as well?

reply to raptor235
Aye, I'm from North Bay, (4 hours north of Toronto) I just switched from Bell because Teksavvy is a much better deal, I was having that issue with Bell and seeing as Teksavvy uses Bells infrastructure, I'm now having the same issue with Teksavvy.

Tracing route to google.ca [74.125.226.95]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.Home [192.168.1.1]
2 681 ms 487 ms 448 ms 206.248.154.104
3 405 ms 362 ms 360 ms 2120.ae0.bdr01.tor.packetflow.ca [69.196.136.66]

4 340 ms 354 ms 357 ms gw-google.torontointernetxchange.net [206.108.34
.6]
5 427 ms 389 ms 404 ms 216.239.47.114
6 474 ms 509 ms 599 ms 64.233.175.98
7 467 ms 380 ms 327 ms yyz06s07-in-f31.1e100.net [74.125.226.95]

Trace complete.

Usually happens between 6-11 at night, but it's the holidays and everybody is online so my latency has been horrible all day.

I'm not getting anywhere with tech support, they all keep telling me they've never seen that issue, even though the forums are full of people saying the same thing.

Internet sucks in canada.

Justin, the OP is on Cable, while you're on DSL. Your issue has nothing to do with his.
--
Battle.net Tech Support MVP

reply to raptor235
raptor, what POI you on?

I've been having issues on York Mills since I got my cable installed in mid December. Rogers is doing everything it can to do nothing at all. Every ticket has been thrown back blaming 'customer equipment,' 'peak hours' or such. I think all they've done is look at the power levels on your modem (and, like yours, is fine) and close the ticket. For me, there is connectivity and speed but my latency is around 1000ms with packet loss.

Good luck.

Also on York Mills, but without problems.

Post tracerts?
--
Battle.net Tech Support MVP

Here's the WIERDEST part. Latency is fine when I INITIALLY connect to the cable modem (eg. modem power cycle, ethernet port swap). A minute later... WHAM.

Believe me... I'm not editing these... I've done enough over the last half month!

PING www.google.com (74.125.226.16): 56 data bytes
64 bytes from 74.125.226.16: icmp_seq=0 ttl=56 time=11.522 ms
64 bytes from 74.125.226.16: icmp_seq=1 ttl=56 time=9.009 ms
64 bytes from 74.125.226.16: icmp_seq=2 ttl=56 time=9.365 ms
64 bytes from 74.125.226.16: icmp_seq=3 ttl=56 time=9.266 ms
64 bytes from 74.125.226.16: icmp_seq=4 ttl=56 time=10.925 ms
64 bytes from 74.125.226.16: icmp_seq=5 ttl=56 time=9.376 ms
64 bytes from 74.125.226.16: icmp_seq=6 ttl=56 time=11.425 ms
64 bytes from 74.125.226.16: icmp_seq=7 ttl=56 time=9.440 ms
64 bytes from 74.125.226.16: icmp_seq=8 ttl=56 time=9.226 ms
64 bytes from 74.125.226.16: icmp_seq=9 ttl=56 time=8.946 ms
64 bytes from 74.125.226.16: icmp_seq=10 ttl=56 time=9.396 ms
64 bytes from 74.125.226.16: icmp_seq=11 ttl=56 time=9.345 ms
64 bytes from 74.125.226.16: icmp_seq=12 ttl=56 time=9.725 ms
64 bytes from 74.125.226.16: icmp_seq=13 ttl=56 time=9.535 ms
64 bytes from 74.125.226.16: icmp_seq=14 ttl=56 time=10.493 ms
64 bytes from 74.125.226.16: icmp_seq=15 ttl=56 time=9.469 ms
64 bytes from 74.125.226.16: icmp_seq=16 ttl=56 time=10.254 ms
64 bytes from 74.125.226.16: icmp_seq=17 ttl=56 time=10.054 ms
64 bytes from 74.125.226.16: icmp_seq=18 ttl=56 time=9.299 ms
64 bytes from 74.125.226.16: icmp_seq=19 ttl=56 time=9.489 ms
64 bytes from 74.125.226.16: icmp_seq=20 ttl=56 time=9.888 ms
64 bytes from 74.125.226.16: icmp_seq=21 ttl=56 time=9.785 ms
64 bytes from 74.125.226.16: icmp_seq=22 ttl=56 time=9.838 ms
64 bytes from 74.125.226.16: icmp_seq=23 ttl=56 time=13.941 ms
64 bytes from 74.125.226.16: icmp_seq=24 ttl=56 time=10.185 ms
64 bytes from 74.125.226.16: icmp_seq=25 ttl=56 time=10.525 ms
64 bytes from 74.125.226.16: icmp_seq=26 ttl=56 time=12.814 ms
64 bytes from 74.125.226.16: icmp_seq=27 ttl=56 time=705.236 ms
64 bytes from 74.125.226.16: icmp_seq=28 ttl=56 time=911.080 ms
64 bytes from 74.125.226.16: icmp_seq=29 ttl=56 time=644.054 ms
64 bytes from 74.125.226.16: icmp_seq=30 ttl=56 time=169.697 ms
64 bytes from 74.125.226.16: icmp_seq=31 ttl=56 time=637.436 ms
64 bytes from 74.125.226.16: icmp_seq=32 ttl=56 time=647.874 ms
64 bytes from 74.125.226.16: icmp_seq=33 ttl=56 time=681.850 ms
64 bytes from 74.125.226.16: icmp_seq=34 ttl=56 time=713.673 ms
64 bytes from 74.125.226.16: icmp_seq=35 ttl=56 time=751.983 ms
64 bytes from 74.125.226.16: icmp_seq=36 ttl=56 time=761.326 ms
64 bytes from 74.125.226.16: icmp_seq=37 ttl=56 time=794.917 ms
64 bytes from 74.125.226.16: icmp_seq=38 ttl=56 time=829.672 ms
64 bytes from 74.125.226.16: icmp_seq=39 ttl=56 time=864.096 ms
64 bytes from 74.125.226.16: icmp_seq=40 ttl=56 time=856.332 ms
64 bytes from 74.125.226.16: icmp_seq=41 ttl=56 time=918.251 ms
64 bytes from 74.125.226.16: icmp_seq=42 ttl=56 time=913.008 ms
64 bytes from 74.125.226.16: icmp_seq=43 ttl=56 time=950.125 ms
64 bytes from 74.125.226.16: icmp_seq=44 ttl=56 time=996.852 ms
64 bytes from 74.125.226.16: icmp_seq=45 ttl=56 time=982.825 ms
Request timeout for icmp_seq 46
64 bytes from 74.125.226.16: icmp_seq=46 ttl=56 time=1031.871 ms
64 bytes from 74.125.226.16: icmp_seq=47 ttl=56 time=1031.070 ms
64 bytes from 74.125.226.16: icmp_seq=48 ttl=56 time=1079.891 ms
64 bytes from 74.125.226.16: icmp_seq=49 ttl=56 time=1045.198 ms
64 bytes from 74.125.226.16: icmp_seq=50 ttl=56 time=1083.931 ms
64 bytes from 74.125.226.16: icmp_seq=51 ttl=56 time=1121.814 ms
64 bytes from 74.125.226.16: icmp_seq=52 ttl=56 time=1115.559 ms
^C
--- www.google.com ping statistics ---
54 packets transmitted, 53 packets received, 1.9% packet loss
round-trip min/avg/max/stddev = 8.946/424.758/1121.814/446.384 ms

Cable on Teksavvy, no router:
traceroute: Warning: www.google.com has multiple addresses; using 74.125.226.18
traceroute to www.google.com (74.125.226.18), 64 hops max, 52 byte packets
1 10.126.7.129 (10.126.7.129) 505.335 ms 489.830 ms 530.137 ms
2 69.63.243.229 (69.63.243.229) 529.522 ms 546.423 ms 575.607 ms
3 yorkmills3.cable.teksavvy.com (24.52.255.14) 622.155 ms
yorkmills2.cable.teksavvy.com (24.52.255.10) 653.371 ms 295.564 ms
4 yorkmills2.cable.teksavvy.com (24.52.255.9) 344.709 ms 334.310 ms 345.483 ms
5 72.14.212.134 (72.14.212.134) 415.916 ms 444.776 ms 479.002 ms
6 216.239.47.114 (216.239.47.114) 459.692 ms 502.909 ms 529.906 ms
7 72.14.233.142 (72.14.233.142) 574.234 ms 596.184 ms 598.672 ms
8 yyz06s05-in-f18.1e100.net (74.125.226.18) 645.090 ms 687.890 ms 707.560 ms

Either you have an issue with your line into your home, or your local node is massively congested - this means everyone in your neighbourhood (whether on Start, Acanac, Rogers or Teksavvy cable) will be experiencing this problem.

Or your system is doing some heavy downloading you're not aware of (ie malware).
--
Battle.net Tech Support MVP

Exactly. But of course, Rogers won't be telling me who's on my node and how congested it is. Certainly the York Mills POI is fairly loaded but my level of service is ridiculous.

My modem levels are fine, which is why Rogers says "hmm.. looks fine on our end!"


Status Code: Operational
Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1

Cable Signal Details
Forward Path:
Channel Frequency Power SNR BER Modulation
1 591.0 MHz 1.7 dBmV 41.6 dB 0.000 % 256 QAM
2 597.0 MHz 1.8 dBmV 42.0 dB 0.000 % 256 QAM
3 603.0 MHz 2.0 dBmV 41.9 dB 0.000 % 256 QAM
4 609.0 MHz 1.6 dBmV 42.4 dB 0.000 % 256 QAM
5 615.0 MHz 2.0 dBmV 42.4 dB 0.000 % 256 QAM
6 621.0 MHz 1.4 dBmV 42.2 dB 0.000 % 256 QAM
7 633.0 MHz 1.4 dBmV 42.5 dB 0.000 % 256 QAM
8 639.0 MHz 1.0 dBmV 41.7 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
5 31.3 MHz 36.3 dBmV 64 QAM
6 25.3 MHz 36.3 dBmV 64 QAM
7 22.1 MHz 36.3 dBmV 64 QAM
8 38.6 MHz 37.8 dBmV 64 QAM


I still have 5mb service with Bell DSL, and my pings are acceptable there. The little ping spike is me clicking on a page on DSLR.


PING www.google.com (74.125.226.16): 56 data bytes
64 bytes from 74.125.226.16: icmp_seq=0 ttl=55 time=14.185 ms
64 bytes from 74.125.226.16: icmp_seq=1 ttl=55 time=13.199 ms
64 bytes from 74.125.226.16: icmp_seq=2 ttl=55 time=13.293 ms
64 bytes from 74.125.226.16: icmp_seq=3 ttl=55 time=14.320 ms
64 bytes from 74.125.226.16: icmp_seq=4 ttl=55 time=12.834 ms
64 bytes from 74.125.226.16: icmp_seq=5 ttl=55 time=13.240 ms
64 bytes from 74.125.226.16: icmp_seq=6 ttl=55 time=13.889 ms
64 bytes from 74.125.226.16: icmp_seq=7 ttl=55 time=15.604 ms
64 bytes from 74.125.226.16: icmp_seq=8 ttl=55 time=12.705 ms
64 bytes from 74.125.226.16: icmp_seq=9 ttl=55 time=14.325 ms
64 bytes from 74.125.226.16: icmp_seq=10 ttl=55 time=15.866 ms
64 bytes from 74.125.226.16: icmp_seq=11 ttl=55 time=13.062 ms
64 bytes from 74.125.226.16: icmp_seq=12 ttl=55 time=250.836 ms
64 bytes from 74.125.226.16: icmp_seq=13 ttl=55 time=116.862 ms
64 bytes from 74.125.226.16: icmp_seq=14 ttl=55 time=77.981 ms
64 bytes from 74.125.226.16: icmp_seq=15 ttl=55 time=257.749 ms
64 bytes from 74.125.226.16: icmp_seq=16 ttl=55 time=58.445 ms
64 bytes from 74.125.226.16: icmp_seq=17 ttl=55 time=13.518 ms
64 bytes from 74.125.226.16: icmp_seq=18 ttl=55 time=104.876 ms
64 bytes from 74.125.226.16: icmp_seq=19 ttl=55 time=13.878 ms
^C
--- www.google.com ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.705/53.033/257.749/74.146 ms


Videonerd: Those poor pings should also see slower speeds (so do a bunch of speedtest.net speed & ping tests), which you can take to Teksavvy to get Rogers to do something about. You can link an entire history, like this:
»www.speedtest.net/results.php?sh···80704354

As for who's on your local node... That'd be your entire neighbourhood.. Probably 1 or 2 streets over from the node itself.

York Mills itself seems fine right now. Frankly, the only time I've had latency issues on York Mills in the last month was last night while my hubby was getting some DLC for the PS3 game he just bought. The QoS I have currently set up for the PS3 is higher than my computer's because I was tired of his complaining of latency while gaming from me uploading pictures & video.
--
Battle.net Tech Support MVP