GitHub Status · History · Incident #6743
RESOLVEDDisruption with GitHub Billing
Minor · Started Aug 26, 2026 · 11:37 PM
GitHub Status · History · Incident #6743
RESOLVEDMinor · Started Aug 26, 2026 · 11:37 PM
Duration
20h 6m
Severity
Minor
Detection lead
—
User reports
—
Summary
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.
Started
Aug 26, 2026 · 11:37 PM
Resolved
Aug 27, 2026 · 7:44 PM
Duration
20h 6m
Severity
Minor
Event timeline
Investigating
Aug 26 · 11:37 PM GitHubWe are investigating reports of impacted performance for some GitHub services.
Investigating
Aug 26 · 11:42 PM GitHubWe 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.
Investigating
Aug 27 · 12:31 AM GitHubWe'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.
Investigating
Aug 27 · 1:35 AM GitHubWe are continuing to monitor the mitigation that we have applied for the billing page disruption.
Investigating
Aug 27 · 2:49 PM GitHubOur mitigation is still holding as we continue to investigate to find the root cause.
Investigating
Aug 27 · 4:20 PM GitHubOur 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.
Investigating
Aug 27 · 5:58 PM GitHubNo 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.
Resolved
Aug 27 · 7:44 PM GitHubOn 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.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.