Disruption with GitHub Billing
GitHub · Letzter gespeicherter Anbieterstatus: resolved
Offizielle Quellentexte werden in Originalsprache angezeigt.
Letzter Ereignisstatus ist nicht aktueller Dienststatus. Quellen können unvollständig sein; Verschwinden bestätigt keine Erholung. Für neuere Belege aktuellen Bericht/Quelle öffnen.
Gespeicherte Ereignisdetails
- Anbieterstatus
- resolved
- Anbieterauswirkungen
- minor
- Anbieterdatensatz erstellt
- 26 Aug 2026, 23:37:20 UTC
- Anbieterdatensatz aktualisiert
- 31 Aug 2026, 22:46:13 UTC
- Ausdrücklicher Anbieterbeginn
- 26 Aug 2026, 23:37:20 UTC
- Ausdrückliches Anbieterende
- 27 Aug 2026, 19:44:08 UTC
Vom Anbieter gemeldete betroffene Komponenten
Anbieter nannte ausdrücklich keine betroffenen Komponenten in dieser Revision.
Zuordnungen beschreiben gemeldeten Ereignisumfang, keine aktuelle Komponentenverfügbarkeit oder verifizierten Abhängigkeiten.
Die Erstellung eines Datensatzes ist nicht zwingend der Ausfallbeginn. Nicht gemeldete Zeiten bleiben unbekannt. Aus Erfassungszeiten berechnen wir keine Ausfalldauer.
Anbieterupdates in gespeicherten Revisionen
Neueste zuerst. Bis zu 100 verschiedene Updates aus den letzten 20 gespeicherten Revisionen. Geänderte Formulierungen bei gleicher Anbieterzeit bleiben separat.
- 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.
In gespeicherter Revision gesehen um 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.
In gespeicherter Revision gesehen um 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.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
Our mitigation is still holding as we continue to investigate to find the root cause.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
In gespeicherter Revision gesehen um 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.
In gespeicherter Revision gesehen um 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.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of impacted performance for some GitHub services.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC