https://approjects-vendor-status-watch.static.hf.space/v/playfab.htmlIncidents from Playfab's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/kv6041b46mybplayfab:2026-09-09T09:27:24.712-07:00Wed, 09 Sep 2026 16:27:24 +0000This incident has been resolved.https://stspg.io/c7pc8zyl42jlplayfab:2026-08-27T11:12:17.933-07:00Thu, 27 Aug 2026 18:12:17 +0000This incident has been resolved.https://stspg.io/6rqswqmvxxsxplayfab:2026-08-23T08:42:44.852-07:00Sun, 23 Aug 2026 15:42:44 +0000This incident has been resolved.https://stspg.io/8xz93bhyfds8playfab:2026-08-07T10:47:54.381-07:00Fri, 07 Aug 2026 17:47:54 +0000This incident has been resolved.https://stspg.io/kft7nmvj0rg7playfab:2026-07-23T09:11:33.782-07:00Thu, 23 Jul 2026 16:11:33 +0000This incident has been resolved.https://stspg.io/2d0b7lx96rvcplayfab:2026-07-16T14:37:44.991-07:00Thu, 16 Jul 2026 21:37:44 +0000This incident has been resolved.https://stspg.io/9w37xzhvf42pplayfab:2026-07-02T12:32:14.608-07:00Thu, 02 Jul 2026 19:32:14 +0000The incident is now resolvedhttps://stspg.io/lk6nz9zk07x8playfab:2026-06-23T18:02:09.014-07:00Wed, 24 Jun 2026 01:02:09 +0000This incident has been resolved.https://stspg.io/jgm71spngxjkplayfab:2026-06-12T13:51:24.295-07:00Fri, 12 Jun 2026 20:51:24 +0000This incident has been resolved.https://stspg.io/2jbrs44rvsr1playfab:2026-06-08T08:30:00.000-07:00Mon, 08 Jun 2026 15:30:00 +0000Some APIs temporarily received HTTP 429 errors.https://stspg.io/yjmssk6tk73vplayfab:2026-05-30T13:33:06.122-07:00Sat, 30 May 2026 20:33:06 +0000This incident has been resolved.https://stspg.io/5wh133jh3y88playfab:2026-05-28T22:24:29.667-07:00Fri, 29 May 2026 05:24:29 +0000On 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 Analyshttps://stspg.io/ls9mjg3hmn75playfab:2026-05-19T18:05:20.673-07:00Wed, 20 May 2026 01:05:20 +0000This incident has been resolved.https://stspg.io/bb18mg3x7m8rplayfab:2026-05-14T09:13:38.466-07:00Thu, 14 May 2026 16:13:38 +0000This incident is now resolved. All players should have up-to-date transaction history.https://stspg.io/ywxvgy9r4rvvplayfab:2026-05-05T12:22:27.183-07:00Tue, 05 May 2026 19:22:27 +0000This incident has been resolved.https://stspg.io/hd30sc2wgtw4playfab:2026-04-29T10:00:42.000-07:00Wed, 29 Apr 2026 17:00:42 +0000This incident has been resolved.https://stspg.io/3my6cbldgs6mplayfab:2026-04-07T14:00:00.000-07:00Tue, 07 Apr 2026 21:00:00 +0000We observed an increase in error rates for Groups APIs between ~2 pm pacific through ~7 pm pacific on Tuesday April 7 (aka 21:00 UTC April 7 - 02:00 UTC April 8). The initial root cause of this incident was a configuration change.https://stspg.io/rgx3s162q8j3playfab:2026-03-24T13:05:12.519-07:00Tue, 24 Mar 2026 20:05:12 +0000This incident has been resolved.https://stspg.io/swwv6nfthpg9playfab:2026-03-18T11:02:07.078-07:00Wed, 18 Mar 2026 18:02:07 +0000This incident has been resolved.https://stspg.io/krh4sr04cmn7playfab:2026-03-03T11:00:00.000-08:00Tue, 03 Mar 2026 19:00:00 +0000Some custom events sent through PlayFab WriteTelemetryEvents API were dropped between 03-03-2026 19:05 UTC to 03-05-2026 00:19 UTC. Our engineers have rolled out a fix, but unfortunately the custom events that were dropped during that window cannot be recovered.https://stspg.io/4wlw61m50b79playfab:2026-02-17T09:00:00.000-08:00Tue, 17 Feb 2026 17:00:00 +0000On 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 https://stspg.io/0pylczr4nml6playfab:2026-02-12T12:11:33.049-08:00Thu, 12 Feb 2026 20:11:33 +0000This incident has been resolved.https://stspg.io/23h43ympmhlfplayfab:2026-02-09T13:26:43.033-08:00Mon, 09 Feb 2026 21:26:43 +0000This incident has been resolved.https://stspg.io/rpt3w3ndhjshplayfab:2026-02-06T15:22:09.000-08:00Fri, 06 Feb 2026 23:22:09 +0000Delays have been resolved. Data is up-to-date.https://stspg.io/k84c76hwxv0splayfab:2026-02-05T12:53:33.678-08:00Thu, 05 Feb 2026 20:53:33 +0000InvalidRequest errors have subsided.https://stspg.io/dx39jzyyk3hqplayfab:2026-02-02T10:30:33.000-08:00Mon, 02 Feb 2026 18:30:33 +0000This incident has been resolved.https://stspg.io/pktm34z2z5svplayfab:2026-01-28T14:35:18.286-08:00Wed, 28 Jan 2026 22:35:18 +0000On January 28, 2026, between approximately 1:35 PM and 8:10 PM PDT, some customers experienced delays related to ban processing. During this time, our global indexing pipeline for ban-related data fell behind after encountering invalid customer data that caused batch processing failures. We mitigated the issue by deploying a hotfix to skip invalid affected records, allowing the indexing pipeline to catch up and normal processing to resume. ### Impact During the incident window \(about 6 hours and 34 minutes\), ban-related indexing was delayed. As a result, scenarios that rely on timely ban updates may have taken longer than expected to take effect. We did not observe data loss; the primary impact was delayed processing. Any bans enacted during the impact period were eventually applied. https://stspg.io/1ngnv1pxb7ykplayfab:2026-01-18T18:15:57.718-08:00Mon, 19 Jan 2026 02:15:57 +0000On January 18, 2026, between approximately 6:00 PM and 10:45 PM PT, some customers experienced delayed updates in the PlayFab Billing Summary report. The issue was triggered by a change in an external data query dependency, and service was restored after a hotfix was deployed and the processing pipelines were re-run. ### Impact The daily Billing Summary update \(including the “last updated” timestamp, daily CSV, and refreshed month-to-date estimates\) was delayed by roughly 4.5 hours. Customers viewing Billing Summary during that window may have seen estimates that were older than expected. ### Root Cause Analysis An external partner change introduced a new required parameter for a data update operation used by our billing reporting pipeline. This caused part of the daily aggregation ahttps://stspg.io/2792s30t14qlplayfab:2026-01-13T15:55:57.322-08:00Tue, 13 Jan 2026 23:55:57 +0000This incident has been resolved.https://stspg.io/qwn5rbg9pqz6playfab:2026-01-13T11:15:54.000-08:00Tue, 13 Jan 2026 19:15:54 +0000On 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