This is not a DDOS, Tell the truth SE.

[Catwho]

If its not DDoS attacks, it's NTT being an absolute dog's arse of a ISP.

Usually when it's an NTT node acting up (looking at you, San Jose) it only impacts certain ISPs. For about six months a few years ago Charter/Spectrum had massive problems with that node, then suddenly one day they resolved.

This is instead a direct blast on the data center that hosts XIV, knocking the instance servers offline specifically. The lobby servers are actually okay. If you get a 9002 and wait about 30-60 seconds before attempting to reconnect, you can get back in without the 2002 (which happens if you try to reconnect too fast.)

These narrow, specific crashes mean it's either:
1. A DDoS attack targeting the instance servers specifically OR

2. The actual data center hardware for the instance server is dying, like a bad switch or something.

If the latter was true, they'd get the blinky lights notifying them of the problem right away and it's easy to do a hardware swap. Commercial hardware warranties are 5 years, so its not a matter of money if a thing dies early.

For me, that rules out #2.

[Shipp]

Usually when it's an NTT node acting up (looking at you, San Jose) it only impacts certain ISPs. For about six months a few years ago Charter/Spectrum had massive problems with that node, then suddenly one day they resolved.

This is instead a direct blast on the data center that hosts XIV, knocking the instance servers offline specifically. The lobby servers are actually okay. If you get a 9002 and wait about 30-60 seconds before attempting to reconnect, you can get back in without the 2002 (which happens if you try to reconnect too fast.)

These narrow, specific crashes mean it's either:
1. A DDoS attack targeting the instance servers specifically OR

2. The actual data center hardware for the instance server is dying, like a bad switch or something.

If the latter was true, they'd get the blinky lights notifying them of the problem right away and it's easy to do a hardware swap. Commercial hardware warranties are 5 years, so its not a matter of money if a thing dies early.

For me, that rules out #2.

The boots haven't knocked me offline once. It leads me to believe it is an attack on one of the ISP nodes instead of the servers themselves. I've maintained connection every single mass DC.

[TaleraRistain]

Usually when it's an NTT node acting up (looking at you, San Jose) it only impacts certain ISPs. For about six months a few years ago Charter/Spectrum had massive problems with that node, then suddenly one day they resolved.

This is instead a direct blast on the data center that hosts XIV, knocking the instance servers offline specifically. The lobby servers are actually okay. If you get a 9002 and wait about 30-60 seconds before attempting to reconnect, you can get back in without the 2002 (which happens if you try to reconnect too fast.)

These narrow, specific crashes mean it's either:
1. A DDoS attack targeting the instance servers specifically OR

2. The actual data center hardware for the instance server is dying, like a bad switch or something.

If the latter was true, they'd get the blinky lights notifying them of the problem right away and it's easy to do a hardware swap. Commercial hardware warranties are 5 years, so its not a matter of money if a thing dies early.

For me, that rules out #2.

Yep and AT&T was affected by that node for some time when our turn came around and Verizon experienced it. It hits certain ISPs at different times. And then just clears up one day. There's a huge thread about it on the tech forums.

That node is notorious but usually causes massive lag and not constant disconnects. Constant disconnects are usually DDoS. And you're right about the lobby servers. If you give it a second before trying to go back in you can usually get by without the lobby server crashing on you.