Atlanta Lag

[Wizz]

Just have a question about the Atlanta location.

Is there a issue going on with this location because for the past few days we have been experencing lag spikes and our pings have doubled. I did see in my event log about a customer did a ddos.

Today our lag spikes and well lagging out started about 4 PM EST.

Also just wondering if any other Atlanta clients are having any issues.

Thanks

Wizz

[Vanderburg]

We aren't seeing any other reports about this, but if you are able to take a trace route from your PC to your game server, we'd be happy to take a look at routing as a possible cause, or other troubleshooting options.

[perfect]

Mine has been really high in the last week or so as well. It seems to have just now resolved itself. Probably within the last 30 minutes. I'm in Tallahassee, FL connecting to a server in Atlanta.

I didn't save a trace route from when it was laggy, but it wasn't just me experiencing the lag. Other people connecting to the server reported pings that were about 3x their normal averages.

Here's the ping / trace route from a little while ago.

Code: Select all

Pinging madmangaming.game.nfoservers.com [74.91.127.30] with 32 bytes of data:
Reply from 74.91.127.30: bytes=32 time=31ms TTL=116
Reply from 74.91.127.30: bytes=32 time=31ms TTL=116
Reply from 74.91.127.30: bytes=32 time=45ms TTL=116
Reply from 74.91.127.30: bytes=32 time=31ms TTL=116

Ping statistics for 74.91.127.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 45ms, Average = 34ms

Tracing route to madmangaming.game.nfoservers.com [74.91.127.30]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2    26 ms    29 ms    29 ms  50.156.167.1 
  3    12 ms    10 ms    10 ms  te-9-2-ur01.etharpest.fl.tallah.comcast.net [68.87.161.37] 
  4    12 ms     9 ms    24 ms  68.86.198.13 
  5    12 ms    10 ms    11 ms  te-6-7-ar01.l3-tallahas.fl.northglf.comcast.net [68.86.181.10] 
  6    18 ms    19 ms    19 ms  te-2-0-0-10-cr01.56marietta.ga.ibone.comcast.net [68.86.93.9] 
  7    15 ms    16 ms    16 ms  64.209.97.13 
  8    17 ms    17 ms    18 ms  te2-4-10G.ar5.ATL1.gblx.net [67.16.157.166] 
  9    33 ms    31 ms    61 ms  Internap-Atlanta.TenGigabitEthernet3-4.ar5.ATL1.gblx.net [207.218.80.218] 
 10    29 ms    31 ms    31 ms  border10.tge4-1-bbnet2.acs.pnap.net [64.94.0.76] 
 11    29 ms    30 ms    30 ms  c-74-91-127-30.internap-atlanta.nfoservers.com [74.91.127.30] 

Trace complete.

[Edge100x]

perfect, your trace indicates that you're still seeing a problem that Internap may be able to work around for you. Please contact us directly about this and provide the traceroute and IP address.

Comcast has been having a lot of problems in the Atlanta area for the last week or so, and we've had to ask Internap to switch many customers to different providers on the outbound.

[perfect]

Hi Edge100x,

I just sent an email to support@nfoservers.com with an updated ping and trace route. Turns out the ping has gone back up to the 70 ms range. Last night it was working fine at around 29-31 ms, which is still just a tad higher than what I'm used to seeing a few weeks ago.

Hopefully we can pinpoint the problem!

Thanks,
perfect

[combineelite]

Exact same issue.

[Edge100x]

The specific Comcast problem that we were seeing before should be worked around by Internap. But, we will be able to look at your situation if you contact us directly. With routing concerns, please always contact us directly with your MTR to the server and client IP address.