{
"vendor": "Playfab",
"slug": "playfab",
"platform": "statuspage",
"status_url": "https://status.playfab.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-10T12:15:40Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-09T10:30:41.221-07:00",
"resolved_inferred": false,
"started_at": "2026-09-09T09:27:24.712-07:00",
"state": "resolved",
"title": "Increased failure rate in Matchmaking, Leaderboard, Lobby, PubSub, and GameSave APIs",
"updated_at": "2026-09-09T10:30:41.238-07:00",
"url": "https://stspg.io/kv6041b46myb"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-27T18:34:07.423-07:00",
"resolved_inferred": false,
"started_at": "2026-08-27T11:12:17.933-07:00",
"state": "resolved",
"title": "Degraded Leaderboard and Statistics operations",
"updated_at": "2026-08-27T18:34:07.442-07:00",
"url": "https://stspg.io/c7pc8zyl42jl"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-23T15:34:54.831-07:00",
"resolved_inferred": false,
"started_at": "2026-08-23T08:42:44.852-07:00",
"state": "resolved",
"title": "Player Deletion Delay",
"updated_at": "2026-08-23T15:34:54.847-07:00",
"url": "https://stspg.io/6rqswqmvxxsx"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-07T21:09:06.038-07:00",
"resolved_inferred": false,
"started_at": "2026-08-07T10:47:54.381-07:00",
"state": "resolved",
"title": "Lobby API availability impact",
"updated_at": "2026-08-07T21:09:06.052-07:00",
"url": "https://stspg.io/8xz93bhyfds8"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-23T12:01:47.891-07:00",
"resolved_inferred": false,
"started_at": "2026-07-23T09:11:33.782-07:00",
"state": "resolved",
"title": "Speech Services Api Outage West US",
"updated_at": "2026-07-23T12:01:47.909-07:00",
"url": "https://stspg.io/kft7nmvj0rg7"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-21T08:24:00.219-07:00",
"resolved_inferred": false,
"started_at": "2026-07-16T14:37:44.991-07:00",
"state": "resolved",
"title": "PlayStream CloudScript Azure Functions Actions Failing Silently",
"updated_at": "2026-07-21T08:24:00.234-07:00",
"url": "https://stspg.io/2d0b7lx96rvc"
},
{
"body": "The incident is now resolved",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-02T13:05:51.346-07:00",
"resolved_inferred": false,
"started_at": "2026-07-02T12:32:14.608-07:00",
"state": "resolved",
"title": "Economy V2 - Transfer operations delayed",
"updated_at": "2026-07-02T13:05:51.359-07:00",
"url": "https://stspg.io/9w37xzhvf42p"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-23T19:52:29.691-07:00",
"resolved_inferred": false,
"started_at": "2026-06-23T18:02:09.014-07:00",
"state": "resolved",
"title": "Elevated API latency",
"updated_at": "2026-06-23T19:52:29.706-07:00",
"url": "https://stspg.io/lk6nz9zk07x8"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-16T13:14:31.380-07:00",
"resolved_inferred": false,
"started_at": "2026-06-12T13:51:24.295-07:00",
"state": "resolved",
"title": "MasterPlayerAccountDeletion Processing Degradation",
"updated_at": "2026-06-16T13:14:31.400-07:00",
"url": "https://stspg.io/jgm71spngxjk"
},
{
"body": "Some APIs temporarily received HTTP 429 errors.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-08T08:30:00.000-07:00",
"resolved_inferred": false,
"started_at": "2026-06-08T08:30:00.000-07:00",
"state": "resolved",
"title": "Partial Outage of APIs Due to Throttling Errors",
"updated_at": "2026-06-08T09:10:11.322-07:00",
"url": "https://stspg.io/2jbrs44rvsr1"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-19T09:12:31.000-07:00",
"resolved_inferred": false,
"started_at": "2026-05-30T13:33:06.122-07:00",
"state": "resolved",
"title": "Event delays",
"updated_at": "2026-06-19T09:12:42.762-07:00",
"url": "https://stspg.io/yjmssk6tk73v"
},
{
"body": "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.\u00a0\n\n### Impact\u00a0\n\nDuring 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.\u00a0\n\n### Root Cause Analysis\u00a0\n\nAn 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.\u00a0\n\n### Action Items\u00a0\n\nAs 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-29T16:34:19.985-07:00",
"resolved_inferred": false,
"started_at": "2026-05-28T22:24:29.667-07:00",
"state": "postmortem",
"title": "Multiple APIs degraded",
"updated_at": "2026-06-17T09:39:44.143-07:00",
"url": "https://stspg.io/5wh133jh3y88"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-19T20:16:47.354-07:00",
"resolved_inferred": false,
"started_at": "2026-05-19T18:05:20.673-07:00",
"state": "resolved",
"title": "Delayed event ingestion for Data Explorer basic and advanced.",
"updated_at": "2026-05-19T20:16:47.368-07:00",
"url": "https://stspg.io/ls9mjg3hmn75"
},
{
"body": "This incident is now resolved. All players should have up-to-date transaction history.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-11T11:33:10.787-07:00",
"resolved_inferred": false,
"started_at": "2026-05-14T09:13:38.466-07:00",
"state": "resolved",
"title": "Economy V2 - Transaction history delayed for a subset of players",
"updated_at": "2026-06-11T11:33:10.804-07:00",
"url": "https://stspg.io/bb18mg3x7m8r"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-06T12:47:34.786-07:00",
"resolved_inferred": false,
"started_at": "2026-05-05T12:22:27.183-07:00",
"state": "resolved",
"title": "Ongoing degradation of Group APIs",
"updated_at": "2026-05-06T12:47:34.803-07:00",
"url": "https://stspg.io/ywxvgy9r4rvv"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-30T13:15:09.000-07:00",
"resolved_inferred": false,
"started_at": "2026-04-29T10:00:42.000-07:00",
"state": "resolved",
"title": "Increased 504 error rate across various APIs",
"updated_at": "2026-04-30T16:48:14.905-07:00",
"url": "https://stspg.io/hd30sc2wgtw4"
},
{
"body": "We 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). \n\nThe initial root cause of this incident was a configuration change.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-07T14:00:00.000-07:00",
"resolved_inferred": false,
"started_at": "2026-04-07T14:00:00.000-07:00",
"state": "resolved",
"title": "Increased Error Rates for Groups APIs",
"updated_at": "2026-04-08T09:35:16.282-07:00",
"url": "https://stspg.io/3my6cbldgs6m"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-24T15:30:31.319-07:00",
"resolved_inferred": false,
"started_at": "2026-03-24T13:05:12.519-07:00",
"state": "resolved",
"title": "Elevated API latency and connection failures",
"updated_at": "2026-03-24T15:30:31.339-07:00",
"url": "https://stspg.io/rgx3s162q8j3"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-18T11:47:37.347-07:00",
"resolved_inferred": false,
"started_at": "2026-03-18T11:02:07.078-07:00",
"state": "resolved",
"title": "Elevated Economy Api Error rate",
"updated_at": "2026-03-18T11:47:37.369-07:00",
"url": "https://stspg.io/swwv6nfthpg9"
},
{
"body": "Some 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-04T16:00:00.000-08:00",
"resolved_inferred": false,
"started_at": "2026-03-03T11:00:00.000-08:00",
"state": "resolved",
"title": "Telemetry Events - Custom events sent through WriteTelemetryEvents API were dropped from 3/3 19:05 - 3/5 00:19 UTC",
"updated_at": "2026-03-04T17:36:39.464-08:00",
"url": "https://stspg.io/krh4sr04cmn7"
},
{
"body": "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.\n\n### Impact\n\nDuring the impact window, customers experienced failed login attempts through the Client/LoginWith\\[Platform\\] APIs, with availability dropping to as low as 93%.\n\n### Root Cause Analysis\n\nA recent code change removed a necessary null check, which caused certain requests for these APIs to fail.\n\n### Action Items\n\nRolled back the service update to immediately restore API availability.\n\nDeployed a hotfix to correct the code regression. Tests were also added to prevent this issue from recurring.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-17T09:00:00.000-08:00",
"resolved_inferred": false,
"started_at": "2026-02-17T09:00:00.000-08:00",
"state": "postmortem",
"title": "Drop in availability for Client/LoginWith[Platform] APIs",
"updated_at": "2026-02-24T14:42:48.504-08:00",
"url": "https://stspg.io/4wlw61m50b79"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-13T11:47:25.422-08:00",
"resolved_inferred": false,
"started_at": "2026-02-12T12:11:33.049-08:00",
"state": "resolved",
"title": "Failure When Creating New Titles In GameManager",
"updated_at": "2026-02-13T11:47:25.437-08:00",
"url": "https://stspg.io/0pylczr4nml6"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-09T13:27:03.922-08:00",
"resolved_inferred": false,
"started_at": "2026-02-09T13:26:43.033-08:00",
"state": "resolved",
"title": "Delay in processing catalog updates for marketplace offers",
"updated_at": "2026-02-09T13:27:03.937-08:00",
"url": "https://stspg.io/23h43ympmhlf"
},
{
"body": "Delays have been resolved. Data is up-to-date.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-06T15:45:00.000-08:00",
"resolved_inferred": false,
"started_at": "2026-02-06T15:22:09.000-08:00",
"state": "resolved",
"title": "Catalog Ratings Processing Delay",
"updated_at": "2026-02-07T11:06:16.793-08:00",
"url": "https://stspg.io/rpt3w3ndhjsh"
},
{
"body": "InvalidRequest errors have subsided.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-05T14:24:48.318-08:00",
"resolved_inferred": false,
"started_at": "2026-02-05T12:53:33.678-08:00",
"state": "resolved",
"title": "PurchaseInventoryItem api failures",
"updated_at": "2026-02-05T14:24:48.333-08:00",
"url": "https://stspg.io/k84c76hwxv0s"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-03T02:00:09.000-08:00",
"resolved_inferred": false,
"started_at": "2026-02-02T10:30:33.000-08:00",
"state": "resolved",
"title": "Delay in scale-up operations for Multiplayer Game Servers",
"updated_at": "2026-02-03T07:36:29.411-08:00",
"url": "https://stspg.io/dx39jzyyk3hq"
},
{
"body": "On 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.\n\n### Impact\n\nDuring 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.\n\n### Root Cause Analysis\n\nA customer-created record contained an invalid value that was interpreted incorrectly during decoding \\(in this case, an invalid date string\\). Because our validation did not sufficiently enforce expected formats for certain fields, the bad data made it into the ban-related data set and caused repeated batch failures in the indexing pipeline. Those failures prevented the pipeline from making forward progress until the problematic records were bypassed.\n\n### Action Items\n\nTo reduce the likelihood and impact of similar issues, we completed the following actions:\n\n* Deployed a hotfix to safely skip invalid records so indexing can continue even when encountering bad data.\n* Improved error logging in the indexing processor to speed up diagnosis if similar processing failures occur.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-28T20:06:13.252-08:00",
"resolved_inferred": false,
"started_at": "2026-01-28T14:35:18.286-08:00",
"state": "postmortem",
"title": "Delay in Ban Updates",
"updated_at": "2026-02-17T14:59:59.286-08:00",
"url": "https://stspg.io/pktm34z2z5sv"
},
{
"body": "On 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.\n\n### Impact\n\nThe daily Billing Summary update \\(including the \u201clast updated\u201d 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.\n\n### Root Cause Analysis\n\nAn 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 and update flow to fail until we adjusted the operation and reprocessed the affected data.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we are taking the following actions:\n\n* Improving our monitoring process to more quickly detect failures in the end-to-end billing update flow so delays can be identified and addressed sooner.\n* Investigating improvements to communication with external dependency team for upcoming changes on their end",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-19T01:45:39.000-08:00",
"resolved_inferred": false,
"started_at": "2026-01-18T18:15:57.718-08:00",
"state": "postmortem",
"title": "Billing Summary - Most recent daily bill estimate may be slow to populate",
"updated_at": "2026-01-28T10:27:33.959-08:00",
"url": "https://stspg.io/1ngnv1pxb7yk"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-20T13:14:02.550-08:00",
"resolved_inferred": false,
"started_at": "2026-01-13T15:55:57.322-08:00",
"state": "resolved",
"title": "Experimentation scorecard generation delayed",
"updated_at": "2026-01-20T13:14:02.568-08:00",
"url": "https://stspg.io/2792s30t14ql"
},
{
"body": "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.\n\n### Impact\n\nA 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.\n\n### Root Cause Analysis\n\nA 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.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following action:\n\n* Improved our throttling telemetry so request-throttling metrics are easier to interpret during investigations.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-13T19:18:59.575-08:00",
"resolved_inferred": false,
"started_at": "2026-01-13T11:15:54.000-08:00",
"state": "postmortem",
"title": "A subset of customers saw excessive throttling when calling the Matchmaking Service",
"updated_at": "2026-01-20T16:16:20.673-08:00",
"url": "https://stspg.io/qwn5rbg9pqz6"
},
{
"body": "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.\n\n### Impact\n\nSome 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.\n\n### Root Cause Analysis\n\nA component responsible for metrics reporting was misconfigured, leading to the data not being displayed in dashboards at full accuracy.\n\n### Action Items\n\n* We updated our infrastructure to ensure metrics are always sent to the correct environment.\n\n* We improved monitoring to better detect and alert on unexpected drops in metrics volume.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-23T11:41:52.296-08:00",
"resolved_inferred": false,
"started_at": "2025-12-23T11:41:52.253-08:00",
"state": "postmortem",
"title": "Lower/incorrect usage reported for Title Overview page dashboards",
"updated_at": "2026-01-06T15:17:11.350-08:00",
"url": "https://stspg.io/v6vg68dncgb1"
},
{
"body": "**Incident Overview**\u00a0\n\nBetween 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.\u00a0 \u00a0\n\n**Impact**\u00a0\n\nUsers\u00a0were unable to redeem a subset\u00a0\\(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.\u00a0\n\n**Action Items**\u00a0\n\nTo prevent similar incidents from happening again, we have taken the following actions:\u00a0\n\n* Additional validation to avoid misconfigurations affecting the redemption processing system\u00a0\n\n* Enhanced alerting for the\u00a0redemption processor to improve detection of similar issues",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-04T09:51:33.931-08:00",
"resolved_inferred": false,
"started_at": "2025-12-03T14:02:17.727-08:00",
"state": "postmortem",
"title": "A subset of catalog items created since October 21st have been unable to be redeemed",
"updated_at": "2025-12-18T15:06:37.619-08:00",
"url": "https://stspg.io/sf3sknjz43j9"
},
{
"body": "On November 25, 2025, between 15:15 PST and 17:00 PST, some customers experienced reduced availability when accessing Leaderboard, Lobby and Game Saves APIs. The incident was caused by a DNS outage in the West US 3 region, which affected communication with our infrastructure. The issue was resolved automatically once the DNS service was restored.\n\n### Impact\n\nDuring the incident, the availability of the FindLobby and FindFriendLobbies APIs dropped to approximately 96%, the availability of all GameSave APIs dropped to an average of 80%, and downstream processing for Leaderboards was delayed. As a result, customers were unable to query for lobbies or upload new game saves using these APIs for about 1 hour and 45 minutes. Leaderboard updates were delayed. Service quality was temporarily below our standard threshold.\n\n### Root Cause Analysis\n\nThe incident was caused by a DNS outage in the West US 3 region. This outage disrupted communication between our Lobby, GameSave and Leaderboard services and their supporting infrastructure, resulting in reduced API availability. The root cause was related to an external dependency and not due to a code or configuration change within PlayFab.\n\n### Action Items\n\nTo prevent similar incidents in the future, we have enhanced our monitoring systems to detect and report anomalies in API availability more quickly. We are also reviewing our infrastructure dependencies to improve resiliency against external outages.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-25T17:18:58.595-08:00",
"resolved_inferred": false,
"started_at": "2025-11-25T16:53:21.841-08:00",
"state": "postmortem",
"title": "Intermittent API failures in Leaderboard, Lobby and Game Saves services",
"updated_at": "2026-01-07T13:15:28.783-08:00",
"url": "https://stspg.io/qlxgwnbrxqhh"
},
{
"body": "On November 23rd\u201324th, 2025, some customers experienced errors when using PlayFab\u2019s Plan Recommendation and Pricing Sync features. The incident was caused by an authentication issue in a billing service component, which disrupted several related services. We resolved the issue by updating the connection logic for our data service.\n\n### Impact\n\nCustomers were unable to access plan recommendations and update workflows. The issue was detected by our monitoring systems and reported by customers.\n\n### Root Cause Analysis\n\nThe authentication errors were triggered by changes in the underlying .Net version, which affected how a billing service component connected to our data service.\n\n### Resolution\n\nWe updated the connection logic for the billing service component, restoring normal operation and notifying affected customers.\n\n### Action Items\n\n* Improved the connection logic for our data service in the affected billing service component.\n\n* Enhanced monitoring to detect authentication issues earlier.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-24T15:25:28.371-08:00",
"resolved_inferred": false,
"started_at": "2025-11-24T11:37:02.906-08:00",
"state": "postmortem",
"title": "Issues loading the Upgrade Account / Plan Recommendation page",
"updated_at": "2026-01-09T15:52:36.949-08:00",
"url": "https://stspg.io/l6qy3b2zytbh"
},
{
"body": "On November 14, 2025, between 8:00 AM and 4:54 PM PST, some PlayFab customers experienced delays in Bulk Segmentation features. This resulted in delays in player profile updates, segment exports, and scheduled tasks. The issue was caused by a state in the ADX cluster powering the features, which led to the materialized view becoming unhealthy. We applied manual recovery steps and collaborated with the ADX team to resolve the problem, as the cluster was in a degraded state.\n\n### Impact\n\nCustomers experienced delays in player profile updates, segment exports, and scheduled tasks due to the degraded health of the player profile materialized view. Bulk Segmentation features were specifically impacted during this period.\n\n### Root Cause Analysis\n\nThe issue was triggered by an unexpected state in the ADX cluster powering the features, which caused materialized views to stop processing new data. This led to delays for customers and required manual recovery steps to restore normal functionality.\n\n### Action Items\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Implemented safeguards to prevent materialized views from entering an unhealthy state in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-14T16:13:25.275-08:00",
"resolved_inferred": false,
"started_at": "2025-11-14T12:46:34.614-08:00",
"state": "postmortem",
"title": "Bulk Segmentation are delayed",
"updated_at": "2025-11-18T15:40:15.795-08:00",
"url": "https://stspg.io/bl9ts6km25nt"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-29T16:00:23.000-07:00",
"resolved_inferred": false,
"started_at": "2025-10-29T09:17:52.065-07:00",
"state": "resolved",
"title": "Widespread Connectivity Issues",
"updated_at": "2025-10-29T21:38:03.949-07:00",
"url": "https://stspg.io/vvw3r29vv0p2"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-24T06:55:13.561-07:00",
"resolved_inferred": false,
"started_at": "2025-10-23T21:32:28.476-07:00",
"state": "resolved",
"title": "Errors when creating/updating Data Connections",
"updated_at": "2025-10-24T06:55:13.574-07:00",
"url": "https://stspg.io/yml8xjtzf3vp"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-15T15:45:30.000-07:00",
"resolved_inferred": false,
"started_at": "2025-10-15T15:30:12.339-07:00",
"state": "resolved",
"title": "Increased failure rate for Client/LoginWithXbox API",
"updated_at": "2025-10-15T15:58:40.662-07:00",
"url": "https://stspg.io/kg1gsrj36tmk"
},
{
"body": "We are investigated an failure rate for the Client/LoginWithXbox API.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-15T15:00:00.000-07:00",
"resolved_inferred": false,
"started_at": "2025-10-15T15:00:00.000-07:00",
"state": "resolved",
"title": "Increased failure rate for Client/LoginWithXbox",
"updated_at": "2025-10-15T15:20:54.630-07:00",
"url": "https://stspg.io/yjb7g0kyfsch"
},
{
"body": "On October 9th, 2025, between 12:20 PM and 2:40 PM PDT, some customers experienced increased failures when accessing the GameClient/ConsumePS5Entitlements and GameClient/ConsumePSNEntitlements APIs, as well as a few related APIs. The incident was caused by an outage in a third-party dependency, which resulted in our APIs receiving increased exceptions and errors. The issue was resolved once the external outage ended and normal service resumed.\n\n### Impact\n\nCustomers were unable to successfully complete requests through affected entitlements APIs for approximately two hours. This resulted in failed attempts to consume entitlements, impacting the user experience for games relying on these APIs.\n\n### Root Cause Analysis\n\nThe root cause of the incident was an external issue: a service outage in a third-party dependency. As our APIs depend on calls to the external service for authentication and entitlement verification, the outage led to increased exceptions and errors being returned to our services.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Enhanced our monitoring and alerting systems to provide earlier detection of external partner outages affecting entitlements APIs.\n\n* Reviewed and improved our exception handling and error messaging to ensure clear communication to customers when third-party outages impact API availability.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-09T14:40:12.926-07:00",
"resolved_inferred": false,
"started_at": "2025-10-09T12:54:59.999-07:00",
"state": "postmortem",
"title": "Increased Error Rates for RedeemPlaystationStoreInventoryItems, ConsumePS5Entitlements, and ConsumePSNEntitlements APIs",
"updated_at": "2025-10-14T15:01:44.267-07:00",
"url": "https://stspg.io/jt2xztycr4rh"
},
{
"body": "On September 16, 2025, between 8:20 PM and 10:42 PM PDT, some customers experienced issues with PlayFab Lobbies. During this period, players across all titles using Lobbies were unable to create, join, or update lobbies, although search APIs remained functional. The incident was caused by a maintenance event internal to our Redis infrastructure, which disrupted connectivity between the Lobby service and Redis. We resolved the issue by rebooting the Redis instances, restoring connectivity and service functionality.\n\n### Impact\n\nPlayers were unable to create, join, or update lobbies across all titles that use the PlayFab Lobby system for approximately 2 hours and 22 minutes. While search APIs continued to work, players could not join lobbies they found during this time.\n\n### Root Cause Analysis\n\nThe root cause of the incident was a maintenance event within our Redis infrastructure that unexpectedly killed connectivity for the Lobby service. While we have the capability to schedule maintenance, this event occurred exactly when the impact started, leading to the service disruption.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Updated the Lobby service to better display its status on our service overview dashboard, which will enhance visibility and expedite future detection and mitigation efforts.\n\n* Improved our internal processes for scheduling and communicating maintenance events that could impact service connectivity.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-16T22:35:42.967-07:00",
"resolved_inferred": false,
"started_at": "2025-09-16T21:01:00.561-07:00",
"state": "postmortem",
"title": "Increased API Error Response Rate",
"updated_at": "2025-09-23T14:04:27.803-07:00",
"url": "https://stspg.io/l1469bfgb657"
},
{
"body": "On September 12, 2025, between 01:42 AM and 03:09 AM PDT, some PlayFab customers experienced issues authenticating with Photon APIs. The incident was caused by unexpected traffic patterns to Photon API endpoints, which resulted in a hot partition and degraded availability. We resolved the issue by setting a throttle limit for the affected API endpoint.\n\n### Impact\n\nDuring the incident, customers with Photon tokens stored on the hot partition may have been unable to authenticate. The availability for Photon APIs dropped to as low as 78.8%, impacting service reliability for approximately 1 hour and 27 minutes.\n\n### Root Cause Analysis\n\nThe root cause was an unexpected traffic pattern on the Photon authentication API endpoint. A large call volume on this endpoint put strain on database lookup tables for logging in the user. The call volume was outside normal parameters.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Cached results from previous Photon sessions to reduce strain on the database infrastructure.\n\n\u00b7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Adjusted the title rate limit for the Photon APIs.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-12T03:19:40.781-07:00",
"resolved_inferred": false,
"started_at": "2025-09-12T02:39:40.492-07:00",
"state": "postmortem",
"title": "Increased API Error Response Rate",
"updated_at": "2025-09-30T13:27:33.090-07:00",
"url": "https://stspg.io/xfmkgdn3q353"
},
{
"body": "This incident has been resolved. All impacted scorecards are regenerated.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-10T09:24:19.925-07:00",
"resolved_inferred": false,
"started_at": "2025-09-09T16:28:19.923-07:00",
"state": "resolved",
"title": "Experimentation Scorecard Generation Delay",
"updated_at": "2025-09-10T09:24:19.943-07:00",
"url": "https://stspg.io/ybmpknrb95hy"
},
{
"body": "This incident has been resolved. Impact was observed from 20:40 PDT to 21:30 PDT. Note that this was after the previous related incident.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-01T11:09:03.144-07:00",
"resolved_inferred": false,
"started_at": "2025-08-31T20:40:49.000-07:00",
"state": "resolved",
"title": "PlayFab Matchmaking APIs experiencing degraded performance",
"updated_at": "2025-09-01T11:09:03.161-07:00",
"url": "https://stspg.io/h6sf77sgqrg4"
},
{
"body": "On August 31, 2025, between 11:50 AM and 7:53 PM PDT, some customers experienced a complete outage of PlayFab Matchmaking. The incident was caused by a regression in the authentication library, which led to unexpected high call rates to Entra ID for token acquisition, resulting in service throttling and failures. We resolved the issue by increasing authentication rate limits, updating the authentication code, recycling affected application instances, and isolating impacted titles into dedicated deployments.\n\n### Impact\n\nDuring the outage, matchmaking services were unavailable for all affected titles, preventing players from joining matches. Notification failures also occurred, resulting in players being stuck in matchmaking and not receiving proper updates.\n\n### Root Cause Analysis\n\nThe root cause of the incident was a regression in the updated authentication library, which failed to cache tokens as expected. This led to a surge in token requests to Entra ID, causing throttling and authentication failures across the service. The updated library created new instances for each authentication attempt, breaking the caching mechanism and increasing network traffic unexpectedly.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Implemented service-level caching for authentication tokens to reduce unnecessary external calls.\n* Enhanced monitoring and diagnostics to detect abnormal network patterns and authentication failures more quickly.\n* Improved notification handling and recycling processes to prevent players from being stuck in matchmaking.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-31T20:28:48.383-07:00",
"resolved_inferred": false,
"started_at": "2025-08-31T12:00:46.000-07:00",
"state": "postmortem",
"title": "PlayFab Matchmaking APIs is experiencing degraded experience",
"updated_at": "2025-09-09T16:35:30.913-07:00",
"url": "https://stspg.io/qlbhffj2r0zb"
},
{
"body": "On August 19, 2025, between 9:32 AM and 10:50 AM PDT, some customers experienced failures when calling PlayFab APIs due to issues with entity token validation. The incident was caused by a switch in the JSON library used for serialization and deserialization of entity tokens \\(for improved security and efficiency\\). We resolved the issue by rolling back the serialization change and advising impacted customers to refresh their tokens.\n\n### Impact\n\nDuring the incident, calls to validate entity tokens failed, preventing all further API calls using those tokens. Affected APIs primarily included WriteTelemetryEvents, Catalog search, GetPlayFabIdFrom\\*Id, ExecuteCloudScript, and Group-related APIs. This resulted in service disruption for customers relying on these endpoints.\n\n### Root Cause Analysis\n\nThe root cause was a deployment that switched the JSON library responsible for entity token serialization.  After rolling back the change, errors persisted for tokens minted during the incident window, requiring customers to refresh their tokens.\n\n### Action Items\n\nTo prevent similar incidents from happening again, we have taken the following actions:\n\n* Added documentation to the entity token release process to highlight serialization risks and warnings.\n\n* Implemented additional backcompat token tests for the entity token to expand test",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-19T13:44:55.608-07:00",
"resolved_inferred": false,
"started_at": "2025-08-19T09:30:18.000-07:00",
"state": "postmortem",
"title": "Increased error rate for Authentication/ValidateToken",
"updated_at": "2025-08-26T13:36:32.780-07:00",
"url": "https://stspg.io/4jc6npxxm0zl"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-14T15:11:19.249-07:00",
"resolved_inferred": false,
"started_at": "2025-08-14T14:15:26.000-07:00",
"state": "resolved",
"title": "PlayStream and Telemetry Event Delivery Delay",
"updated_at": "2025-08-14T15:11:19.266-07:00",
"url": "https://stspg.io/bm2td7glkt72"
}
]
}