connection errors

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

[BettyHarlow]

I suggest as many of us contact support as possible! Thank you, thank you DDRDiesel, and many others for posting all of this information. It made reporting this easier for me!

[fawlgaiy]

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!

Thanks a lot for the awesome work! Posting my trace routes to NA and JP below for comparison:

JP
4 3 ms 3 ms 2 ms 209.216.96.50
5 3 ms 2 ms 2 ms 163.ae12.mpr1.sea1.us.zip.zayo.com [216.200.159.145]
6 3 ms 3 ms 3 ms ae6.mpr1.yyz1.ca.zip.zayo.com [64.125.23.121]
7 * * * Request timed out.
8 10 ms 10 ms 10 ms be2994.ccr22.cle04.atlas.cogentco.com [154.54.31.233]
9 15 ms 15 ms 15 ms be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
10 37 ms 38 ms 37 ms be2832.ccr22.mci01.atlas.cogentco.com [154.54.44.169]
11 63 ms 36 ms 36 ms be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89]
12 47 ms 46 ms 47 ms be3038.ccr32.slc01.atlas.cogentco.com [154.54.42.97]
13 65 ms 65 ms 65 ms be3110.ccr22.sfo01.atlas.cogentco.com [154.54.44.141]
14 64 ms 64 ms 64 ms be3670.ccr41.sjc03.atlas.cogentco.com [154.54.43.14]
15 172 ms 173 ms 173 ms be3696.ccr72.tyo01.atlas.cogentco.com [154.54.86.138]
16 170 ms 169 ms 170 ms be3050.rcr51.b060372-1.tyo01.atlas.cogentco.com [154.54.91.214]
17 170 ms 208 ms 170 ms square-enix.demarc.cogentco.com [154.18.1.146]
18 175 ms 155 ms 155 ms 219.117.144.118
19 155 ms 155 ms 155 ms 219.117.144.53
20 155 ms 155 ms 155 ms 219.117.144.41
21 157 ms 155 ms 155 ms 219.117.147.194
22 165 ms 164 ms 164 ms 124.150.157.15

NA
4 * * * Request timed out.
5 * 13 ms * 100ge0-76.core3.nyc4.he.net [184.104.196.177]
6 14 ms 16 ms 16 ms nyk-b1-link.ip.twelve99.net [62.115.183.157]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.