Quantcast
Channel: Shaw forum - dslreports.com
Viewing all articles
Browse latest Browse all 870

having some problems

0
0
ok so i decided to ping google a second ago when i was gonna do a little test on my connection. noticed it was taking over 100ms or around that. thought it was odd. so i pinged my default gateway (cmts) and response times were fine ping 174.7.244.1 -t Pinging 174.7.244.1 with 32 bytes of data: Reply from 174.7.244.1: bytes=32 time=7ms TTL=254 Reply from 174.7.244.1: bytes=32 time=7ms TTL=254 Reply from 174.7.244.1: bytes=32 time=8ms TTL=254 Reply from 174.7.244.1: bytes=32 time=8ms TTL=254 Reply from 174.7.244.1: bytes=32 time=7ms TTL=254 Reply from 174.7.244.1: bytes=32 time=9ms TTL=254 Reply from 174.7.244.1: bytes=32 time=7ms TTL=254 Ping statistics for 174.7.244.1: Packets: Sent = 7, Received = 7, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 9ms, Average = 7ms ping google.com -t Pinging google.com [173.194.33.0] with 32 bytes of data: Reply from 173.194.33.0: bytes=32 time=50ms TTL=56 Reply from 173.194.33.0: bytes=32 time=121ms TTL=55 Reply from 173.194.33.0: bytes=32 time=116ms TTL=55 Reply from 173.194.33.0: bytes=32 time=123ms TTL=55 Reply from 173.194.33.0: bytes=32 time=63ms TTL=56 Reply from 173.194.33.0: bytes=32 time=120ms TTL=55 Reply from 173.194.33.0: bytes=32 time=52ms TTL=56 Reply from 173.194.33.0: bytes=32 time=53ms TTL=56 Reply from 173.194.33.0: bytes=32 time=49ms TTL=56 Reply from 173.194.33.0: bytes=32 time=111ms TTL=55 Reply from 173.194.33.0: bytes=32 time=56ms TTL=56 Ping statistics for 173.194.33.0: Packets: Sent = 11, Received = 11, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 123ms, Average = 83ms ping google.com -t Pinging google.com [173.194.33.0] with 32 bytes of data: Reply from 173.194.33.0: bytes=32 time=153ms TTL=55 Reply from 173.194.33.0: bytes=32 time=150ms TTL=55 Reply from 173.194.33.0: bytes=32 time=75ms TTL=56 Reply from 173.194.33.0: bytes=32 time=151ms TTL=55 Reply from 173.194.33.0: bytes=32 time=65ms TTL=56 Reply from 173.194.33.0: bytes=32 time=63ms TTL=56 Reply from 173.194.33.0: bytes=32 time=71ms TTL=56 Reply from 173.194.33.0: bytes=32 time=152ms TTL=55 Reply from 173.194.33.0: bytes=32 time=65ms TTL=56 Ping statistics for 173.194.33.0: Packets: Sent = 9, Received = 9, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 63ms, Maximum = 153ms, Average = 105ms ping google.com -t Pinging google.com [173.194.33.6] with 32 bytes of data: Reply from 173.194.33.6: bytes=32 time=55ms TTL=56 Reply from 173.194.33.6: bytes=32 time=138ms TTL=55 Reply from 173.194.33.6: bytes=32 time=59ms TTL=56 Reply from 173.194.33.6: bytes=32 time=140ms TTL=55 Reply from 173.194.33.6: bytes=32 time=146ms TTL=55 Reply from 173.194.33.6: bytes=32 time=82ms TTL=56 Reply from 173.194.33.6: bytes=32 time=76ms TTL=56 Reply from 173.194.33.6: bytes=32 time=138ms TTL=55 Reply from 173.194.33.6: bytes=32 time=70ms TTL=56 Reply from 173.194.33.6: bytes=32 time=144ms TTL=55 Reply from 173.194.33.6: bytes=32 time=72ms TTL=56 Reply from 173.194.33.6: bytes=32 time=75ms TTL=56 Reply from 173.194.33.6: bytes=32 time=151ms TTL=55 Ping statistics for 173.194.33.6: Packets: Sent = 13, Received = 13, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 55ms, Maximum = 151ms, Average = 103ms Control-C so i ran a traceroute, and immediately i noticed the problem was within shaws network. the hop that goes from vancouver to washington, is having issues or is massively congested. tracert google.com Tracing route to google.com [173.194.33.6] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 * * * Request timed out. 3 10 ms 23 ms 11 ms rd3bb-tge0-8-0-0-7.vc.shawcable.net [64.59.156.2 43] 4 19 ms 19 ms 13 ms 66.163.68.250 5 16 ms 11 ms 11 ms 66.163.65.150 6 98 ms 98 ms 96 ms rc6wt-pos0-8-1-0.wa.shawcable.net [66.163.76.130 ] 7 44 ms 42 ms 42 ms 72.14.216.66 8 134 ms 126 ms 127 ms 209.85.249.32 9 60 ms 56 ms 58 ms 209.85.253.24 10 64 ms 60 ms 60 ms sea09s01-in-f6.1e100.net [173.194.33.6] Trace complete. then i tested to a gameserver that i know is in california to make sure it wasnt just only some of my westcoast traffic having this issue... tracert 108.61.235.105 Tracing route to 108.61.235.105.choopa.net [108.61.235.105] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 * * * Request timed out. 3 12 ms 11 ms 12 ms rd3bb-tge0-8-0-0-7.vc.shawcable.net [64.59.156.2 43] 4 12 ms 17 ms 10 ms 66.163.65.174 5 21 ms 11 ms 11 ms rc2wh-tge0-6-0-10.vc.shawcable.net [66.163.69.18 2] 6 99 ms 96 ms 94 ms rc6wt-pos0-8-1-0.wa.shawcable.net [66.163.76.130 ] 7 150 ms 150 ms 142 ms rc5wt-tge0-10-0-14.wa.shawcable.net [66.163.68.8 1] 8 118 ms 126 ms 126 ms sea-b1-link.telia.net [62.115.12.73] 9 118 ms 114 ms 115 ms level3-ic-304311-sea-b1.c.telia.net [62.115.37.1 18] 10 69 ms 76 ms 76 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150] 11 81 ms 81 ms 82 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49] 12 109 ms 105 ms 101 ms ae-92-92.csw4.SanJose1.Level3.net [4.69.153.30] 13 * 109 ms 109 ms ae-4-90.edge8.SanJose1.Level3.net [4.69.152.212] 14 75 ms 78 ms 79 ms CHOOPA-LLC.edge8.SanJose1.Level3.net [4.30.150.8 6] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 71 ms 72 ms 81 ms 108.61.235.105.choopa.net [108.61.235.105] Trace complete. for comparison this is what that connection should look like/ looked like the other day tracert 108.61.235.105 Tracing route to 108.61.235.105.choopa.net [108.61.235.105] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 * * * Request timed out. 3 10 ms 15 ms 15 ms rd3bb-tge0-8-0-0-7.vc.shawcable.net [64.59.156.2 43] 4 19 ms 13 ms 21 ms rc2bb-tge0-5-0-2.vc.shawcable.net [66.163.68.201 ] 5 17 ms 19 ms 19 ms rc5wt-pos0-1-1-0.wa.shawcable.net [66.163.76.142 ] 6 15 ms 17 ms 15 ms sea-b1-link.telia.net [62.115.12.73] 7 15 ms 17 ms 15 ms level3-ic-304311-sea-b1.c.telia.net [62.115.37.1 18] 8 31 ms 33 ms 33 ms ae-31-51.ebr1.Seattle1.Level3.net [4.69.147.150] 9 41 ms 37 ms 37 ms ae-7-7.ebr2.SanJose1.Level3.net [4.69.132.49] 10 34 ms 32 ms 33 ms ae-92-92.csw4.SanJose1.Level3.net [4.69.153.30] 11 40 ms 69 ms 32 ms ae-4-90.edge8.SanJose1.Level3.net [4.69.152.212] 12 36 ms 32 ms 33 ms CHOOPA-LLC.edge8.SanJose1.Level3.net [4.30.150.8 6] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 34 ms 34 ms 38 ms 108.61.235.105.choopa.net [108.61.235.105] Trace complete.

Viewing all articles
Browse latest Browse all 870

Latest Images

Trending Articles





Latest Images