High Ping Times Through ATDN.NET

[lgieg]

Hi All -

I run a game server and my users on the Road Runner network are experiencing high latency (>100ms, which is high for intranational game server connectivity) because they are routing through the Qwest<>ATDN.net connection (66.185.139.218). I contacted the techie POC for atdn.net and the people who answered the phone didn't know what a router is ("we're just here for email problems!"). I wanted to know if anyone else is having this problem - which seems to be intermittent. Traceroute follows:

Tracing route to www.poopvortex.com [72.4.174.108]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 172.19.97.1
2 7 ms 7 ms 7 ms 10.47.192.1
3 7 ms 7 ms 7 ms ge0-3.nycmnys-ubr9.nyc.rr.com [24.29.104.169]
4 8 ms 7 ms 7 ms 24-29-100-13.nyc.rr.com [24.29.100.13]
5 8 ms 7 ms 7 ms 24-29-104-202.nyc.rr.com [24.29.104.202]
6 8 ms 7 ms 7 ms pos4-0-nycmnyl-rtr1.nyc.rr.com [24.29.100.85]
7 8 ms 6 ms 8 ms tenge10-0-0.nycmnyrdc-rtr1.nyc.rr.com [24.29.119.117]
8 7 ms 8 ms 8 ms tenge2-1-0.nycmnyrdc-rtr2.nyc.rr.com [24.29.119.146]
9 9 ms 7 ms 9 ms pop2-nye-P11-0.atdn.net [66.185.146.21]
10 112 ms 9 ms 7 ms bb1-nye-P1-0.atdn.net [66.185.151.64]
11 14 ms 14 ms 12 ms bb2-ash-P10-0.atdn.net [66.185.152.87]
12 13 ms 14 ms 13 ms pop2-ash-P3-0.atdn.net [66.185.151.151]
13 96 ms 97 ms 96 ms Qwest.atdn.net [66.185.139.218]
14 105 ms 104 ms 102 ms dcx-core-01.inet.qwest.net [205.171.251.33]
15 * * * Request timed out.
16 130 ms 131 ms 131 ms nap-edge-01.inet.qwest.net [205.171.27.50]
17 135 ms 132 ms 134 ms 65.124.216.54
18 133 ms 136 ms 137 ms miaswr001-g5-1.mia.affinity.com [216.219.251.190]
19 142 ms 140 ms 141 ms 207.234.128.45
20 138 ms 137 ms 145 ms vzlin1.primarydns.com [72.4.174.4]
21 141 ms 137 ms 138 ms 72-4-174-108.ptr.primarydns.com [72.4.174.108]

Trace complete.

[lgieg]

Performance is fine this morning, even though it looks like the routing is the same. Maybe it's a congested link, but seems to me that enough congestion to cause latency to increase sevenfold is something that should be corrected.

Tracing route to www.poopvortex.com [72.4.174.108]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 172.19.97.1
2 9 ms 6 ms 7 ms 10.47.192.1
3 6 ms 8 ms 11 ms ge0-3.nycmnys-ubr9.nyc.rr.com [24.29.104.169]
4 6 ms 8 ms 7 ms 24-29-100-13.nyc.rr.com [24.29.100.13]
5 8 ms 9 ms 8 ms 24-29-104-202.nyc.rr.com [24.29.104.202]
6 9 ms 7 ms 6 ms pos4-0-nycmnyl-rtr1.nyc.rr.com [24.29.100.85]
7 8 ms 8 ms 7 ms tenge10-0-0.nycmnyrdc-rtr1.nyc.rr.com [24.29.119.117]
8 7 ms 7 ms 8 ms tenge2-1-0.nycmnyrdc-rtr2.nyc.rr.com [24.29.119.146]
9 8 ms 15 ms 9 ms pop2-nye-P11-0.atdn.net [66.185.146.21]
10 11 ms 9 ms 8 ms bb1-nye-P1-0.atdn.net [66.185.151.64]
11 14 ms 15 ms 14 ms bb2-ash-P10-0.atdn.net [66.185.152.87]
12 16 ms 13 ms 14 ms pop2-ash-P3-0.atdn.net [66.185.151.151]
13 15 ms 14 ms 13 ms Qwest.atdn.net [66.185.139.218]
14 14 ms 20 ms 15 ms dcx-core-01.inet.qwest.net [205.171.251.33]
15 * * * Request timed out.
16 51 ms 51 ms 50 ms nap-edge-01.inet.qwest.net [205.171.27.50]
17 52 ms 50 ms 52 ms 65.124.216.54
18 48 ms 47 ms 50 ms miaswr001-g5-1.mia.affinity.com [216.219.251.190]
19 107 ms 48 ms 52 ms 207.234.128.45
20 49 ms 48 ms 49 ms vzlin1.primarydns.com [72.4.174.4]
21 49 ms 52 ms 49 ms 72-4-174-108.ptr.primarydns.com [72.4.174.108]

Trace complete.