PlayFab incident
A subset of customers saw excessive throttling when calling the Matchmaking Service
PlayFab experienced a minor incident on January 13, 2026 affecting Matchmaking, lasting 8h 3m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Jan 14, 2026, 03:12 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 14, 2026, 03:18 AM UTC
This incident has been resolved.
- postmortem Jan 21, 2026, 12:16 AM UTC
On January 13, 2026, between approximately 11:15 AM and 7:23 PM PST, some customers experienced increased failures when using PlayFab Matchmaking, including errors when calling matchmaking-related APIs \(such as GetMatch\). This was caused by a configuration update that applied more restrictive request limits than intended for some titles. We resolved the issue by rolling back the configuration change and monitoring service health to confirm recovery. ### Impact A subset of titles using the PlayFab Matchmaking Service experienced elevated API failures, which could cause matchmaking flows to fail and lead to a degraded gameplay experience until the rollback was completed. ### Root Cause Analysis A configuration change intended to adjust request limits did not map as expected to existing limits for certain APIs. As a result, some titles were throttled more aggressively than intended, increasing request failures. Because monitoring did not immediately highlight the affected titles, the issue was detected later and then mitigated by reverting the change. ### Action Items To prevent similar incidents from happening again, we have taken the following action: * Improved our throttling telemetry so request-throttling metrics are easier to interpret during investigations.