traceroute showing packet loss to lobby server on SE's own network

[renachi]

I know this is probably going to get buried in the all the angry posts from people that cant log in, but hopefully someone in SE support reads it to help get the issue fixed.

79 ms 80 ms * 204.2.229.230

When running tracerouts to the Crystal lobby server(204.2.229.11) I am getting problems on the hop right before the lobby almost every trace(I have run over 50 of them at this point and maybe 2 didnt have any issues showing). I have also had problems pop up on multiple hops within NTT.net servers, which appears to be SE's ISP for the NA servers. I checked to each NA lobby server, all of them go to 204.2.229.230 as the hop right before the lobby itself
I have ran tracerts with an without a VPN running. I tried setting the VPN location to various parts of the country and the route always has to go through 204.2.229.230 and that hop finds issue more often than not. different cities get different sets of NTT.net servers on the way to the lobby, and most traces are clear through the NTT.net hops, but they have issues far more often than they should so it appears something is going wrong with their systems.

The server on 204.2.229.230 definitely has an issue though, and that is likely causing the drops from people waiting in queue.

Please fix this server so we can actually get into your game!

[Khartina]

I can confirm these results, WinMTR to 204.2.229.11 has a perfect connection until the second to last hop 204.2.229.230 which has SIGNIFICANT packet loss.

Ping to NTT.net also has a perfect signal except for the second to last hop (same 204.2.229.230).

SE's servers are on fire and it's showing.