dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2806
rippleeffect
join:2012-11-02
Palmdale, CA

rippleeffect

Member

[Connectivity] Odd Routing of Twitch.tv Traffic

I'm in Colorado Springs trying to broadcast to an ingest server for Twitch TV through either Dallas or Chicago, depending on how bad my connection is that day. I confused as to what's going on with these paths the data is going.

live.twitch.tv San Francisco
live-dfw.twitch.tv Dallas
live-ord.twitch.tv Chicago

None of this routing makes sense.
CoSpgs > CA > DFW
CoSpgs > DFW > Chicago
CoSpgs > DFW > SF

No wonder why I have such a poor quality connection to Twitch. Its sending me everywhere! Anyone else seeing this?

From Colorado Springs to Dallas it appears to send me back to California before going back to Dallas.

C:\Users\Jason>tracert live-fdw.twitch.tv

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

1 tracert live-ord.twitch.tv

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

1 tracert live.twitch.tv

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

1 1 ms 1 ms 1 ms READYSHARE [192.168.1.1]
2 26 ms 29 ms 40 ms 71.229.236.1
3 15 ms 11 ms 10 ms te-0-5-0-10-ur04.cosprings.co.denver.comcast.net
[69.139.228.245]
4 15 ms 15 ms 15 ms te-0-5-0-2-ar02.aurora.co.denver.comcast.net [68
.85.89.45]
5 14 ms 15 ms 15 ms he-3-4-0-0-cr01.denver.co.ibone.comcast.net [68.
86.90.149]
6 28 ms 27 ms 31 ms he-2-7-0-0-cr01.dallas.tx.ibone.comcast.net [68.
86.85.54]
7 28 ms 29 ms 52 ms be-13-pe02.1950stemmons.tx.ibone.comcast.net [68
.86.82.142]
8 * * * Request timed out.
9 * ^C

EG
The wings of love
Premium Member
join:2006-11-18
Union, NJ

EG

Premium Member

[Connectivity] Re: Odd Routing of Twitch.tv Traffic

FWIW, All I see in that trace is Colorado to Texas. And the response times seem right.

train_wreck
slow this bird down
join:2013-10-04
Antioch, TN
Cisco ASA 5506
Cisco DPC3939

train_wreck to rippleeffect

Member

to rippleeffect
where are you seeing california? and are you sure that those "xxxx.twitch.tv" domains are definitely in San Fransisco, Dallas, and Chicago, as you say they are? keep in mind that CDN hosting can make your final destination end up somewhere other than the actual server location, at least as far as a traceroute would show.

there was a story a few days ago about how the "twitch plays pokemon" thing was degrading the twitch.tv servers, you might be seeing a side effect of this.

here's mine, which stops at Ashburn....

traceroute to live.twitch.tv (199.9.251.235), 30 hops max, 60 byte packets
 1  x-x-x-x-Knoxville.hfc.comcastbusiness.net (x.x.x.x)  0.566 ms  0.563 ms  0.520 ms
 2  96.173.76.1 (96.173.76.1)  26.933 ms  17.452 ms  26.836 ms
 3  xe-3-2-0-32767-sur01.ruralhillrd.tn.nash.comcast.net (68.85.50.189)  13.940 ms  14.461 ms  15.353 ms
 4  xe-5-1-11-0-ar01.goodslettvll.tn.nash.comcast.net (68.86.176.57)  18.089 ms  65.462 ms  13.351 ms
 5  he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.90.189)  19.609 ms  23.619 ms  23.679 ms
 6  he-0-6-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.89.161)  37.266 ms  37.099 ms  32.767 ms
 7  he-0-11-0-0-pe07.ashburn.va.ibone.comcast.net (68.86.83.74)  36.253 ms  39.245 ms  33.301 ms
 

Qumahlin
Never Enough Time
MVM
join:2001-10-05
united state

Qumahlin to rippleeffect

MVM

to rippleeffect
Regardless of where you're being sent your response times are still well within a "good" range so that shouldn't be the issue. Could they be faster? Yes, but really not by much.
rippleeffect
join:2012-11-02
Palmdale, CA

rippleeffect

Member

bah, my copy/paste didn't throw everything in there.

These times are all pretty good, but during peak hours, I'll see pings in the 800s and jitter around 50ms.

During that time too I'll barely have 2up while paying for 50/10 (normal speeds are 57/12)

EG
The wings of love
Premium Member
join:2006-11-18
Union, NJ

1 recommendation

EG

Premium Member

said by rippleeffect:

bah, my copy/paste didn't throw everything in there.

O/k but it appears that the trace was deliberately aborted here;

"9 * ^C" CNTRL & C

jlivingood
Premium Member
join:2007-10-28
Philadelphia, PA

jlivingood to rippleeffect

Premium Member

to rippleeffect
I think they recently did at least one datacenter upgrade, so maybe that is still in process?

plencnerb
Premium Member
join:2000-09-25
53403-1242

plencnerb to rippleeffect

Premium Member

to rippleeffect
For what its worth, below is my full trace route. It times out at hop #6, but I left it run for the 30 hops just to show that it never does complete.

tracert live.twitch.tv
 
Tracing route to live.twitch.tv [199.9.251.241]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms     1 ms  m0n0wall.local [192.168.1.1]
  2    23 ms    11 ms    10 ms  24.13.16.1
  3     9 ms    10 ms    10 ms  te-0-7-0-18-sur04.algonquin.il.chicago.comcast.net [68.87.229.189]
  4    16 ms    15 ms    15 ms  te-2-7-0-6-ar01.area4.il.chicago.comcast.net [68.86.189.241]
  5    13 ms    15 ms    19 ms  pos-3-9-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.17]
  6    15 ms    13 ms    12 ms  he-0-12-0-0-pe04.350ecermak.il.ibone.comcast.net [68.86.83.162]
  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     *        *        *     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.
 
 

I also did a ping, which also times out.

ping live.twitch.tv
 
Pinging live.twitch.tv [199.9.251.234] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 199.9.251.234:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 

--Brian

train_wreck
slow this bird down
join:2013-10-04
Antioch, TN
Cisco ASA 5506
Cisco DPC3939

train_wreck to EG

Member

to EG
said by EG:

said by rippleeffect:

bah, my copy/paste didn't throw everything in there.

O/k but it appears that the trace was deliberately aborted here;

"9 * ^C"
right, because i believe he hit a device that wasn't forwarding pings? (notice he killed it just as the 2nd hop in a row timed out)

EG
The wings of love
Premium Member
join:2006-11-18
Union, NJ

EG

Premium Member

said by train_wreck:

right, because i believe he hit a device that wasn't forwarding pings? (notice he killed it just as the 2nd hop in a row timed out)

Maybe you're not getting it. The reason I mentioned it is because he stated this;

"bah, my copy/paste didn't throw everything in there."

Doesn't really matter anyway....

train_wreck
slow this bird down
join:2013-10-04
Antioch, TN

train_wreck

Member

alrighty then...