Optus DCs

[danjaykay]

Omg i have been getting this issue non stop lately for about a week or more. Im with optus also. and i dont have any other issues playing any other online issue. What are we gonna do to be able to fix this. The issue makes it super hard to play and level up jobs. Why is it all of a sudden that we are having issues. I have played this game since beta and it has never happened before. now all of a sudden it doesnt work properly. I really do think this is a square enix issue since i dont have issues with other online games and my internet is working fine for everything else. Is there any way we can get square enix to look into this at all? because its making this game unplayable for a lot of people. even my best friend can not play because of this issue.

What can we do to get Square-Enix to listen to us and fix the issue so this game can be playable again?

[simshadows]

Can confirm, I'm living in Sydney with the home internet on Optus NBN, and Japanese FFXIV servers are completely unplayable while American FFXIV servers are perfectly fine. I'm getting around the problem by using mobile data.

I don't know anyone else with Optus playing FFXIV, but friends who are with other ISPs have no such problems.

When contacting Optus about it, their first reply was an inappropriately enthusiastic message about their Game Path service. Leaves a sour taste when considering that this entire thing may be a deliberate attempt at pulling new Game Path subscriptions.

May be shopping for a new ISP soon.

[Leki674]

If this is the case, Optus is very fucked up. Wonder if we can report Optus to ACCC

[Manuu]

Hello, just to let you all know. American servers are having the same problem. If you check here:

https://forum.square-enix.com/ffxiv/...-REPLY-HERE%21

I play on American Server and Im having packet loss with FF servers. It only happens with FF. Its a month now and the problem still. There we are discussing that FF servers are getting overloaded cuz we have so many new players joining us.

For now, staff still dont recognize this problem but more and more players are reporting the same issue everyday.

[VelKallor]

There we are discussing that FF servers are getting overloaded cuz we have so many new players joining us.

I had the same thought.

It may be an idea for SE toi start looking at sharding / zones like we had at the start of SHB earlier than expected. Influx and congestion may become a serious issue prior to launch, but thats up to them to decide. The issue seems to have ameliorated in the last day or so, but I cant confirm until later when the server gets busy.

Also, i want to thank you all for your help and input on the matter. Much appreciated.

[etzlenos]

For some strange reason, the problem seems to happen only between 3pm - 12am (GMT+10) for me. Out of this time frame, it's completely okay.

[the88shrimp]

Having the same issue.

I just did a ping test on the 2 JP data centre servers and ran them for a minute each.

neolobby05.ffxiv.com (124.150.157.156) had 61 sent 53 received at a 13% package loss

neolobby01.ffxiv.com (124.150.157.158) had 62 sent 49 received at a 21% package loss

Did a typical one with google as well even using the US site despite my DNS probably resolving it back to AU. Had 0% packet loss after a minute.

The fact that it only happens during prime times I'm guessing means Optus's route to Japan is getting conjested as using a VPN to connect to Japan still gives me the same issue. Maybe they just don't have the desire or funds to have an as efficient route / connection to JP.

[Majere]

It is probably just the lead up to the Olympics and during the Olympics that is causing a huge bandwidth issue on the optic fibre in and out of Japan at the moment with broadcasters getting better QoS.

Should hopefully be back to normal on the 9th or soon after

At least I hope it is only that and it will be back to normal soon

[Cimegs5088]

Hmm as Optus customer there's sometimes a day or so that cant log into the game, where it get dc when trying to connect to the data center with error code such as 2022, which means congested que. Normally it resolve by itself the next day but it's frustrating at times.