Disruption with GitHub Billing
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- minor
- Provider record created
- 26 Aug 2026, 23:37:20 UTC
- Provider record updated
- 31 Aug 2026, 22:46:13 UTC
- Explicit provider start
- 26 Aug 2026, 23:37:20 UTC
- Explicit provider end
- 27 Aug 2026, 19:44:08 UTC
Affected components reported by the provider
The provider explicitly listed no affected components in this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- resolved
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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
Our mitigation is still holding as we continue to investigate to find the root cause.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of impacted performance for some GitHub services.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC