PlayFab Outage History

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.

Between December 5, 2025, 11:37 PST and December 22, 2025, 14:20 PST, some PlayFab customers experienced inaccurate metrics reporting for certain dashboards \(which were underreported by as much as 30%\). The issue was caused by an infrastructure misconfiguration. ### Impact Some PlayFab dashboards displayed inaccurate or incomplete data during this period. Metrics such as API call volumes, login counts, and cloudscript processing times were underreported by up to 30%. No customer gameplay or operational functionality was affected, but visibility into service activity and performance was temporarily reduced. ### Root Cause Analysis A component responsible for metrics reporting was misconfigured, leading to the data not being displayed in dashboards at full accuracy. ### Action Items * We updated our infrastructure to ensure metrics are always sent to the correct environment. * We improved monitoring to better detect and alert on unexpected drops in metrics volume.

**Incident Overview** Between October 21st, 2025, and December 3rd, 2025, users were unable to redeem a subset of marketplace purchases for catalog items created during this window. The incident was caused by a misconfiguration affecting a redemption processor that prevented a subset of newly created items from being available for redemption. The issue was resolved by fixing the misconfiguration. **Impact** Users were unable to redeem a subset \(3-4%\) of items that were created during the window. All purchases made during this period have been redeemable since the fix on December 3rd. **Action Items** To prevent similar incidents from happening again, we have taken the following actions: * Additional validation to avoid misconfigurations affecting the redemption processing system * Enhanced alerting for the redemption processor to improve detection of similar issues