PlayFab had 40 outages in the last 2 years totaling 60h 8m of downtime — averaging 1.6 incidents per month.
There were 40 PlayFab outages since June 5, 2025 totaling 60h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating an increased failure rate for the Client/LoginWithXbox API.
This incident has been resolved.
We are investigated an failure rate for the Client/LoginWithXbox API.
We are currently experiencing an issue with an upstream dependency that is impacting the PlayFab Experimentation service. As a result, scorecard generation is delayed. Our engineering team is actively working with the upstream provider to resolve the issue and restore full functionality. We will continue to provide updates as progress is made.
The upstream service has rolled back their feature. All impacted scorecards are now being regenerated.
This incident has been resolved. All impacted scorecards are regenerated.
We are currently investigating this issue.
The matchmaking feature is experiencing a major degradation. Titles utilizing real-time notifications experienced very low success rates depending upon their scenarios.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. Impact was observed from 20:40 PDT to 21:30 PDT. Note that this was after the previous related incident.
We are currently experiencing an issue in our data delivery pipeline. Customers may notice a delay in events appearing via Data Explorer or in Data Connections. Real-time processing of PlayStream events (e.g. for Automation Rules or WebHooks) is also impacted. No data has been lost and engineers are working to resolve this as soon as possible.
We have identified the issue and are working on a fix.
A fix has been deployed and we are monitoring the results.
This incident has been resolved.
On July 25, there was a delay in PlayStream processing between 07:40 - 08:10 PDT (14:40 - 15:10 UTC). We have identified the cause and the service has now recovered.
On July 25, 2025, between 2:52 PM and 3:13 PM UTC, some customers experienced delays in PlayStream processing. The incident was caused by errors when our systems encounter partner storage service errors. The incident was resolved when the underlying storage resource recovered. ### Impact All PlayStream processing was delayed for approximately 21 minutes. No repeated outages were reported. ### Root Cause Analysis The PlayStream processor application encountered errors while accessing a critical database. A slight increase in server-side latency was observed. ### Action Items * Improve internal log formatting for PlayStream services to ensure exception data is more easily queryable and can be aggregated for common error analysis. * Enhance monitoring and alerting to better capture anomalies in PlayStream processing and database connectivity.
We're experiencing delayed responses from our API servers and are currently investigating.
We are continuing to investigate this issue.
We're experiencing delayed responses from our API servers and are currently investigating. Customers are experiencing issues such as logging into Game Manager and API responses. In-game experiences may experience degraded performance.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On June 17, 2025, between 4:51 PM and 6:06 PM PDT, customers experienced increased latency and timeouts while accessing PlayFab services. The incident was caused by an influx of traffic, which caused increased latency in responding to across multiple titles, resulting in delays and timeouts. We resolved the issue by rerouting the traffic and implementing measures to reduce excess requests. ### Impact During the incident, some customers attempting to access multiple PlayFab titles encountered delays and timeouts for approximately 1 hour and 15 minutes. ### Root Cause Analysis The root cause of the incident was an influx of traffic targeting an endpoint, which caused increased latency in responding to requests across multiple titles, resulting in service disruption in the form of delays and timeouts. ### Action Items To minimize the impact of this happening again, we have implemented measures to better manage how an unexpected influx of traffic is managed.