It pops up for every release during the surge when people top out the login servers. However it has never been THIS bad. I'm betting the reasoning they never really got around to fixing it was the capacity issue never stuck around for more than a few days. Once everyone settled into routine the errors became far less common and didn't necessitate addressing.



Reply With Quote


