PlayFab incident

Billing Summary - Most recent daily bill estimate may be slow to populate

Minor Resolved View vendor source →

PlayFab experienced a minor incident on January 19, 2026 affecting Reports, lasting 2h 45m. The incident has been resolved; the full update timeline is below.

Started
Jan 19, 2026, 07:00 AM UTC
Resolved
Jan 19, 2026, 09:45 AM UTC
Duration
2h 45m
Detected by Pingoru
Jan 19, 2026, 07:00 AM UTC

Affected components

Reports

Update timeline

  1. investigating Jan 19, 2026, 02:15 AM UTC

    Billing Summary daily bill estimates may not contain the most recent day's estimate. We are currently investigating this issue, and expect to populate all daily billing estimates in the summary when the issue is resolved

  2. monitoring Jan 19, 2026, 04:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 19, 2026, 04:14 PM UTC

    This incident has been resolved.

  4. postmortem Jan 28, 2026, 05:15 PM UTC

    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. ### 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 and update flow to fail until we adjusted the operation and reprocessed the affected data. ### Action Items To prevent similar incidents from happening again, we are taking the following actions: * 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. * Investigating improvements to communication with external dependency team for upcoming changes on their end