Quote Originally Posted by DDRDiesel View Post
New info

After getting some more details from friends of mine who happened to stumble across this thread, I saw that the next hop after the node located in NYC is a node located in Hoboken, NJ. The node designation is ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]. Here is the WHOIS information for the node. Yep, another NTT node. I tried pinging and running a tracert to this node in particular and both failed spectacularly.

It's my belief that this is where the failure is occurring for East Coast players. NTT is a network company contracted by SE for pathing to their datacenters, and this is where the failure appears to consistently occur. As such, SE is responsible for working with the vendor in getting this node back up and running. As a playerbase we should not have to rely on a VPN to connect to a service when SE is responsible for the networking in the first place
What should we do? Should we all contact support and mention the aforementioned Hoboken node? They seem pretty content just pushing blame and not fixing anything. Would rather not pay for a VPN on top of sub fees for something on their end, but I’m also pessimistic with them giving a darn about this.