Unusual Lag Spikes?

[Kurogaea]

Still getting it. It appears to happen around night time. Server congestion maybe?

[szalkerous]

Not sure if this is a related issue....

http://www.theregister.co.uk/2015/11...eported_in_us/

[szalkerous]

Still getting it. It appears to happen around night time. Server congestion maybe?

No, it's been pretty much sleuthed out to be a problem with the Level3 backbone.

[Meirii]

been like this for me since the last hotfix, not sure thats going on but omg is the lag bad.
This is the first time I have had lag issues with the game

[Kalsoa]

This is making Void Ark impossible, everyone is lagging horribly at Cuchulainn and wiping over and over.

[Tonberrian]

Still practically unplayable here as well going on 4 days now (started monday) on Behemoth server. Most of my FC is experiencing the same lag spikes. I've heard using a VPN can alleviate the lag, but I'd rather play my game without third party software involved, getting to be bothersome!

[Coldbrand]

The server hates the Diadem nerfs and is rebelling. Also I'm getting hit with massive lag over the past couple days as well and don't know why. Excalibur, again.

[KaijinRhada]

Still getting lag spikes, but I'm not with Comcast (Shaw is my ISP, western Canada). Nothing to report from their end, and I don't experience lag any where else.

[szalkerous]

Still getting lag spikes, but I'm not with Comcast (Shaw is my ISP, western Canada). Nothing to report from their end, and I don't experience lag any where else.

It's all about who your ISP teams up with as a backbone provider. If you do a tracert from you to the server IP, I bet you'll find Level3 in there around hop 6 or 7. That seems to be a common denominator as people with them in their routing can VPN around it and avoid the dropped packets entirely.

Here's an example of hops 5-12 for me on Comcast in the Boston area, headed to the Excalibur server (on a good day):

  5    15 ms    11 ms    16 ms  be-77-ar01.needham.ma.boston.comcast.net [68.87.146.194]
  6    10 ms    10 ms    14 ms  4.68.71.217
  7    44 ms    42 ms    45 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
  8    40 ms    38 ms    41 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
  9    39 ms    39 ms    42 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
 10    57 ms    56 ms    56 ms  192.34.76.10
 11    56 ms    57 ms    54 ms  199.91.189.242
 12    57 ms    54 ms    57 ms  199.91.189.45

During this lag, hops 8-12 (for me, your results may vary) will have extremely high response or will drop entirely. It's even easier to do a 100 count ping to the server and compile the packet loss percentage from that.

C:\>ping 199.91.189.45 -n 100

...

Ping statistics for 199.91.189.45:
    Packets: Sent = 100, Received = 93, Lost = 7 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 64ms, Average = 55ms

You should have 0% loss if things are working correctly. I've been seeing between 5 and 20 percent loss during evening primetime this week.

[Raist]

7    44 ms    42 ms    45 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
8    40 ms    38 ms    41 ms  ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

Oh that pesky level3 car2 hop, when will they ever fix that route? It's been showing up in buggered routes for years