PlayFab had 49 outages in the last 2 years totaling 1666h 8m of downtime — averaging 2 incidents per month.
There were 49 PlayFab outages since May 23, 2025 totaling 1666h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're currently investigating an outage with speech services api's in the west us region.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Starting at July 16, 2026 4:15 PM UTC, PlayStream CloudScript Azure Functions started failing silently for around over 3 hours. Any title using PlayStream rules to trigger Azure Functions had those functions silently not fire, no error surfaced to the title or player. Direct API calls, other action types, and API availability were unaffected. The issue has been identified and mitigated.
This incident has been resolved.
We have identified an issue affecting in-game currency transfers. Transfer operations may be delayed while we implement a mitigation.
The incident is now resolved
We are currently investigating elevated latencies affecting a portion of API requests, across all APIs.
We have identified an issue causing increased API latency in one of the compute clusters and are re-routing traffic to mitigate the issue.
We have completed re-routing traffic from the affected compute cluster, and API latencies are returning to normal.
This incident has been resolved.
Player deletion requests are experiencing processing delays. All requests remain queued and will be processed. We are actively working on improving throughput to reduce the backlog.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some APIs temporarily received HTTP 429 errors.
All PlayFab events are currently delayed and the team is investigating
A fix has been deployed and we're monitoring the status.
This incident has been resolved.
An issue has been fixed that was causing ingestion delays for event data to the Data Explorer features in Game Manager. Approximately 25% of titles may have been impacted with up to a 40 minute delay. The issue has been addressed and we are monitoring the ingestion delay recovery.
This incident has been resolved.
A subset of players (~1.5%) may experience delays in their transaction history. We have identified the issue and are actively working on remediation.
This incident is now resolved. All players should have up-to-date transaction history.
We are currently experiencing increased Timeouts and Operation Canceled errors for our Group APIs.
This incident has been resolved.
We are investigating an increase in error rates starting at 4:10 PM pacific on Wednesday April 29.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We observed an increase in error rates for Groups APIs between ~2 pm pacific through ~7 pm pacific on Tuesday April 7 (aka 21:00 UTC April 7 - 02:00 UTC April 8). The initial root cause of this incident was a configuration change.
A change to API request routing has caused a temporary increase in API latency and connection errors. We have deployed a change to mitigate the impact, and we are observing a return to normal latencies.
This incident has been resolved.
We are currently investigating an increased error rate in Economy apis impacting multiple titles.
The issue has been identified and a fix was deployed.
We are continuing to monitor for any further issues.
This incident has been resolved.
Some custom events sent through PlayFab WriteTelemetryEvents API were dropped between 03-03-2026 19:05 UTC to 03-05-2026 00:19 UTC. Our engineers have rolled out a fix, but unfortunately the custom events that were dropped during that window cannot be recovered.
We observed a spike in errors affecting all Client/LoginWith[Platform] APIs. This was caused by a production deployment that was reverted.
On February 17, 2026, between approximately 10:00 AM and 11:14 AM Pacific Time, some customers experienced increased failures when calling the Client/LoginWith\[Platform\] APIs. The issue was caused by a code regression that inadvertently removed a required validation check, leading to internal server errors. We mitigated the issue by rolling back the update. ### Impact During the impact window, customers experienced failed login attempts through the Client/LoginWith\[Platform\] APIs, with availability dropping to as low as 93%. ### Root Cause Analysis A recent code change removed a necessary null check, which caused certain requests for these APIs to fail. ### Action Items Rolled back the service update to immediately restore API availability. Deployed a hotfix to correct the code regression. Tests were also added to prevent this issue from recurring.
Short term solution is to sign out of GameManager and sign in again. We are currently investigating the root cause and working on a fix.
This incident has been resolved.
This incident has been mitigated.
This incident has been resolved.
We are currently experiencing delayed processing of catalog ratings. No data has been lost and engineers are working to resolve this as soon as possible.
Delays have been resolved. Data is up-to-date.
We are investigating an issue with PurchaseInventoryItem. Error responses take the form of InvalidRequest errors beginning at 18:20 UTC.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
InvalidRequest errors have subsided.
Customers may face delays in scaling up Multiplayer Game Servers across multiple regions
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue and are working on fixing an issue with delayed scorecard generation for existing PlayFab experiments. Experiments created on or after Jan 13th are working as expected.
A mitigation is being implemented for experiments created before Jan 13th to display updated scorecard data in PlayFab.
A fix has been implemented for experiments created before January 13th, we will continue to validate and monitor health.
This incident has been resolved.