Best served with cold steel.

[Sauvage]

I think the worst part in all this is SE is just being silent. We have no idea what they are working on anymore, and this isn't reassuring.
I'm sure they read these forums atm, so I'm not really sure why they aren't saying anything. Seems to be the same with every video game company ever, to be honest, aha.

Also realize it's about 4am in Japan. Most of the people who will make these decisions are probably asleep. They did a quick fix early, saw that the servers were stable, and called it a day.

[LunarEmerald]

I think the worst part in all this is SE is just being silent. We have no idea what they are working on anymore, and this isn't reassuring.
I'm sure they read these forums atm, so I'm not really sure why they aren't saying anything. Seems to be the same with every video game company ever, to be honest, aha.

They aren't being silent. They've already addressed the issue. There's a limited number of instances for the battle and to prevent crashing, they're letting in a small amount of people at a time. Imagine a door and there's 1,000,000 people waiting to go through but only 1000 can pass at a time. It's working as intended, there's just so much congestion that it's going to take a while for it to clear up. The reason you get kicked back after the cutscene is because there's no available slots. As the day progresses, people are getting home from school/work and the congestion worsens. Until these people start going to bed, it's going to be nigh impossible to get in.

* Currently, players progressing through the main story quest of FINAL FANTASY XIV: Stormblood are unable to enter instances battles due to it reaching its limit of players allowed. Due to this, players are asked to wait until a player leaves an instanced area before they are able to enter.
While we have plenty of instances available, to prevent a heavy load on the servers, we are currently limiting the number of players that can enter at a time. If you are unable to enter an instance, we recommend waiting and trying again at a later time.

[Claviusnex]

NA servers start to go die around 10 PM. By around 2 AM, not many are on. I honestly think it's your best shot at getting in. Most people have school or work and can't stay up all night.

Except it's Friday night going into the weekend so it wouldn't surprise me to see a lot of folks stay up late.

[Finnfinite]

And to make things worse, the instance server is shared. So even small servers like Goblin are having to share slots with Balmung...

[Seryne]

I think a nap may be in order for me. Hopefully by the time I wake up this will be fixed. It probably won't be though

[LunarEmerald]

Except it's Friday night going into the weekend so it wouldn't surprise me to see a lot of folks stay up late.

Nah. A lot of them are kids that have trouble staying up late. It's not going to die down completely but it should take out a significant chunk. And hopefully that will be enough to get through.

[Moonlite]

No I just don't see the point in getting worked up for what anyone who has ever been in any expansion knows happens the first day. Early access in this game has always been a nice way of saying "7 day test server". It always happens. You wanna get snippy with me because I had realistic expectations and your toys are broken, go for it man.

You also don't seem to find the point in calling out bad design and money grabbing design either. HW's was smooth once you got past the login server had no problem with any quest at all. But hey they just some good ol boys tying to make a buck.

[Finnfinite]

You also don't seem to find the point in calling out bad design and money grabbing design either. HW's was smooth once you got past the login server had no problem with any quest at all.

they also didn't have an instance almost immediately. SB did branch the msq, but the other branch was really short...

[Rokke]

1 and a half hours of spamming the duty and it finally let me in. Going to wait a few days to attempt that on my alts lol

[Sauvage]

There's a limited number of instances for the battle and to prevent crashing, they're letting in a small amount of people at a time. Imagine a door and there's 1,000,000 people waiting to go through but only 1000 can pass at a time. It's working as intended, there's just so much congestion that it's going to take a while for it to clear up. The reason you get kicked back after the cutscene is because there's no available slots...

I don't think anyone is arguing your point. The problem most are having is that this solo instance they designed and placed so early on in the MSQ was their own doing and they have the power to fix it. Also, it's creating a vacuum on the backend causing players who were lucky enough to get through some substantial wait times for DF content. I personally have been trying to get through for the past 7 hours. The problem isn't the server load, it's in their content design.

Forcing players to simply "wait it out" or "comeback at another time" is a bad decision given that this problem has the potential of continuing well into next week.