connection errors

[Vateri]

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.

[Strider_xiii]

Here it is with the vpn set to ny which works

4 31 ms 13 ms 7 ms be6080.ccr31.jfk04.atlas.cogentco.com [38.104.72.1]
5 18 ms 9 ms 7 ms be3363.ccr42.jfk02.atlas.cogentco.com [154.54.3.125]
6 13 ms 8 ms 7 ms be3496.ccr31.jfk10.atlas.cogentco.com [154.54.0.142]
7 17 ms 11 ms 9 ms ae-13.r01.nycmny17.us.bb.gin.ntt.net [129.250.8.145]
8 18 ms 9 ms 11 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
9 39 ms 40 ms 35 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 34 ms 32 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
11 98 ms 91 ms 83 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 90 ms 99 ms 82 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 82 ms 78 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 81 ms 81 ms * 204.2.29.241
15 81 ms 79 ms 83 ms 204.2.29.122

[DDRDiesel]

Here it is with the vpn set to ny which works

4 31 ms 13 ms 7 ms be6080.ccr31.jfk04.atlas.cogentco.com [38.104.72.1]
5 18 ms 9 ms 7 ms be3363.ccr42.jfk02.atlas.cogentco.com [154.54.3.125]
6 13 ms 8 ms 7 ms be3496.ccr31.jfk10.atlas.cogentco.com [154.54.0.142]
7 17 ms 11 ms 9 ms ae-13.r01.nycmny17.us.bb.gin.ntt.net [129.250.8.145]
8 18 ms 9 ms 11 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
9 39 ms 40 ms 35 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 34 ms 32 ms 37 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
11 98 ms 91 ms 83 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 90 ms 99 ms 82 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 82 ms 78 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 81 ms 81 ms * 204.2.29.241
15 81 ms 79 ms 83 ms 204.2.29.122

Thanks, that's a huge help with your other post. It seems when you're on the VPN, which is functional, you aren't going through the nodes owned by twelve99, but playing normally you're being routed through them then back to the NTT pathing. So it's hard to say if the NTT node is actually the problem or if it's a forwarding issue from the twelve99 nodes to the NTT nodes thereafter. This is something that has to be looked at and investigated by SE and their L2/L3 backbone partners, unfortunately I won't be able to investigate much further as that's where the general population's access stops

[DDRDiesel]

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.

It's a tough answer to come up with, as there's still not a specific problem we as the general public can identify. I'm able to investigate enough to give a general idea of where to start, but this now is up to SE and their backbone partners to isolate. Reading through Strider's posts gives me an idea of where the issue might lie, but it's still a list of nearly a dozen potential issues that they have to solve on their end.

I'd say continue to let SE support know, and direct them to this thread in particular. There's plenty of usable information here among all the complaining, and hopefully it will eventually be seen by someone that can escalate it enough to begin a proper investigation into the issue

[Vateri]

It's a tough answer to come up with, as there's still not a specific problem we as the general public can identify. I'm able to investigate enough to give a general idea of where to start, but this now is up to SE and their backbone partners to isolate. Reading through Strider's posts gives me an idea of where the issue might lie, but it's still a list of nearly a dozen potential issues that they have to solve on their end.

I'd say continue to let SE support know, and direct them to this thread in particular. There's plenty of usable information here among all the complaining, and hopefully it will eventually be seen by someone that can escalate it enough to begin a proper investigation into the issue

So what should I tell support exactly? I'm not network savvy enough and do not want to use the wrong language. Please give me a general thing I can say, and then link them this thread for reference. Nothing will be done unless we can flag a community rep in here.

[TiliniFashonti]

I was having repeated issues trying to log in on my main last night, sometimes getting bounced from title screen with 90002 or 2002 errors, and sometimes being bounced after selecting my main on Jenova and making it to the loading screen, then receiving a 10105 error. I was able to log in after approximately 40 minutes of this cycle by selecting a Japanese data center (Meteor) where I had no characters, fully exiting the game, then relaunching and selecting Aether, but I understand that this might be a fluke fix.

Unfortunately tried this again today and no dice, still having trouble logging in/connecting and am unable to do so.

[DDRDiesel]

So what should I tell support exactly? I'm not network savvy enough and do not want to use the wrong language. Please give me a general thing I can say, and then link them this thread for reference. Nothing will be done unless we can flag a community rep in here.

Basically open with the usual problem. Let them know the issues is widespread among players located in the East Coast US. Then after they give you the usual copy/paste answer, send them a link to this thread and tell them there's a ton of information already available for them to start an investigation

[wizisi2k]

I'm chiming in as someone from NJ as well on Optimum. I decided to also try using T-mobile hostpot to connect because I am a homeowner and was able to world visit to faerie and back-doing a run of Puppet's Bunker while I was over there. Oddly enough, the tracert I did on hotspot timed out for 17 hops after the first hop before ending at the lobby server. I dunno if I was lucky but the fact that the routing might be different would be notable as not going through that NTT hop. I think the issue is probably going to be islolated to the northeast unless routing takes everyone on the East Coast through that node resulting in more people chiming in

[Vateri]

I'm chiming in as someone from NJ as well on Optimum. I decided to also try using T-mobile hostpot to connect because I am a homeowner and was able to world visit to faerie and back-doing a run of Puppet's Bunker while I was over there. Oddly enough, the tracert I did on hotspot timed out for 17 hops after the first hop before ending at the lobby server. I dunno if I was lucky but the fact that the routing might be different would be notable as not going through that NTT hop. I think the issue is probably going to be islolated to the northeast unless routing takes everyone on the East Coast through that node resulting in more people chiming in

I am also a NJ resident with Optimum

[ShanksFCS]

Another NJ resident on Optimum here. I'm glad I'm not the only one having this issue! I haven't been able to log in all day. Continually getting 2002 lobby server errors. The rare times I get past character selection, I'm unable to load the zone and I get bounced with a 10105 error.

The issues started sometime in the last couple days for me. I was able to log in at some point yesterday for a few hours, then I got booted at night and haven't been able to get back in.