Any plans to address severe server issues?

[reiichi]

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

What do I do with this?

From a traceroute perspective, that all looks pretty good. None of them timed out in the middle and a ping of 40-50ms is what most people would refer to as "extremely good." (While SE claims the game will work fine with 200ms and better, I'd probably still shoot for 150ms or lower myself for a smoother experience.)

It's probably safe to say that NTT is still getting DDoSed though, which can cause issues all around. I have an almost perfect route to the datacenter and yesterday was spotty here and there.

[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.

[Baingoleth]

I am experiencing this right now. There is an attack at ae-41.r02.snjsca04.us.bb.gin.ntt.net

Tracing route to 204.2.229.88 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.254
  2     2 ms     2 ms     2 ms  10.252.10.1
  3    16 ms    16 ms    16 ms  154.11.12.203
  4    46 ms    48 ms    45 ms  sea-b2-link.telia.net [213.248.74.220]
  5    55 ms    57 ms    55 ms  ntt-ic-327522-sea-b2.c.telia.net [80.239.195.59]
  6    56 ms    55 ms    55 ms  ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
  7    46 ms    46 ms    47 ms  ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
  8    68 ms    69 ms    70 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
  9   879 ms   851 ms   900 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 10     *      368 ms     *     ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
 11   345 ms    93 ms    72 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 12    72 ms     *       72 ms  204.2.229.234
 13    72 ms    72 ms    72 ms  204.2.229.88

[Baingoleth]

Another NOC post about this:

http://forum.square-enix.com/ffxiv/t...8Nov.-10-11%29

[Baingoleth]

Just happened again. Same hop:

Tracing route to 204.2.229.88 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.254
  2     2 ms     2 ms     2 ms  10.252.10.1
  3    17 ms    16 ms    16 ms  154.11.12.203
  4    48 ms    45 ms    46 ms  sea-b2-link.telia.net [213.248.74.220]
  5    55 ms    55 ms    55 ms  ntt-ic-327522-sea-b2.c.telia.net [80.239.195.59]
  6    55 ms    55 ms    55 ms  ae-9.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.117]
  7    60 ms    46 ms    46 ms  ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.7]
  8    68 ms    68 ms    68 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
  9     *        *      907 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 10     *        *        *     Request timed out.
 11    73 ms    72 ms    72 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 12     *       72 ms    71 ms  204.2.229.234
 13    72 ms    73 ms    76 ms  204.2.229.88