PlayFab Status

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.

This incident is now resolved. All players should have up-to-date transaction history.

A subset of players (~1.5%) may experience delays in their transaction history. We have identified the issue and are actively working on remediation.

On May 29, 2026, between approximately 9:00 PM and 10:09 PM Pacific Time, some customers experienced increased failures and timeouts across multiple PlayFab APIs. The issue was caused by an upstream infrastructure outage in the hosting environment that disrupted connectivity to backend storage services. The issue auto-resolved once the upstream infrastructure problem was mitigated.  ### Impact  During the impact window, customers experienced elevated error rates, timeouts, and connection disruptions when calling PlayFab APIs. Services including Lobby, Matchmaking, and real-time messaging were most heavily affected, with availability for those services degraded to between 75% and 95%. Multiple titles were impacted during the approximately 26-minute incident window.  ### Root Cause Analysis  An upstream infrastructure outage disrupted connectivity between PlayFab services and backend storage, causing request timeouts and elevated error rates across multiple APIs. The issue was external to PlayFab and self-resolved once the underlying infrastructure was restored.  ### Action Items  As part of our ongoing reliability investment, we are conducting a comprehensive assessment of our disaster recovery posture to improve resilience against upstream infrastructure disruptions. This includes evaluating regional redundancy for all critical data stores and developing documented recovery procedures to reduce the duration and impact of future incidents of this nature.

This incident has been resolved.

Services have recovered, we're monitoring for regressions.

The cause of the outage has been identified, PlayFab engineers are engaged.

We are currently investigating widespread impact to multiple features.

Some APIs temporarily received HTTP 429 errors.