GitHub incident

Disruption with GitHub Billing

Minor Resolved View vendor source →

GitHub experienced a minor incident on August 26, 2026, lasting 20h 6m. The incident has been resolved; the full update timeline is below.

Started
Aug 26, 2026, 11:37 PM UTC
Resolved
Aug 27, 2026, 07:44 PM UTC
Duration
20h 6m
Detected by Pingoru
Aug 26, 2026, 11:37 PM UTC

Update timeline

  1. investigating Aug 26, 2026, 11:37 PM UTC

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

  2. investigating Aug 26, 2026, 11:42 PM 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.

  3. investigating Aug 27, 2026, 12:31 AM 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.

  4. investigating Aug 27, 2026, 01:35 AM UTC

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

  5. investigating Aug 27, 2026, 02:49 PM UTC

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

  6. investigating Aug 27, 2026, 04:20 PM 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.

  7. investigating Aug 27, 2026, 05:58 PM 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.

  8. resolved Aug 27, 2026, 07:44 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.