Quantcast
Channel: CenturyLink forum - dslreports.com
Viewing all articles
Browse latest Browse all 4880

[CenturyTel] Large packetloss/slow speed routing through cogent/youtube servers

$
0
0
I am having multiple issues with accessing sites that get routed through the cogent network. Pinging ophion.feralhosting.com [185.21.217.8] with 32 bytes of data: Reply from 185.21.217.8: bytes=32 time=181ms TTL=51 Reply from 185.21.217.8: bytes=32 time=181ms TTL=51 Reply from 185.21.217.8: bytes=32 time=181ms TTL=51 Reply from 185.21.217.8: bytes=32 time=182ms TTL=51 Ping statistics for 185.21.217.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 181ms, Maximum = 182ms, Average = 181ms tracert ophion.feralhosting.com Tracing route to ophion.feralhosting.com [185.21.217.8] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 21 ms 21 ms 21 ms hlrn-dsl-gw08.hlrn.qwest.net [207.225.112.8] 3 21 ms 21 ms 23 ms hlrn-agw1.inet.qwest.net [71.217.188.57] 4 * * * Request timed out. 5 55 ms 55 ms 55 ms te0-4-0-35.ccr23.lax05.atlas.cogentco.com [154.5 4.11.125] 6 55 ms 55 ms 55 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41 .113] 7 67 ms 68 ms 69 ms be2067.ccr21.iah01.atlas.cogentco.com [154.54.7. 161] 8 83 ms 82 ms 82 ms be2172.ccr41.atl01.atlas.cogentco.com [154.54.29 .17] 9 91 ms 91 ms 91 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31 .106] 10 93 ms 94 ms 93 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31 .130] 11 164 ms 164 ms 164 ms be2349.mpd21.lon13.atlas.cogentco.com [154.54.30 .178] 12 173 ms 174 ms 173 ms be2277.ccr41.ams03.atlas.cogentco.com [154.54.62 .146] 13 173 ms 173 ms 172 ms be2434.agr21.ams03.atlas.cogentco.com [130.117.2 .241] 14 174 ms 174 ms 176 ms te0-0-0-1.nr12.b021908-0.ams03.atlas.cogentco.co m [154.25.1.82] 15 181 ms 194 ms 181 ms 149.11.64.214 16 181 ms 181 ms 181 ms ophion.feralhosting.com [185.21.217.8] Trace complete. tracert 38.110.117.89 Tracing route to 89.117.110.38.rdns.lunanode.com [38.110.117.89] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 21 ms 21 ms 21 ms hlrn-dsl-gw08.hlrn.qwest.net [207.225.112.8] 3 21 ms 21 ms 21 ms hlrn-agw1.inet.qwest.net [71.217.188.57] 4 * * * Request timed out. 5 56 ms 55 ms 55 ms te0-4-0-35.ccr23.lax05.atlas.cogentco.com [154.5 4.11.125] 6 55 ms 55 ms 55 ms be2178.mpd22.lax01.atlas.cogentco.com [154.54.41 .117] 7 67 ms 69 ms 67 ms be2068.ccr22.iah01.atlas.cogentco.com [154.54.7. 157] 8 68 ms 68 ms 67 ms be2146.ccr22.dfw01.atlas.cogentco.com [154.54.25 .242] 9 77 ms 77 ms 78 ms be2010.ccr22.mci01.atlas.cogentco.com [154.54.46 .217] 10 80 ms 80 ms 80 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6. 118] 11 104 ms 105 ms 104 ms be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42 .6] 12 105 ms 105 ms 104 ms be2429.rcr12.yyz01.atlas.cogentco.com [154.54.1. 158] 13 105 ms 105 ms 105 ms te0-0-2-0.nr11.b011152-1.yyz01.atlas.cogentco.co m [154.24.4.146] 14 105 ms 104 ms 104 ms 38.140.10.90 15 105 ms 104 ms 104 ms 89.117.110.38.rdns.lunanode.com [38.110.117.89] 16 105 ms 105 ms 104 ms 89.117.110.38.rdns.lunanode.com [38.110.117.89] Trace complete. I notice both have a "Request timed out" around 4th hop... Youtube is sometimes virtually unusuable: Tracing route to r9.sn-p5qlsn7e.c.youtube.com [173.194.63.14] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 21 ms 21 ms 21 ms hlrn-dsl-gw08.hlrn.qwest.net [207.225.112.8] 3 21 ms 21 ms 21 ms hlrn-agw1.inet.qwest.net [71.217.188.57] 4 22 ms 22 ms 22 ms dvr-edge-13.inet.qwest.net [67.14.24.93] 5 88 ms 86 ms 79 ms 67.134.166.226 6 32 ms 39 ms 22 ms 72.14.234.59 7 22 ms 22 ms 23 ms 216.239.46.144 8 42 ms 32 ms 32 ms 72.14.239.48 9 44 ms 44 ms 44 ms 216.239.48.217 10 63 ms 72 ms 63 ms 72.14.232.70 11 64 ms 64 ms 64 ms 72.14.236.149 12 138 ms 128 ms 130 ms 209.85.252.47 13 64 ms 64 ms 64 ms 216.239.48.22 14 64 ms 64 ms 64 ms 173.194.63.14 Tracing route to r4.sn-2gph0nj5o-tt1e.c.youtube.com [216.254.154.15] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 21 ms 21 ms 23 ms hlrn-dsl-gw08.hlrn.qwest.net [207.225.112.8] 3 21 ms 21 ms 21 ms hlrn-agw1.inet.qwest.net [71.217.188.57] 4 22 ms 22 ms 22 ms dvr-brdr-02.inet.qwest.net [67.14.24.118] 5 22 ms 22 ms 22 ms 63.146.26.134 6 69 ms 69 ms 69 ms vlan52.ebr2.Denver1.Level3.net [4.69.147.126] 7 69 ms 70 ms 69 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62] 8 69 ms 69 ms 69 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189] 9 69 ms 69 ms 96 ms ae-1-9.bar1.Toronto1.Level3.net [4.69.151.109] 10 69 ms 102 ms 69 ms ae-0-11.bar2.Toronto1.Level3.net [4.69.151.242] 11 70 ms 70 ms 70 ms IB-COMMUNIC.bar2.Toronto1.Level3.net [4.28.138.7 0] 12 69 ms 69 ms 69 ms concord-idea-15.static.t1.primus.ca [216.254.154 .15] Trace complete. and is rated horribly: "Users on networks rated as Standard Definition should expect smooth playback on standard-definition YouTube videos (360p) and may experience occasional interruptions on high-definition YouTube videos (720p and above). " Any routing through the cogent network causes massive ping issues and slow download speeds. Help?

Viewing all articles
Browse latest Browse all 4880

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>