Hi, it's a sat night where i am and while i've noticed that ping times usually escalate on the weekends, these ping times have been particularly bad lately. I've run a traceroute to google with results shown below:
Tracing route to Ihrl4s21-in-f4.1e100.net [173.194.34.132] •ver a maximum of 30 hops:
1 17 ms 3 ms 2 ms 192.168.0.1
2 * * Request timed out.
3 126 ms 49 ms 12 ms 64.59.147.209
4 524 ms 384 ms 271 ms rc2bb-tge0-2-2-0.vc.shawcable net [66.163.69.13'
5 450 ms 383 ms 611 ms 66.163.68.150
6 630 ms 1028 ms 1500 ms 66.163.78.62
7 967 ms 1209 ms 921 ms 72.14.216.66
8 41 ms 46 ms 154 ms 209.85.249.32
9 512 ms 694 ms 1042 ms 66.249.94.195
10 360 ms 509 ms 376 ms 216.239.46.156
11 408 ms 561 ms 72.14.239.48
12 931 ms 1217 ms 1009 ms 209.85.241.23
13 70 ms 96 ms 73 ms 72.14.237.131
14 362 ms 105 ms 119 ms 209.85.248.222
15 165 ms 487 ms 216.239.46.225
16 426 ms 698 ms 706 ms 209.85.253.115
17 675 ms 1016 ms * Ihrl4s21-in-f4.1e100.net [173.194.34.132]
18 788 ms 547 ms 536 ms Ihrl4s21-in-f4.1e100.net [173.194.34.132]
Trace complete.
If anybody can interpret this data perhaps tell me if something's wrong that'd be helpful thanks. If possible i would like to be able to improve my connection speeds as i do game and ping this bad usually means no game time. And it happens every weekend. =(
Particularly bad ping times
The first line is on your home network. The time is short. No problem.
Lines 3 is to the first router that you see within the shawcable network. Again the time (12ms) is short enough to suggest that there is a problem with yur connection to shawcable.
The next 3 lines are all within the shawcable network. And the times are longer than they should be. That suggest that either Shaw is under a DoS attack, or that their backbone network is underpowered for the load it has to carry.
Lines 3 is to the first router that you see within the shawcable network. Again the time (12ms) is short enough to suggest that there is a problem with yur connection to shawcable.
The next 3 lines are all within the shawcable network. And the times are longer than they should be. That suggest that either Shaw is under a DoS attack, or that their backbone network is underpowered for the load it has to carry.
thanks!
Hah alright. As long as there's no problem with my network internally i can just blame shaw. It's sunday morning now and suddenly everything is fine again with <50ms ping. I guess my people in my neighbourhood have a thing for playing on a sat night( i can't blame them really) and shaw needs to do better.nwrickert wrote:The first line is on your home network. The time is short. No problem.
Lines 3 is to the first router that you see within the shawcable network. Again the time (12ms) is short enough to suggest that there is a problem with yur connection to shawcable.
The next 3 lines are all within the shawcable network. And the times are longer than they should be. That suggest that either Shaw is under a DoS attack, or that their backbone network is underpowered for the load it has to carry.
Thanks for the input!
(edit)*rep added