Any plans to address severe server issues?

[Baingoleth]

So, I did a traceroute and it looks like it's probably a mess on my end...

What do I do with this?

That traceroute looks good except for 100ge10-2.core1.yvr1.he.net. 2 responses took 17ms and one response took 71ms. That's not terrible but not something I'd like to see so early in the route. That router belongs to Hurricane Electric, Inc.

A few questions. Did you run the traceroute at the time you were experiencing trouble? If you run the traceroute multiple times, is there always jitter like this on that hop? What if you do a "ping 184.105.64.113" a few times? Does the ping time vary a lot with that hop?

If all your traces keep coming up looking okay within the ntt.net hops, you aren't affected by this DDoS problem that people are reporting.

[eternalstar01]

A few questions. Did you run the traceroute at the time you were experiencing trouble? If you run the traceroute multiple times, is there always jitter like this on that hop? What if you do a "ping 184.105.64.113" a few times? Does the ping time vary a lot with that hop?

If all your traces keep coming up looking okay within the ntt.net hops, you aren't affected by this DDoS problem that people are reporting.

Sadly not, I was logged out of the game when I ran it... Would have been a great idea to run it during a spike! Today seems to be a lot smoother. No spikes yet, even in a DF.