Telia poor routing to Dacentec... Ongoing issue?

pubcrawler

Well just looked at routes packets are flowing today to Dacentec.

From my Time Warner connection now we are heading out from Chicago to Lenoir via Cogent! Ping times are often a bit under 50ms, which is lower than before.

12: ae-1-0.pr0.chi10.tbone.rr.com 30.593ms
13: te0-2-0-7.ccr22.ord03.atlas.cogentco.com 34.777ms asymm 17
14: te0-3-0-0.ccr22.ord01.atlas.cogentco.com 37.727ms asymm 16
15: te0-0-0-4.ccr21.atl01.atlas.cogentco.com 47.512ms asymm 16
16: no reply
17: dacentec.demarc.cogentco.com 57.504ms
18: dct-ds04--vl56.dacentec.com 55.469ms

rtt min/avg/max/mdev = 46.706/51.420/64.356

Looks like someone did something at Dacentec about Chicago routes

qps

TWC/RR has some crappy routing. They recently started routing everything from here (about 10 miles north of Charlotte) to Raleigh to Washington DC rather than from here to Atlanta for me, so that adds a ton of extra latency for just about everything.

1 2 ms 1 ms 3 ms router [192.168.1.1]
2 40 ms 30 ms 27 ms cpe-075-181-160-001.carolina.res.rr.com [75.181.160.1]
3 11 ms 14 ms 11 ms cpe-024-074-253-225.carolina.res.rr.com [24.74.253.225]
4 20 ms 21 ms 36 ms ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 32 ms 34 ms 55 ms 107.14.19.20
6 28 ms 30 ms 24 ms 107.14.19.133
7 27 ms 30 ms 48 ms te0-6-0-7.mpd21.iad02.atlas.cogentco.com [154.54.10.193]
8 32 ms 27 ms 28 ms te0-5-0-2.mpd21.dca01.atlas.cogentco.com [154.54.1.205]
9 39 ms 38 ms 31 ms te4-4.ccr01.clt01.atlas.cogentco.com [154.54.84.254]
10 46 ms 44 ms 47 ms dacentec.demarc.cogentco.com [38.104.168.10]
11 52 ms 42 ms 49 ms mirror.dacentec.com [199.191.56.90]

fly

nope, telia still derping it up for me

http://sprunge.us/SFiE

i opened another ticket

Holoshed

@pubcrawler said: From my Time Warner connection now we are heading out from Chicago to Lenoir via Cogent! Ping times are often a bit under 50ms, which is lower than before.

I am in Winston-Salem (triad.rr.com) and getting telia still. I am actually surprised you are not all that far but RR is routing it so different.

1 172.16.1.1 (172.16.1.1) 4.210 ms 2.470 ms 0.928 ms
2 * * *
3 gi15-0-0-2102.gnboncsg-rtr1.triad.rr.com (24.28.228.57) 19.109 ms 11.355 ms 10.513 ms
4 ge-1-3-0.rlghncpop-rtr1.southeast.rr.com (24.93.64.48) 14.132 ms 22.516 ms 12.425 ms
5 107.14.19.44 (107.14.19.44) 38.166 ms
107.14.19.42 (107.14.19.42) 34.502 ms
107.14.19.44 (107.14.19.44) 33.971 ms
6 107.14.19.133 (107.14.19.133) 37.603 ms 27.784 ms
ae-2-0.pr0.dca10.tbone.rr.com (66.109.6.169) 26.316 ms
7 ash-bb1-link.telia.net (80.239.132.169) 35.079 ms
ash-bb1-link.telia.net (80.239.167.237) 31.906 ms
ash-bb1-link.telia.net (80.239.132.169) 86.976 ms
8 ash-bb3-link.telia.net (80.91.248.156) 25.352 ms
adm-bb3-link.telia.net.130.155.213.in-addr.arpa (213.155.130.0) 26.634 ms
ash-bb3-link.telia.net (80.91.248.156) 25.375 ms
9 atl-bb1-link.telia.net (213.155.134.131) 24.547 ms
atl-bb1-link.telia.net (80.91.252.218) 27.415 ms
atl-bb1-link.telia.net (80.91.248.137) 26.177 ms
10 dacentec-ic-154273-atl-bb1.c.telia.net (213.155.129.114) 41.645 ms 41.665 ms 39.914 ms
11 dct-cr01--v51.dacentec.com (199.255.156.53) 54.555 ms 49.586 ms 50.986 ms
12 dct-ds08-vl-41 (199.241.190.230) 60.447 ms 50.277 ms 50.195 ms
13 (192.198) 51.539 ms 49.898 ms 47.892 ms

qps

@fly said: nope, telia still derping it up for me

http://sprunge.us/SFiE

i opened another ticket

You're running through Inteliquent (fka Tinet), not Telia.

qps

@Holoshed said: I am in Winston-Salem (triad.rr.com) and getting telia still. I am actually surprised you are not all that far but RR is routing it so different.

That's very strange. My traceroute still matches what I showed above (through Cogent). Hard to believe that the routing is that different...

fly

derp same diff

NateN34

Believe it or not, my route has changed... For the better too.

Slightly less latency as a result.

fly

We have been approved for more network hardware which will allow better traffic flow. It is another layer of networking and will require a little bit of time to complete.
We have an open (internal) ticket to complete this as soon as possible.

In the meantime we might be able to route you differently internally which will improve your performance. I can take out 1 hop internally.
If I set it up in the background the only time you would go down is when physically move the cable/switch your route. It will be approximately 2-3 seconds.

yall can thank me

pubcrawler

What is that @fly? From your ticket with Dacentec?

Unsure how their internal hack does anything for the rest of us ...