dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1244
AcePuppy
join:2014-10-15
Gainesville, VA

2 edits

AcePuppy

Member

Twitch.tv Casting/Broadcasting Buffering/Stalling/Lagging

This has been longed talked about and I even went to Verizon directly about this 3 days ago, they said they would look in the issue. Yesterday I called back and they stated their network engineers looked into it and after running a tracert themselves said it has nothing to do with Verizon. I am a broadcaster who makes my living off of Twitch. I come across these problems in the evening but also during the day randomly. Below is a tracert myself (anything after Hop 8 will time out as Twitch does not accept ping/ICMP traffic). Hop 4 should not be timing out.

I have no problems streaming other broadcasters, watching VOD off Twitch.. just broadcasting myself.

I have seen threads on here and on reddit and twitch in the NorthernVA area and Richmond area with the same problem broadcasting.

I have 150/150 internet so there should be no problem with me streaming or broadcasting on Twitch.

I am very IT savy so I have tried everything from changing from Verizon's DNS to Open DNS to Google DNS to blocking certain ranges, etc.

Twitch is the only site I have encountered any problems with. Can we all come together and find a solution to this problem, if possible can an actual Verizon rep look into this?

tracert live.twitch.tv

Tracing route to live.twitch.tv [199.9.249.199]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 2 ms 1 ms 1 ms L100.WASHDC-VFTTP-94.verizon-gni.net [96.241.211.1]
3 5 ms 3 ms 7 ms G1-7-0-1.WASHDC-LCR-22.verizon-gni.net [100.41.195.82]
4 * * * Request timed out.
5 43 ms 79 ms 14 ms 0.xe-0-0-0.XL4.IAD8.ALTER.NET [152.63.36.202]
6 17 ms 10 ms 12 ms TenGigE0-7-0-4.GW1.IAD8.ALTER.NET [152.63.36.222]
7 6 ms 6 ms 6 ms teliasonera-gw.customer.alter.net [152.179.50.234]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

nycdave
MVM
join:1999-11-16
Melville, NY

nycdave

MVM

Hop 4 timing out is normal for a device that doesn't respond to ICMP pings, since the trace continues after that hop....

My trace from NY looks similar, which indicates the issue is beyond Verizon:

tracert live.twitch.tv

Tracing route to live.twitch.tv [199.9.251.254]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 3 ms 4 ms L100.NYCMNY-VFTTP-124.verizon-gni.net [96.232.13
2.1]
3 5 ms 6 ms 8 ms G0-7-3-7.NYCMNY-LCR-21.verizon-gni.net [130.81.1
75.4]
4 90 ms 33 ms 3 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.
102]
5 * * * Request timed out.
6 9 ms 8 ms 8 ms 2.ae1.XT1.NYC4.ALTER.NET [140.222.228.119]
7 12 ms 10 ms 10 ms TenGigE0-6-0-6.GW5.NYC4.ALTER.NET [152.63.17.142
]
8 7 ms 6 ms 6 ms teliasonera-gw.customer.alter.net [152.179.163.1
78]
9 62 ms 15 ms 8 ms nyk-bb2-link.telia.net [213.155.135.78]
10 10 ms 8 ms 8 ms nyk-b3-link.telia.net [80.239.147.136]
11 * * * Request timed out.
12 * * * Request timed out.
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 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Since I can load the main Twitch site and see content, something else is going on. A trace to www.twitch.tv is resolving to a different host and subnet:

tracert www.twitch.tv

Tracing route to cdn.justin.tv.c.footprint.net [192.221.118.253]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 24 ms 28 ms 25 ms L100.NYCMNY-VFTTP-124.verizon-gni.net [96.232.13
2.1]
3 8 ms 6 ms 6 ms G0-7-3-6.NYCMNY-LCR-22.verizon-gni.net [130.81.1
75.2]
4 7 ms 21 ms 5 ms so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.18]
5 * * * Request timed out.
6 7 ms 8 ms 8 ms 0.ae1.BR3.NYC4.ALTER.NET [140.222.229.97]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 ^C

I think you need to contact Twitch for them to investigate from their side.
AcePuppy
join:2014-10-15
Gainesville, VA

AcePuppy

Member

Twitch is not the issue, like I said the only problem I am having is broadcasting on Twitch, everything else on Twitch is fine. Now if streaming others was an issue then I would believe Twitch would be the issue, but others in this area are having the same problem with Twitch and Verizon.
hubrisnxs
join:2009-12-30
Fountain Valley, CA

hubrisnxs to AcePuppy

Member

to AcePuppy
Twitch historically has terrible routing and pretty bad uploads. surprised it looks good on any network.
hubrisnxs

hubrisnxs to AcePuppy

Member

to AcePuppy
fwiw, just google twitch broadcasting problems ______________

then insert any carrier name, uverse, Comcast etc....

You'll see what I mean
AcePuppy
join:2014-10-15
Gainesville, VA

AcePuppy

Member

said by hubrisnxs:

fwiw, just google twitch broadcasting problems ______________

then insert any carrier name, uverse, Comcast etc....

You'll see what I mean

Yeah, I already know this. I'm a broadcaster. Again trying to find a solution, not trying to talk about what we already know is the problem and already stated in my OP.

PoloDude
Premium Member
join:2006-03-29
Aiken, SC

PoloDude

Premium Member

The solution is to go to twitch with the problem.
AcePuppy
join:2014-10-15
Gainesville, VA

AcePuppy

Member

said by PoloDude:

The solution is to go to twitch with the problem.

Read above that. Twitch is not the issue.

nycdave
MVM
join:1999-11-16
Melville, NY

nycdave

MVM

From your own post, you stated this is an issue with you broadcasting on Twitch but not other sites. If you don't have an issue with other sites, how is this not related to Twitch? Verizon doesn't host Twitch, so asking for solutions in this forum won't help. The last hop in my trace to resolve is Telia, so Twitch needs to engage their upstream providers to help determine what is going on. We can't speculate without a reverse trace from Twitch.
AcePuppy
join:2014-10-15
Gainesville, VA

AcePuppy

Member

said by nycdave:

From your own post, you stated this is an issue with you broadcasting on Twitch but not other sites. If you don't have an issue with other sites, how is this not related to Twitch? Verizon doesn't host Twitch, so asking for solutions in this forum won't help. The last hop in my trace to resolve is Telia, so Twitch needs to engage their upstream providers to help determine what is going on. We can't speculate without a reverse trace from Twitch.

Why would they need to engage their upstream providers if the issue has been constant with those on FiOS in the Northern VA and Richmond areas, but no where else. Upstream is not an issue because streaming is fine as well as watching VOD. Anything after hop 8 will time out as Twitch blocks ping/icmp/tracert traffic.

Hop 4 is run by Verizon and is not blocked by ICMP so it should resolve fine as seen below. Hop 4 goes in and out. This is a Verizon problem.

Tracing route to live.twitch.tv [199.9.251.166]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 192.168.1.1
2 5 ms 5 ms 5 ms L100.WASHDC-VFTTP-94.verizon-gni.net [96.241.211.1]
3 9 ms 8 ms 8 ms G0-13-3-4.WASHDC-LCR-21.verizon-gni.net [130.81.109.170]
4 11 ms 8 ms 25 ms ae7-0.RES-BB-RTR1.verizon-gni.net [130.81.174.208]
5 10 ms 11 ms 10 ms 0.so-2-0-2.XL3.IAD8.ALTER.NET [152.63.30.17]
6 21 ms 10 ms 12 ms TenGigE0-6-0-1.GW1.IAD8.ALTER.NET [152.63.35.137]
^C
hubrisnxs
join:2009-12-30
Fountain Valley, CA

hubrisnxs

Member

that's not true. it's everywhere else. less than a minute of googling proves that.

If there is an actual issue, the latency, the time out, the packet loss ALL will continue or increase for all future hops. If they don't, then it's not a real issue. a packet can't magically recreate itself if it's fully being dropped.

Latency spikes in the middle of a traceroute mean absolutely nothing if they do not continue forward. same is true for the time outs and/or perceived packet loss

- At worst it could be the result of an asymmetric path.
-But it is probably an artificial rate-limit or prioritization issue.
- By definition, if regularly forwarded packets are being affected
you should see the issue persist on all future hops.
hubrisnxs

hubrisnxs to AcePuppy

Member

to AcePuppy
if this was true and you know this, then why are you here and not at twitch site or reddit? it's a problem with twitch.

nycdave
MVM
join:1999-11-16
Melville, NY

nycdave to AcePuppy

MVM

to AcePuppy
said by AcePuppy:

said by nycdave:

From your own post, you stated this is an issue with you broadcasting on Twitch but not other sites. If you don't have an issue with other sites, how is this not related to Twitch? Verizon doesn't host Twitch, so asking for solutions in this forum won't help. The last hop in my trace to resolve is Telia, so Twitch needs to engage their upstream providers to help determine what is going on. We can't speculate without a reverse trace from Twitch.

Why would they need to engage their upstream providers if the issue has been constant with those on FiOS in the Northern VA and Richmond areas, but no where else. Upstream is not an issue because streaming is fine as well as watching VOD. Anything after hop 8 will time out as Twitch blocks ping/icmp/tracert traffic.

Hop 4 is run by Verizon and is not blocked by ICMP so it should resolve fine as seen below. Hop 4 goes in and out. This is a Verizon problem.

Tracing route to live.twitch.tv [199.9.251.166]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 192.168.1.1
2 5 ms 5 ms 5 ms L100.WASHDC-VFTTP-94.verizon-gni.net [96.241.211.1]
3 9 ms 8 ms 8 ms G0-13-3-4.WASHDC-LCR-21.verizon-gni.net [130.81.109.170]
4 11 ms 8 ms 25 ms ae7-0.RES-BB-RTR1.verizon-gni.net [130.81.174.208]
5 10 ms 11 ms 10 ms 0.so-2-0-2.XL3.IAD8.ALTER.NET [152.63.30.17]
6 21 ms 10 ms 12 ms TenGigE0-6-0-1.GW1.IAD8.ALTER.NET [152.63.35.137]
^C

For someone who claims to be IT savvy, you have no idea if you think a hop that doesn't resolve is an issue....
silbaco
Premium Member
join:2009-08-03
USA

silbaco to AcePuppy

Premium Member

to AcePuppy
Keep in mind the server that you upload your broadcast to is probably not going to be the same server you stream a broadcast from. Twitch.tv has servers located all over the US so they may not even be in the same region.
Expand your moderator at work
hubrisnxs
join:2009-12-30
Fountain Valley, CA

hubrisnxs to AcePuppy

Member

to AcePuppy

Re: Twitch.tv Casting/Broadcasting Buffering/Stalling/Lagging

something you didn't share, but I noticed in a reddit post by you is that they are sending you to a SFO server, instead of something local. you should play with your DNS more to try to get a better server, or even go so far as to try a VPN. There's something about your set up that is triggering a shot over to a distant server, far far away, and THAT more than anything is probably causing your issue.

Try A LOT of different dns's or ask people that are hitting the DC servers, what DNS are they using, and then duplicate it.

If you try one or two or even 4 or 5 and it doesn't work, don't get discouraged, try several like upto 10 or 15 diff ones.

Try these two lists
»www.getdriver.com/how-to ··· nce.html

»pcsupport.about.com/od/t ··· vers.htm
AcePuppy
join:2014-10-15
Gainesville, VA

AcePuppy

Member

said by hubrisnxs:

something you didn't share, but I noticed in a reddit post by you is that they are sending you to a SFO server, instead of something local. you should play with your DNS more to try to get a better server, or even go so far as to try a VPN. There's something about your set up that is triggering a shot over to a distant server, far far away, and THAT more than anything is probably causing your issue.

Try A LOT of different dns's or ask people that are hitting the DC servers, what DNS are they using, and then duplicate it.

If you try one or two or even 4 or 5 and it doesn't work, don't get discouraged, try several like upto 10 or 15 diff ones.

Try these two lists
»www.getdriver.com/how-to ··· nce.html

»pcsupport.about.com/od/t ··· vers.htm

No can do. Even used namebench.