Network connectivity to Atlanta

[Ron]

There is a network issue currently affecting Atlanta. I am seeing an approximate 20% packet loss using WinMTR set at 5 second intervals.

Support is aware of the issue.

[wuurp]

Hmm... maybe that explains why the command line, or editing a file is so type and wait today.

But I'm also seeing it on a server in Houston.

[Gwaihir]

I'm seeing it on Atlanta only (and the traceroute puts it inside Gnax).

[Rob]

There is a problem with the carrier Global Crossing

[Daniel_DBS]

GAH! Ok I just got done experiencing down DNS servers through Comcast, talk about a pain in the @$$!

Anywho... It seems that GNAX shutdown the Global Crossing uplink

[Daniel_DBS]

Yep, I just did a Tracert... Normally when using my Sprint aircard, i was routed using Global Crossing. I just did a test with the card and instead of going straight to GNAX through Global Crossing, it took a side trip. The route went from sprint to global crossing and then from global crossing to "Beyond the Network America, Inc." (which I've never heard of before) Then from that link into GNAX...

[EuroNut]

The route went from sprint to global crossing and then from global crossing to "Beyond the Network America, Inc." (which I've never heard of before) Then from that link into GNAX...

Beyond the Network = pccwbtn ... and I'm getting some real nice speeds in and out of Atlanta now

[Daniel_DBS]

Beyond the Network = pccwbtn ... and I'm getting some real nice speeds in and out of Atlanta now

Ahhh... I'm slow... Long night, been dealing with down DNS through my ISP as well as a down server... GAH!

[Robert Vining]

I have been dealing with this since I signed up on December 27. Download speeds when they are good are around 1.1 MB per second on a 6MB comcast connection... then most of the time they drop to 200k per second... like now.

Seems pccwbtn is the culprit...

Tracing route to server.robertswebdesign.net [69.73.139.245]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 9 ms 6 ms 73.211.24.1
3 9 ms 7 ms 8 ms 68.85.248.89
4 10 ms 10 ms 13 ms 68.85.244.65
5 9 ms 9 ms 10 ms 68.85.244.46
6 12 ms 28 ms 12 ms 68.85.244.73
7 12 ms 13 ms 12 ms 68.85.244.154
8 18 ms 17 ms 20 ms pos-0-14-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.153]
9 39 ms 39 ms 40 ms 64.209.97.14
10 60 ms 76 ms 76 ms 64.209.97.13
11 59 ms 76 ms 76 ms 64.209.97.74
12 91 ms 101 ms 101 ms gnax.ge2-13.br01.atl01.pccwbtn.net [63.216.31.13
0]
13 107 ms 101 ms 101 ms 209.51.131.90
14 98 ms 101 ms 101 ms eclipse.nocdirect.com [69.73.141.135]
15 86 ms 87 ms 86 ms server.robertswebdesign.net [69.73.139.245]

Trace complete.

[EuroNut]

Seems pccwbtn is the culprit...

What makes you say that? I'm currently pulling some backups down from one of my boxes at Jag to the UK, along pccwbtn all the way @ 2583kbps average, 2124kbps minimum. The same box at Jag is also feeding some other files down my older 2mbps DSL and it's max'd out at 242kbps without a blip (down Telia on that one).

[Daniel_DBS]

Yes, pccwbtn is giving me some of the best speeds as well... I am normally routed from savvis to global crossing, now i am being routed in through pccwbtn since GC was shut down

[Robert Vining]

Just looking at hop 12 above in the trace... where would you say the slow down is?

[Daniel_DBS]

Well, hops 12-15 have a lot of high response times...

You seem to have a lot of hops... I only hope 7 or 8 times, and 3 of those are inside the NAP.

[Robert Vining]

well 1-7 are all just getting out of Houston...

[EuroNut]

The response time of each individual hop doesn't tell you its capacity for carrying your traffic. All it really tells you is how long it takes to respond to the equivalent of a ping and a who-are-you request. Many routers and switches are set-up to DELAY responses like that because that's not what they're there for - They're there to shift traffic.

You are better off casting around for opinions on speed from similar users like yourself, preferably on Comcast, and in the same sort of area as you. When you asked, I was getting motorway speed down pccwbtn from GNAX to the UK.

Tracerts are good for telling you how your data gets from point A to point B, but they're a lot less useful when it comes to telling you how fast your data will travel down that route. Any one link between 2 hops on the route from you to Atlanta (especially nearer to you) could be a lousy 100mbps connection being choked by another 1000 Comcast users hooked into YouTube and Microsoft Update

The fact that your speed was jumping up and down is another sign of this - My download at the same time was from data-center to data-center, so I was on a big trans-Atlantic pipe and my speed help pretty steady for the hour that I was sucking files down.