dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed



Bad routing in Qwest backbone.

A server I frequently communicate with is having an issue with one of Qwest's routers. The server is in Georgia, and I am in Arizona. When I run a traceroute, the data goes out of the US, into Europe, then back through Seattle to Georgia, causing relatively high latency.

What would be the proper channel to communicate this issue to? I wouldn't think basic tech support would be much help, especially since I'm not a Qwest customer.

For those interested, here's my full trace:
  1    1 ms    1 ms    1 ms  Flagstaff []
  2     7 ms    15 ms     8 ms
  3     *        *        *     Request timed out.
  4    19 ms    15 ms    22 ms
  5    77 ms    69 ms    73 ms  phn-edge-05.inet.qwest.net []
  6    73 ms    65 ms    72 ms  lap-brdr-03.inet.qwest.net []
  7    56 ms     *       52 ms
  8    88 ms    93 ms    93 ms  ash-bb1-link.telia.net []
  9    93 ms     *       89 ms  internap-ic-140171-ash-bb1.c.telia.net []
 10    99 ms    95 ms    94 ms  border1.pc2-bbnet2.wdc002.pnap.net []
 11     *      137 ms   143 ms

As far as I can tell, hops 8 and 9 are in Europe.

Premium,Ex-Mod 2003-9
How did you determine that lines 8 & 9 are in Europe? Try a trace route to www.telia.net and see if there is any difference in trace route times.
Front Range Mountain Bike Patrol - »www.frmbp.org
Go4it2day Web Services - »www.go4it2day.com


Moline, IL
reply to Crazydog
Hops 8 and 9 aren't in Europe, they appear to be on the East Coast of the US. If they were in Europe you would see much higher increases in latency. As for fixing the problem, there's really nothing you can do about it other than possibly changing service to another ISP that doesn't use Qwest for transit.

Aurora, CO
reply to Crazydog
I think you may be mistaking the company that operates the router being based in Europe with the router being in Europe (a 30ms hop to Europe or back is very unlikely.)
If you’re greener than Gore, you’re green enough.


Boise, ID
reply to Crazydog
There's also the issue of asymmetrical routing that could be taking place. I don't usually see issues going through Telia (which operates a network both here in the US, and in Europe as well), but rather GlobalCrossing (GBLX).

Since Qwest is too lame to bother to offer IPv6 to their residential customers who want it, I have to use Hurricane Electric's tunnel broker system, which unfortunately needs to traverse GBLX's network.

As soon as I hit GBLX, latency jumps from 50ms to over 110ms. Paths _from_ HE to me on Qwest take Telia exclusively, and don't show the huge latency changes.

This creates a rather crappy IPv6 experience. :-/
http://www.sosdg.org / http://brielle.sosdg.org