All login calls to our app are timing out (we have a 30 second timeout in our client). This suddenly started happening about 90 minutes ago and is affecting all users (iOS & Android). The status page indicates no issues, but this is a huge issue for our app, as we are currently being featured.
We're experiencing the same issue in our App, we've just sent a high-priority ticket to PlayFab.
Yep we too have seen a sharp rise in PlayFab API request failure exceptions in the past 12 hours or so
Apologies for the inconvenience caused. Our engineering team are working to resolve this known incident. Thanks for the patience.
Our users are able to login but for the last 11 hours or so we've been seeing weird authentication and other issues (like title data randomly not loading sometimes). Not affecting everyone though.
Same here, especially GetPlayerCombinedInfo is returning 504 after 01:00 timeout
The issue was resolved at 3:45am PST January 31 and our players are able to log in normally.
The damage caused to our game by this incident is significant. It resulted in a significant revenue loss, but more importantly, several hundred 1-star reviews on both iOS and Google Play. The timing could not have been worse, since this was the first weekend of a special event in our game while being featured by the App Store.
What's most disappointing is that after using all channels available to us (contact form, forums, discord) to report the issue at 1:30pm PST January 30, it took about 12 hours before any sort of investigation started (according to the PlayFab incident report).
>> What's most disappointing is that after using all channels available to us (contact form, forums, discord) to report the issue at 1:30pm PST January 30, it took about 12 hours before any sort of investigation started (according to the PlayFab incident report).
Apologies for the impact within this time. In fact, since there is the complexity behind this issue, the PlayFab status page has been updated after the long time investigation.
We're having this problem too. Any response from PlayFab?
Can confirm, we are also facing similar issues for the last few hours
@Sarah Zhang The issue seems to be resolved. But I have a question about why it took such a long time for PlayFab to respond. According to our data, the problem started about 12:30pm PST. Ralf posted at 2pm PST.
For 12 hours there was no response from PlayFab, and the Status page listed no problems. Then the status page was updated at 1am PST that the problem was being investigated, and by 3am PST it was fixed.
Why did it take 12 hours to get a response from PlayFab? This is critical downtime for us, and cost us significant goodwill (and revenue) with our players.
- Matt
We are currently working on a full postmortem, which will be posted to the Status Page. To be clear, the goal is to firstly prevent issues like this from occurring, but in cases where they do to quickly detect and fix them, to minimize impact on titles. In this specific case, the issue presented in a way we had not seen before, and which meant it was not causing alerts to fire in the service as we would expect. The team is reviewing all the details of this for both the postmortem and to determine what additional monitoring we can add to help prevent anything like this from happening in future.
19 People are following this question.
