dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed


Chicago, IL

Chicago Routing is WACKED! This needs to be fixed ASAP!

I'm bascially in Chicago and i played a lot of Quake3, and when I ping or connect to my favorate server for the past 3 years i've had a nice 12-19ms ping because this server is in Chicago Also.

The past month it's risen up to 30ms, and today it's 50-60ms.

Looks at this TraceRoute: Not only does it go Through quest where it's spiking bad, and jump on to 30-50ms, but then it's routed through New York, then back here to Elk Grove in Illinois. Excuse my french! haha but why the hell if I'm in Chicago, and the POP is in Chicago, am I being routed through Quest & New York to connect to another server in Chicago!!!

traceroute to 87-97-182-64.cust.propagation.net (, 30 hops max, 46 byte packets
1 ( 0.984 ms 0.942 ms 0.879 ms
2 er1.chi1.speakeasy.net ( 13.930 ms 13.036 ms 13.101 ms
3 220.ge-0-1-0.cr2.chi1.speakeasy.net ( 11.506 ms 23.980 ms 19.376 ms
4 chx-edge-01.inet.qwest.net ( 54.999 ms 11.455 ms 10.802 ms
5 cer-core-02.inet.qwest.net ( 11.305 ms 11.447 ms 10.835 ms
6 * * *
7 ewr-brdr-01.inet.qwest.net ( 31.945 ms 31.807 ms 32.061 ms
8 dcr3-so-3-1-0.newyork.savvis.net ( 32.484 ms 55.534 ms 31.575 ms
9 bcs2-so-1-1-0.NewYork.savvis.net ( 31.774 ms bcs1-so-1-1-0.NewYork.savvis.net ( 31.605 ms bcs2-so-3-0-0.NewYork.savvis.net ( 31.936 ms
10 dcr1-so-1-0-0.Chicago.savvis.net ( 54.538 ms dcr2-so-3-0-0.Chicago.savvis.net ( 55.525 ms dcr1-so-1-0-0.Chicago.savvis.net ( 55.044 ms
11 ber1-pos-7-0-0.Chicago.savvis.net ( 53.723 ms dcr2-so-5-0-0.Chicago.savvis.net ( 54.053 ms dcr1-so-5-0-0.chicago.savvis.net ( 53.587 ms
12 ber1-vlan-241.chicagoequinix.savvis.net ( 54.558 ms ber2-vlan-242.chicagoequinix.savvis.net ( 55.702 ms ber2-pos-7-0-0.Chicago.savvis.net ( 54.063 ms
13 ber1-vlan-241.chicagoequinix.savvis.net ( 53.794 ms 53.767 ms ber2-vlan-242.chicagoequinix.savvis.net ( 56.160 ms
14 bhr1-pos-0-0.ElkGrovech3.savvis.net ( 56.189 ms 55.318 ms bpr1-ge-2-3-0.chicagoequinix.savvis.net ( 54.721 ms
15 bhr1-pos-0-0.ElkGrovech3.savvis.net ( 55.513 ms * *


Chicago, IL

I'm guessing this was a temporary issue with the peering between Qwest & Savvis in Chicago, causing traffic to be routed to NY. I'm in Chicago and got this traceroute:

3 16ms 15ms 15ms 220.ge-0-1-0.cr2.chi1.speakeasy.net []
4 14ms 14ms 15ms chx-edge-01.inet.qwest.net []
5 14ms 13ms 14ms cer-core-02.inet.qwest.net []
6 14ms 13ms 13ms chp-brdr-02.inet.qwest.net []
7 14ms 13ms 12ms ber1-ge-7-3.chicagoequinix.savvis.net []
8 12ms 12ms 12ms bpr1-ge-7-0-0.chicagoequinix.savvis.net []
9 14ms 16ms 13ms bhr1-pos-0-0.ElkGrovech3.savvis.net []


Chicago, IL

The routing through Quest on the 3rd and 4th Hop:

4 chx-edge-01.inet.qwest.net ( 54.999 ms 11.455 ms 10.802 ms
5 cer-core-02.inet.qwest.net ( 11.305 ms 11.447 ms 10.835 ms

has not changed muched, i'm still getting 30-40 ms connecting to Local Chicago Servers from chicago, where as for the past 5 years i've been getting 8-12 ms ping time. this is really got me upset on this awful routing. If quest using interleaving or error checking or something, thats the only things that jumps ping times up like this.

Pittsburgh, PA
·Verizon FiOS

There was a problem with the Cogent network yesterday that seemed to trickle down to Cogent's other peers. One of the peers that had problems was Savvis.

After noticing weird Cogent routing problems yesterday I checked with internet health report. I have not seen that much red since the level3 fiasco.

I still don't know what happened out there with Cogent. On the 14th of February, the fiber had become severed in New York.

Des Plaines, IL

The word on the street here in the Chicago colo market is that Cogent might have the best prices, but at the expense of reliability. Call this an extreme example.

I'd like to know what freak of networking caused what should have been a 16 block hop from CHX to Equinix to suddenly head for New York, going right past Equinix along the way. That area is crazy-full of fiber. That is truly screwy!


Chicago, IL
reply to Mandr4ke


That increase on hop 4 doesn't indicate it problem, it just indicates that Qwest's router is likely deprioritizing ICMP ping packet requests (which is the way many routers are configured). Does the full trace show higher than normal latency at the destination?


Chicago, IL
reply to Mandr4ke

Hmm seems like chicago is getting better now, quest seems to be back to 10ms.. but once it's jumping into att.net i'm timing out after 10 hops. Must be thoese Secret NSA Rooms that AT&T routes all traffic through screwing up all my ping times now. haha Still thought something is very intermentant. when i ping a server it say 15 ms, when i jump on i get 40ms, and i see the net graphic ging very unstable and choppy like lots of packet loss almost, but just spikes and a delay. Nasty!