PlayFab incident

Multiple APIs degraded

Minor Resolved View vendor source →

PlayFab experienced a minor incident on May 29, 2026 affecting Authentication and Cloud Script and 1 more component, lasting 18h 9m. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 05:24 AM UTC
Resolved
May 29, 2026, 11:34 PM UTC
Duration
18h 9m
Detected by Pingoru
May 29, 2026, 05:24 AM UTC

Affected components

AuthenticationCloud ScriptContentDataEconomy (V2)EventsInventoryLobbyMatchmakingStatistics and Leaderboards

Update timeline

  1. investigating May 29, 2026, 05:24 AM UTC

    We are currently investigating widespread impact to multiple features.

  2. identified May 29, 2026, 06:11 AM UTC

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

  3. monitoring May 29, 2026, 05:16 PM UTC

    Services have recovered, we're monitoring for regressions.

  4. resolved May 29, 2026, 11:34 PM UTC

    This incident has been resolved.

  5. postmortem Jun 10, 2026, 06:07 PM UTC

    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.