Optimum User here as well. North Jersey. Cant login. I managed to get in once yesterday.
Printable View
Optimum User here as well. North Jersey. Cant login. I managed to get in once yesterday.
I might have missed it, but where did someone post optimum say it's their fault? I can play every other game fine including destiny and diablo. I don't think the issue is optimum.
yes its spreading to FL and SC 2002 error.
Also having issues. Optimum is my American provider when I'm playing south of the border.
Can provide trace route, though it sounds like the same issues AT&T were having with regards to handing off to NTT not too long ago, just now it's with Optimum.
What's crazy is the blatant disregard from SE to their community. I see no posts or responses for this issue. How many more complaints do they need?
I'd also like to point out this issue started two or three days ago.
It's been difficult playing at all because I cannot get in.
Great question! No idea since I use Optimum in the US and Cogeco back home.
Someone recently posted "today is better" a month after the complaints topic was made https://forum.square-enix.com/ffxiv/...server-network
So uh... a month?
We could probably use the same issue forum a community rep linked.
https://forum.square-enix.com/ffxiv/...61#post6252761
Specifically this one
I'm going to fill it out now. I hope you all do too.
Still waiting for an SE tech. support team member to chime into this thread. Also an Optimum user on the East coast here and haven't been able to login properly for 2+ days now.
A few people seem to be repeating that the issue must be Optimum however as I mentioned earlier in the thread, I am Canadian where that ISP is not even an option. Pointing all fingers at one specific ISP does not help the issue and ultimately lets Square place all blame on the ISP.
I lost my internet about 2 hours ago. I've been trying to troubleshoot this issue all day and now Optimum decided to crash and burn. Their sending a tech out on Saturday in the AM.
CT optimum and having an issue myself.
By some miracle this evening, I was able to log in and at least visit my house and do a couple roulettes. Zero issues at all actually playing the game. I'm still failing to ping/trace to the node however, and trying to get back in still fails. Guess I got a lucky route or something.
I came to the forums to see if anyone else was having issues or if it was my stupid internet. While I haven't DC'd, I've had lag and even saw the DC symbol next to my name while trading stuff in to my GC, despite my ping being normal.
For reference I also live in Canada and don't use the ISP that others are saying is the cause.
Last update before I head off to bed 06/15/23 at 11:43pm EST after 30 mins of trying to log on and failing I finally got in! I showed as having 0 ping, lmao. But my gcd was fine and everything did my raid and was told my static member in CA is having the extreme lag issues his ping was reading 3.5k which explains a lot of the dying while doing mechanics part. However, as soon as I logged out to try to switch for alt reclears got walled again by 2002. Followed by a hard crash. /playdead
Pray for answers soon. Have a nice night all.
I contacted SE tech. support. I urge everyone else to do the same so we can try and have this fixed ASAP.
Hey all, first post here; as a workaround I've been using cloudflare warp. Before using it I was completely unable to log into any NA DC; However now I'm able to log into Crystal/Goblin. I'll update this post with my findings in a bit after doing a few queues.
Update: Was able to run through P11N, and P12N without issue. I ran into a problem where I got dropped after going into O7N, however I had also joined a Discord Call at the exact same time; So im going to chalk it up to a network hiccup on my end.
I can also log into my character using Cloudflare Warp
So, again in NJ Trenton area I had no luck logging in without a VPN. In Manhattan at work I was able to log in fine the last two days. I am visiting my parents in North NJ who also have optimum and same issue. Can't connect. I tried using my phone as a Hotspot through Verizon and it worked. So for the time being until SE fixes this your options to play are a 1 month sub to a VPN or mobile Hotspot if you have unlimited Hotspot data. Both are not ideal as no way I'm paying for ffxiv and a VPN every month.
Can't log in to DC, get error 2002 and boot from game, and if I manage to get to loading in, I get error 90002. Optimum customer.
This is a great band aid fix, but here’s hoping they address the issue for real still lol
So funny thing, my internet went out late last night. I got up this morning and my internet is back on, and I was able to log in. Just a bit ago my friend here at my house was able to log into the game as well. I'm hoping this is fixed.
Giving an update early in the morning. Don't know if this is due to near non-existent traffic at this time of day but I managed to get in first try with no hitches at this very moment.
Now you can bet your asses and half a t**** I won't be logging out for the rest of the day
My trace results are actually reaching the destination IP this morning, so I'm tentatively going to assume the problem got fixed, wherever it was.
I logged in first try this morning, no lag issues so far! Hopefully it's resolved now.
Came here to mention I also was able to log in on the first try. Hopefully more people see this and we get some more results. Pinging the DC IP address of 204.2.29.122 gets results right away, and tracert reaches the destination
------------
Tracert results:
Tracing route to 204.2.29.122 over a maximum of 30 hops
4 12 ms 5 ms 4 ms 65.19.100.4
5 3 ms 3 ms 6 ms 64.15.5.80
6 8 ms 3 ms 4 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89]
7 5 ms 4 ms 4 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
8 10 ms 19 ms 12 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
9 27 ms 24 ms 24 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
10 28 ms 26 ms 30 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
11 79 ms 72 ms 76 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 77 ms 77 ms 78 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 76 ms 79 ms 78 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 79 ms * 204.2.29.241
15 75 ms 77 ms 74 ms 204.2.29.122
Trace complete.
----------------------------------
The route looks to be changed from using the nodes owned by twelve99 to use nodes from Level3, another internet backbone provider.
Anyone not from the NY area that was having problems, please run a ping and tracert to the IP address 204.2.29.122 and let us know if you get the same results!
Same in with 0 issues right now
Same here I'm able to log in no problem. My connection route is also going through Level3 now.
Tracing route to 204.2.29.70 over a maximum of 30 hops
4 12 ms 10 ms 27 ms ool-4353f892.dyn.optonline.net [67.83.248.146]
5 13 ms 12 ms 17 ms 64.15.7.71
6 12 ms 15 ms 12 ms 451be0d2.cst.lightpath.net [65.19.120.210]
7 12 ms 41 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89]
8 12 ms 14 ms 11 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
9 19 ms 15 ms 12 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.9
6]
10 29 ms 30 ms 29 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.1
66]
11 40 ms 29 ms 32 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.2
7]
12 * * * Request timed out.
13 82 ms 81 ms 88 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.5
7]
14 81 ms 84 ms 82 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.2
41.2.18]
15 81 ms * * 204.2.29.241
16 92 ms 84 ms 80 ms 204.2.29.70
Imagine how much stress and frustration and wasted time could have been avoided if a single SE representative had stepped in here to acknowledge it was a bad node along the path to the northeast, and that they were working to redirect.
Don't get me wrong. I'm thrilled it appears fixed.
I just happen to also be super disappointed that the answers most people got from "support" on this issue were "your isp sucks idk" and the folks on SE's end who were actually capable, held their complete silence rather than providing any updates or answers.
DDRDiesel, I'm not kidding when I say we all have YOU, SPECIFICALLY, to thank for this being resolved. Without your know-how, independent investigation, and tenacious reporting with aforementioned knowledge, I doubt the rest of us would have gotten any response, much less this fix!
Edit to add: My own tracert results for this morning
Tracing route to 204.2.29.122 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms [redacted]
2 * * * Request timed out.
3 8 ms 9 ms 8 ms [redacted]
4 15 ms 11 ms 11 ms opti37-8.nassau.cv.net [167.206.37.8]
5 12 ms 11 ms 12 ms 451be0fc.cst.lightpath.net [65.19.99.252]
6 13 ms 11 ms 11 ms 64.15.1.88
7 25 ms 12 ms 12 ms ae88.edge2.NewYork6.Level3.net [4.30.181.89]
8 13 ms 12 ms 17 ms NTT-level3-NewYorkCity6.Level3.net [4.68.75.78]
9 13 ms 14 ms 14 ms ae-2.r21.nwrknj03.us.bb.gin.ntt.net [129.250.6.96]
10 35 ms 35 ms 36 ms ae-3.r22.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
11 32 ms 32 ms 34 ms ae-1.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
12 * 87 ms * ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 88 ms 84 ms 84 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
14 85 ms 83 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
15 * * * Request timed out.
16 83 ms 83 ms 83 ms 204.2.29.122
Trace complete.
Checking in here to say that my ping/tracert to NA was successful and I was able to log in without issue today. I'll try it again later this evening, but based on these replies I have hope this is resolved for real and not just a fluke! Cheers for all your detective work DDRDiesel!
So I have been busy all day and I didn't want my poor PC struggling away keeping FFXIV up so I logged out this morning. I was just able to log back in and I am hoping this adventure we had to endure is finally over. Have fun all!
Exactly! It was a simple peek in their forum!! We did all the work for them! Thank you DDRDiesel, fawlgaiy, Strider_xiii, NaiaLalita and so many more for all of their work!!