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.

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

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

[DDRDiesel]

Update from support

I spent a good 15-20 minutes working with support earlier. I was on the phone with a rep named Daniel and then in chat with a rep named Eddy. Both reps were receptive of what I had to say and I made sure to give them as much information as I possibly could. Daniel let me know that they've been receiving these calls in increasing volume since around 10 AM EST yesterday (Wednesday) morning. I directed him to this post and made sure to let him know that there is more than enough information here to start a proper investigation. I also provided him with the NTT node information such as geolocation and IP address.

It took a bit of doing, but I eventually was able to convince both reps that this was not an ISP issue with Optimum, since they don't have ownership of the node and there is no other internet-related problems, they just happen to have a very large market share in the area which is why most of the complaints have that in common.

I was informed that the information was forwarded to the relevant teams to investigate and hopefully we'll see an official acknowledgement of the issue within the next day by way of a Lodestone post or maybe even a resolution. Keep fingers crossed and please be sure to post any new information if it's available!

[Hav3nsblade]

Update from support

I spent a good 15-20 minutes working with support earlier. I was on the phone with a rep named Daniel and then in chat with a rep named Eddy. Both reps were receptive of what I had to say and I made sure to give them as much information as I possibly could. Daniel let me know that they've been receiving these calls in increasing volume since around 10 AM EST yesterday (Wednesday) morning. I directed him to this post and made sure to let him know that there is more than enough information here to start a proper investigation. I also provided him with the NTT node information such as geolocation and IP address.

It took a bit of doing, but I eventually was able to convince both reps that this was not an ISP issue with Optimum, since they don't have ownership of the node and there is no other internet-related problems, they just happen to have a very large market share in the area which is why most of the complaints have that in common.

I was informed that the information was forwarded to the relevant teams to investigate and hopefully we'll see an official acknowledgement of the issue within the next day by way of a Lodestone post or maybe even a resolution. Keep fingers crossed and please be sure to post any new information if it's available!

the real MVP

[Ostheim89]

Update from support

I spent a good 15-20 minutes working with support earlier. I was on the phone with a rep named Daniel and then in chat with a rep named Eddy. Both reps were receptive of what I had to say and I made sure to give them as much information as I possibly could. Daniel let me know that they've been receiving these calls in increasing volume since around 10 AM EST yesterday (Wednesday) morning. I directed him to this post and made sure to let him know that there is more than enough information here to start a proper investigation. I also provided him with the NTT node information such as geolocation and IP address.

It took a bit of doing, but I eventually was able to convince both reps that this was not an ISP issue with Optimum, since they don't have ownership of the node and there is no other internet-related problems, they just happen to have a very large market share in the area which is why most of the complaints have that in common.

I was informed that the information was forwarded to the relevant teams to investigate and hopefully we'll see an official acknowledgement of the issue within the next day by way of a Lodestone post or maybe even a resolution. Keep fingers crossed and please be sure to post any new information if it's available!

Very glad to hear it, and glad someone took the proactive step here. Doing us all a solid, here's hoping there's results soon.