According to Asobo, this issue was caused by a cache that was overloaded and constantly restarting. This was used in part of the authentication process, I believe when they check what content you have. This explains why people had missing content if they were lucky enough to get in. This was my experience - got in after a very long load time and then couldn’t really do anything due to missing content.

This doesn’t seem like it’s a Microsoft cloud issue per se, it seems like Asobo had a single point of failure in the design that didn’t scale well. Today seems like the CDN limits are finally being reached, as it took a while to load up new areas. Getting into the game was no issue, though.

[–] scrubbles@poptalk.scrubbles.tech 9 points 1 month ago (1 children)

Hey you! You with your logic and reasoning and reading the issue notes from developers. You aren't a real gamer, get out of here with that! We're here to dogpile on a new game here!

[–] superkret@feddit.org 5 points 1 month ago (1 children)

From the point of view of a customer, the exact failure method is irrelevant.
Microsoft took a lot of money and wasn't able to deliver what was promised in exchange.

[–] scrubbles@poptalk.scrubbles.tech 2 points 1 month ago

Doesn't mean I'm not a forgiving person who understands problems happen. At this point, if you expect a game to work perfectly you can't buy day 1. Software is too complex to not expect any bugs day 1.