Minor impactResolvedDevOps

GitHub incident: Disruption with GitHub Billing

GitHub reported this minor-impact incident on its official status page on Aug 26, 2026, 23:37 UTC. It was resolved after 20h 7m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Aug 26, 2026, 23:37 UTC
started
Aug 27, 2026, 19:44 UTC
resolved
20h 7m
duration
Minor
impact
  1. resolvedAug 27, 2026, 19:44 UTC

    On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). <br /><br />This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. <br /><br />We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.

  2. investigatingAug 27, 2026, 17:58 UTC

    No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.

  3. investigatingAug 27, 2026, 16:20 UTC

    Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses.

  4. investigatingAug 27, 2026, 14:49 UTC

    Our mitigation is still holding as we continue to investigate to find the root cause.

  5. investigatingAug 27, 2026, 01:35 UTC

    We are continuing to monitor the mitigation that we have applied for the billing page disruption.

  6. investigatingAug 27, 2026, 00:31 UTC

    We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.

  7. investigatingAug 26, 2026, 23:42 UTC

    We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.

  8. investigatingAug 26, 2026, 23:37 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history

GitHub incident on Aug 26, 2026: Disruption with GitHub Billing · APIStatus.watch