One thing I will hand SE right now. Is they seem to finish maintenance well ahead of projections.
except the maintenances haven't fixed anything so maybe they shouldn't be ending early.
We don't know that. They may be fixing things you are unaware of. Just because they didnt fix what you wanted fixed, doesnt mean they didnt fix anything.
Except, we do know that, as they stated the exact problem they "fixed" after each maintenance, which are not fixed.
Just because they fixed one cause of an issue doesn't mean they fixed all causes of an issue. It isn't as simple as "fixed error 101, will never happen again". The same issue for the end user could have many different causes. This is one of the most annoying things about working in software. Your users don't have a clue about how the software is working, but they know everything about the software. If you fix an issue that was causing slowdowns for 5 of your users and have that in your patch notes, 20 others will come forward and say that you didn't fix it because it is still slow for them.
With that said, this is still on SquareEnix and reflects poorly on their management. For whatever reason, they were unable to properly configure their NA/EU datacenter (or, the traffic on the NA/EU datacenter has exposed issues that weren't present under lighter loads, as evidenced by the fact that the JP datacenter doesn't seem to experience). If, however, there is enough traffic on the NA/EU servers to causes these issues, I question why both datacenters have the same number of servers. Capacity planning is hugely important for any system, but it doesn't seem like the managers took the time to do it properly. The company also boxed themselves into a corner with a release date, so they were unable to extend the open-beta period in the event of issues occurring. I know that, where I work, there wouldn't be an engineer who didn't complain about having the release date so close to our largest beta test.