Issues with metered billing report generation

What to do

• Check whether you use GitHub in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 23m it lasted.

  Anything that failed between 2026-03-31 13:47 UTC and 2026-03-31 15:10 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 7

1. investigatingMar 31, 2026, 1:47 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

   provider

2. investigatingMar 31, 2026, 1:56 PM UTC

   We're seeing issues related to metered billing reports, intermittently affecting metered usage graphs and reports on the billing page. We have identified an issue with a data store, and are working on mitigations.

   provider

3. investigatingMar 31, 2026, 2:39 PM UTC

   We're continuing to see high failure rates on billing report generation, and are working on mitigations for a data store related to billing reports.

   provider

4. investigatingMar 31, 2026, 2:56 PM UTC

   We are seeing a high number of 500s due to timeouts across GitHub services. We are redeploying some of our core services and we expect that this allow us to recover.

   provider

5. investigatingMar 31, 2026, 2:59 PM UTC

   We have applied mitigations to a data store related to billing reports, and are seeing partial recovery to billing report generation. We continue to monitor for full recovery.

   provider

6. monitoringMar 31, 2026, 3:01 PM UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

   provider

7. resolvedMar 31, 2026, 3:10 PM UTC

   On March 31, 2026, between 06:15 UTC and 15:30 UTC, the GitHub billing usage reports feature was degraded due to reduced server capacity. Customers requesting billing usage reports and loading the top usage by organization and repository on the billing overview and usage pages were impacted. The average error rate for usage report requests was 15%, peaking at 98% over an eight-minute window. For the billing pages, an average of 56% of requests failed to load the top usage cards. The root cause was an increase in billing usage report requests with large datasets, which exhausted the capacity of the nodes responsible for reporting data. There was no impact on billing charges. We mitigated the incident by adjusting our auto-scaling thresholds to better meet our capacity needs. We are working to improve our metrics to reduce time to detection and mitigation for similar issues in the future.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.