|
Routing issue between FiOS customers and alter.net?New topic thread for this, because I can't seem to post in the old one.
I am trying to watch a live stream on espn3.com and it is less than bearable. Stream keeps starting and stopping, and it will not display in high definition, which it has never had a problem before.
Here is my route to espn.go.com:
Tracing route to espn.go.com [68.71.213.221] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms myrouter.home [192.168.1.1] 2 4 ms 3 ms 3 ms L100.HSTNTX-VFTTP-01.verizon-gni.net [96.228.64. 1] 3 3 ms 3 ms 2 ms P2-1.HSTNTX-LCR-01.verizon-gni.net [130.81.97.14 0] 4 11 ms 11 ms 11 ms so-6-0-1-0.DFW01-BB-RTR1.verizon-gni.net [130.81 .29.234] 5 13 ms 13 ms 13 ms 0.xe-2-0-2.XL3.DFW7.ALTER.NET [152.63.1.18] 6 56 ms 56 ms 56 ms 0.xe-11-1-0.XL3.VEG2.ALTER.NET [152.63.1.234] 7 61 ms 61 ms 60 ms GigabitEthernet6-0-0.GW3.VEG2.ALTER.NET [152.63. 113.13] 8 60 ms 60 ms 60 ms switchcomm-gw.customer.alter.net [208.222.10.174 ] 9 62 ms 64 ms 62 ms te4-3.las-core2-1.switchnap.com [66.209.64.145]
10 61 ms 61 ms 61 ms te7-1.las-agg7s2-1.switchnap.com [66.209.64.98]
11 * * * Request timed out. 12 * * * Request timed out. 13 59 ms 59 ms 59 ms 68.71.213.221
Trace complete.
Now I will do it again:
Tracing route to espn.go.com [68.71.213.221] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms myrouter.home [192.168.1.1] 2 4 ms 3 ms 3 ms L100.HSTNTX-VFTTP-01.verizon-gni.net [96.228.64. 1] 3 4 ms 3 ms 3 ms P2-1.HSTNTX-LCR-01.verizon-gni.net [130.81.97.14 0] 4 11 ms 11 ms 11 ms so-6-0-1-0.DFW01-BB-RTR1.verizon-gni.net [130.81 .29.234] 5 12 ms 13 ms 12 ms 0.xe-2-0-2.XL3.DFW7.ALTER.NET [152.63.1.18] 6 56 ms 75 ms 56 ms 0.xe-11-1-0.XL3.VEG2.ALTER.NET [152.63.1.234] 7 61 ms 63 ms 60 ms GigabitEthernet6-0-0.GW3.VEG2.ALTER.NET [152.63. 113.13] 8 94 ms 60 ms 60 ms switchcomm-gw.customer.alter.net [208.222.10.174 ] 9 159 ms 201 ms 212 ms te4-3.las-core2-1.switchnap.com [66.209.64.145]
10 61 ms 61 ms 61 ms te7-1.las-agg7s2-1.switchnap.com [66.209.64.98]
11 * * * Request timed out. 12 * * * Request timed out. 13 62 ms 64 ms 60 ms 68.71.213.221
Obviously, there's nothing wrong on my end. But, there is obviously something wrong with alter.net and with switchnap.com. This effects my viewing pleasure, and leaves me very unsatisfied with verizon fios. |
|
McBane join:2008-08-22 Wylie, TX |
McBane
Member
2012-Oct-31 11:01 pm
That looks like a firewall or router that isn't responding to traceroutes to me. I honestly don't see a problem with that traceroute. Tonight is the first game night for the majority of the NBA, and with Harden's performance probably all of Houston are hitting up the same ESPN videos. My guess is it's a load issue on ESPN's side. Also, alter.net is Verizon, it's an old backbone Verizon bought (UUNet) |
|
|
If it was my router or a firewall, then it would show in the first 3 hops. It does not. This doesn't just effect espn.go.com. It also effects youtube.com and plenty of other websites that show streaming videos. |
|
McBane join:2008-08-22 Wylie, TX |
McBane
Member
2012-Nov-1 4:14 am
Remote firewalls can also block ICMP traffic and they're rarely on the first 3 hops. Firewalls don't exist only locally, they exist on the remote end you're trying to connect to as well and sometimes even in the middle of the routes on the backbones. Most hosting providers do block their internal network routing to protect it from hackers these days so it's pretty common to see packets dropped at the end going to a traceroute.
Try pinging and tracerouting to cnn.com for instance, same results. |
|
|
to lrdchaos3
said by lrdchaos3:If it was my router or a firewall, then it would show in the first 3 hops. It does not. This doesn't just effect espn.go.com. It also effects youtube.com and plenty of other websites that show streaming videos. Youtube is the WORST example that you could give for this issue. All you have to do is search Youtube buffering in Google and you will find thousands of people bitching about that problem. It is a well known issue that basically every ISP has issues with YouTube due to Google not having the bandwidth to support the site and not doing anything to address it for the last few years. Now as for ESPN I suspect what McBane said is correct, the problem with ESPN is they have a lot of people watching the same video (You need to realize there are a lot of people in NY/NJ that don't have TV service right now but do have a phone or tablet and want something to watch) and do not have the bandwidth or hardware to support the number of people watching it. |
|
Smith6612 MVM join:2008-02-01 North Tonawanda, NY ·Charter Ubee EU2251 Ubiquiti UAP-IW-HD Ubiquiti UniFi AP-AC-HD
|
I wouldn't quite say that. Google seems to have ample amounts of bandwidth to support YouTube. For what I've noticed, it not only depends on your ISP but it also depends on what cache farm you are going to. You still have that common entrance point to Google's network from your ISP regardless of the cache, but if you were to find a way to force a cache change (perhaps by modifying the video URL when you are downloading it, for example) you could still land at the same datacenter, but on another cache.
Their problem just seems to be a case where they are not properly load balancing traffic across ALL of their machines. Their network being saturated would bother more than just YouTube. It would bother Google.com and other Google services. |
|
|
So, you guys are telling me with Verizon FIOS 15 MB down and 5 MB upload I shouldn't be able to stream videos on the internet?
Did you guys even look at my traceroute? |
|
lrdchaos3 |
|
|
guppy_fish Premium Member join:2003-12-09 Palm Harbor, FL |
Thats one crappy test site, show my flawless 15/5 which runs at 25/5 24/7 as 2mb down, 5 mb up |
|
guppy_fish |
to lrdchaos3
said by lrdchaos3:So, you guys are telling me with Verizon FIOS 15 MB down and 5 MB upload I shouldn't be able to stream videos on the internet?
Did you guys even look at my traceroute? Were not saying FIOS can't handle the stream, were saying the content provider ( host ) can't handle the requests ... very common. While your on a 8 lane highway with FIOS, the event your trying to view is trying to get out of the parking lot on a single lane, dirt road with ruts in the road ... maybe that will help you understand some of the limitations of the internet |
|
ilikeme Premium Member join:2002-08-27 Stafford, TX |
to lrdchaos3
Just out of curiosoty, what area of Houston are you in? I did not think any of the Verizon areas down there had FIOS. Here is what I get to that site from up here near Dallas.
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
tracert espn.go.com
Tracing route to espn.go.com [68.71.212.186] over a maximum of 30 hops:
1 54 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 5 ms 4 ms 4 ms L100.DLLSTX-VFTTP-87.verizon-gni.net [68.238.152 .1] 3 6 ms 5 ms 5 ms G0-3-2-4.DLLSTX-LCR-21.verizon-gni.net [130.81.1 38.0] 4 6 ms 7 ms 7 ms so-4-1-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81. 151.242] 5 21 ms 24 ms 22 ms 0.ge-6-3-0.XT3.DFW9.ALTER.NET [152.63.96.193] 6 50 ms 52 ms 51 ms 0.xe-11-1-0.XL3.VEG2.ALTER.NET [152.63.1.234] 7 57 ms 62 ms 62 ms GigabitEthernet6-0-0.GW3.VEG2.ALTER.NET [152.63. 113.13] 8 59 ms 103 ms 62 ms switchcomm-gw.customer.alter.net [208.222.10.174 ] 9 62 ms 65 ms 61 ms te4-3.las-core2-1.switchnap.com [66.209.64.145]
10 59 ms 61 ms 64 ms te7-1.las-agg7s2-1.switchnap.com [66.209.64.98]
11 * * * Request timed out. 12 * * * Request timed out. 13 56 ms 59 ms 59 ms 68.71.212.186 |
|
|
I am in League City, TX. It's just south of Houston and the very small area down here that offers verizon FIOS. Here's my smokeping results: » /r3/sm ··· bfd1c22bI used that "crappy" speedtest site because it said it was located in Houston and I wanted to test something close. The issues I'm having only seem to happen during primetime hours. 7:00 PM until 9:30 PM. |
|
|
ilikeme Premium Member join:2002-08-27 Stafford, TX |
ilikeme
Premium Member
2012-Nov-2 12:42 pm
Ah, I knew League City was Verizon, but did not know it had FIOS. I am originally from Sugar Land. |
|
guppy_fish Premium Member join:2003-12-09 Palm Harbor, FL |
to lrdchaos3
said by lrdchaos3:I am in League City, TX. It's just south of Houston and the very small area down here that offers verizon FIOS.
Here's my smokeping results:
»/r3/sm ··· bfd1c22b
I used that "crappy" speedtest site because it said it was located in Houston and I wanted to test something close.
The issues I'm having only seem to happen during primetime hours. 7:00 PM until 9:30 PM. Your image is testing to Washington DC to some totally unknown server, its also a European based speed test site. You have yet to explain what your issue is, except to say 7:00-9:00pm, what is slow, a game server? |
|
batsonaMaryland join:2004-04-17 Ellicott City, MD |
to lrdchaos3
Slightly off-topic.. lrdchaos3: Do you know a Mr. Bob McNeil? An old co-worker of mine who lives in League City. Lived in one of the neighborhoods off of the east side of rt45... |
|
|
to guppy_fish
That is one of the problems I'm experiencing. I am having extremely high latency issues with game servers. I am having problems watching video streams on the internet. The problem seems to be with alter.net. A routing problem.
I don't know who Bob McNeil is. |
|
guppy_fish Premium Member join:2003-12-09 Palm Harbor, FL |
said by lrdchaos3:That is one of the problems I'm experiencing. I am having extremely high latency issues with game servers. I am having problems watching video streams on the internet. The problem seems to be with alter.net. A routing problem.
I don't know who Bob McNeil is. Its not FIOS, its where your getting the content ... 159 ms 201 ms 212 ms te4-3.las-core2-1.switchnap.com switchnap is overloaded |
|
|
to lrdchaos3
Coming from central NJ here
C:\Users\XXXX>tracert ftp9.us.freebsd.org
Tracing route to osmirrors.cerias.purdue.edu [128.10.252.13] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router [192.168.10.1] 2 3 ms 5 ms 4 ms L100.NWRKNJ-VFTTP-99.verizon-gni.net [98.109.77.1] 3 5 ms 5 ms 4 ms G0-5-4-0.NWRKNJ-LCR-21.verizon-gni.net [130.81.183.145] 4 6 ms 9 ms 12 ms ae0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.154] 5 7 ms 7 ms 7 ms 0.xe-8-1-0.XL3.NYC1.ALTER.NET [152.63.5.213] 6 10 ms 9 ms 9 ms 0.ae3.BR2.NYC4.ALTER.NET [152.63.3.110] 7 9 ms 9 ms 9 ms 204.255.168.110 8 10 ms 9 ms 9 ms te0-1-05.mpd21.jfk02.atlas.cogentco.com [154.54.3.97] 9 8 ms 9 ms 9 ms te2-3.ccr01.jfk01.atlas.cogentco.com [154.54.24.145] 10 * 9 ms 9 ms te7-2.ccr01.alb02.atlas.cogentco.com [154.54.42.141] 11 * 22 ms 19 ms te3-.ccr01.buf02.atlas.cogentco.com [154.54.42.241] 12 33 ms * 35 ms te4-.ccr02.cle04.atlas.cogentco.com [154.54.27.86] 13 36 ms * * te3-7.ccr01.cmh02.atlas.cogentco.com [154.54.45.121] 14 37 ms 37 ms 34 ms te3-.ccr01.cvg02.atlas.cogentco.com [154.54.84.173] 15 35 ms 34 ms 35 ms te3-.ccr01.ind01.atlas.cogentco.com [154.54.84.166] 16 112 ms 112 ms 111 ms 38.104.214.6 17 * 36 ms 37 ms indiana-gigapop-ctc-internet-mx960.tcom.purdue.edu [192.5.40.179] 18 39 ms 39 ms 39 ms tel-210-c7609s-01-te1-1-890.tcom.purdue.edu [192.5.40.177] 19 * * * Request timed out. 20 40 ms 39 ms 39 ms cisco3.cerias.purdue.edu [128.10.254.1] 21 37 ms 37 ms 42 ms osmirrors.cerias.purdue.edu [128.10.252.13]
Trace complete. Hop 16 is quite crazy, given the hops after it are far quicker.
And a second, this time from my NAS. Not sure where the loss' origin truly is:
[user@NAS ~]$ traceroute ftp9.us.freebsd.org traceroute to osmirrors.cerias.purdue.edu (128.10.252.13), 64 hops max, 52 byte packets 1 router (192.168.10.1) 3.359 ms 3.088 ms 3.643 ms 2 L100.NWRKNJ-VFTTP-99.verizon-gni.net (98.109.77.1) 9.218 ms 7.439 ms 7.656 ms 3 G0-5-4-0.NWRKNJ-LCR-21.verizon-gni.net (130.81.183.145) 8.092 ms 7.534 ms 7.599 ms 4 ae0-0.NWRK-BB-RTR1.verizon-gni.net (130.81.209.154) 8.535 ms * * 5 0.xe-8-1-0.XL3.NYC1.ALTER.NET (152.63.5.213) 11.483 ms 9.872 ms 9.963 ms 6 0.ae3.BR2.NYC4.ALTER.NET (152.63.3.110) 13.736 ms 13.619 ms 59.876 ms 7 204.255.168.114 (204.255.168.114) 9.961 ms 9.853 ms 10.093 ms 8 te0-2-0-4.mpd22.jfk02.atlas.cogentco.com (154.54.46.253) 13.649 ms te0-6-0-4.mpd21.jfk02.atlas.cogentco.com (154.54.46.249) 11.545 ms te0-3-0-5.mpd22.jfk02.atlas.cogentco.com (154.54.3.165) 13.155 ms 9 te9-8.ccr01.jfk01.atlas.cogentco.com (154.54.40.29) 13.390 ms te2-3.ccr01.jfk01.atlas.cogentco.com (154.54.24.145) 13.119 ms te9-1.ccr01.jfk01.atlas.cogentco.com (154.54.1.173) 10.528 ms 10 te8-2.ccr01.alb02.atlas.cogentco.com (154.54.43.5) 219.976 ms te7-2.ccr01.alb02.atlas.cogentco.com (154.54.42.141) 195.035 ms * 11 * * te3-8.ccr01.buf02.atlas.cogentco.com (154.54.42.241) 172.321 ms 12 te4-2.ccr02.cle04.atlas.cogentco.com (154.54.27.86) 38.396 ms te8-8.ccr02.cle04.atlas.cogentco.com (154.54.31.237) 36.637 ms * 13 * * * 14 te3-7.ccr01.cvg02.atlas.cogentco.com (154.54.84.173) 41.485 ms te4-7.ccr01.cvg02.atlas.cogentco.com (154.54.84.177) 40.749 ms 39.971 ms 15 te3-4.ccr01.ind01.atlas.cogentco.com (154.54.84.166) 38.346 ms te4-1.ccr01.ind01.atlas.cogentco.com (154.54.84.170) 41.332 ms te3-4.ccr01.ind01.atlas.cogentco.com (154.54.84.166) 37.565 ms 16 38.104.214.6 (38.104.214.6) 62.944 ms 63.699 ms 63.250 ms 17 indiana-gigapop-ctc-internet-mx960.tcom.purdue.edu (192.5.40.179) 39.983 ms * 39.588 ms 18 tel-210-c7609s-01-te1-1-890.tcom.purdue.edu (192.5.40.177) 42.235 ms 43.776 ms 43.773 ms 19 * * * 20 * * *
It keeps timing out after #20 now.
I've had packet loss issues since 25/OCT, pre-Sandy |
|
|
to lrdchaos3
alter.net is Verizon, it goes back to the old UUnet days. |
|
guppy_fish Premium Member join:2003-12-09 Palm Harbor, FL |
None of the trace routes in this thread show alter.net as the issue, all the posted routes show third party network congestion
te3-8.ccr01.buf02.atlas.cogentco.com (154.54.42.241) 172.321 ms
159 ms 201 ms 212 ms te4-3.las-core2-1.switchnap.com
112 ms 112 ms 111 ms 38.104.214.6 ( a cogentco IP ) |
|