Critical incident

GitHub: Incident with GitHub.com

Affected: Git Operations, Webhooks, API Requests, Issues, Pull Requests, Actions, Pages, Copilot

Current status of GitHub: Operational — live GitHub status

Timeline

1. Aug 17, 2026, 13:40 UTC
   investigating
   We are investigating reports of impacted performance for some GitHub services.
2. Aug 17, 2026, 13:41 UTC
   investigating
   API Requests is experiencing degraded performance. We are continuing to investigate.
3. Aug 17, 2026, 13:42 UTC
   investigating
   Actions is experiencing degraded performance. We are continuing to investigate.
4. Aug 17, 2026, 13:44 UTC
   investigating
   Webhooks is experiencing degraded performance. We are continuing to investigate.
5. Aug 17, 2026, 13:45 UTC
   investigating
   We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available
6. Aug 17, 2026, 13:46 UTC
   investigating
   Issues is experiencing degraded performance. We are continuing to investigate.
7. Aug 17, 2026, 13:58 UTC
   investigating
   Pull Requests is experiencing degraded performance. We are continuing to investigate.
8. Aug 17, 2026, 14:04 UTC
   investigating
   We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. Investigations are on-going into the root cause, and updates will continue to be provided as we investigate.
9. Aug 17, 2026, 14:24 UTC
   investigating
   We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. Investigations are on-going and we will continue to provide updates as we discover more information.
10. Aug 17, 2026, 14:31 UTC
    investigating
    Copilot is experiencing degraded availability. We are continuing to investigate.
11. Aug 17, 2026, 14:45 UTC
    investigating
    Pull Requests is experiencing degraded availability. We are continuing to investigate.
12. Aug 17, 2026, 14:49 UTC
    investigating
    Issues is experiencing degraded availability. We are continuing to investigate.
13. Aug 17, 2026, 14:54 UTC
    investigating
    Pull Requests is experiencing degraded availability. We are continuing to investigate.
14. Aug 17, 2026, 14:58 UTC
    investigating
    Actions is experiencing degraded availability. We are continuing to investigate.
15. Aug 17, 2026, 14:58 UTC
    investigating
    We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently performing mitigations based on our investigation thus far and are monitoring for improvement.
16. Aug 17, 2026, 14:58 UTC
    investigating
    Webhooks is experiencing degraded availability. We are continuing to investigate.
17. Aug 17, 2026, 15:01 UTC
    investigating
    API Requests is experiencing degraded availability. We are continuing to investigate.
18. Aug 17, 2026, 15:10 UTC
    investigating
    Pages is experiencing degraded performance. We are continuing to investigate.
19. Aug 17, 2026, 15:21 UTC
    investigating
    Git Operations is experiencing degraded performance. We are continuing to investigate.
20. Aug 17, 2026, 15:40 UTC
    investigating
    Webhooks is experiencing degraded performance. We are continuing to investigate.
21. Aug 17, 2026, 15:42 UTC
    investigating
    We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently performing mitigations and will post updates as we progress.
22. Aug 17, 2026, 16:16 UTC
    investigating
    We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are still working to identify the root cause and will continue to post updates as we learn more and perform mitigation.
23. Aug 17, 2026, 16:36 UTC
    investigating
    We identified the problematic component and have taken corrective actions. There are strong signs of recovery but we are still working to completely restore service, with error rates still remaining slightly elevated. We will post further updates as recovery continues.
24. Aug 17, 2026, 16:59 UTC
    investigating
    The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
25. Aug 17, 2026, 17:30 UTC
    investigating
    Git Operations is experiencing degraded performance. We are continuing to investigate.
26. Aug 17, 2026, 17:34 UTC
    investigating
    We identified the problematic component and have taken corrective actions, but we are seeing residual impact across numerous services. We are continuing to apply additional mitigations and investigate the remaining impact.
27. Aug 17, 2026, 17:36 UTC
    investigating
    Issues is experiencing degraded performance. We are continuing to investigate.
28. Aug 17, 2026, 18:11 UTC
    investigating
    We identified the problematic component and have taken corrective actions, but we are seeing residual impact in the form of sporadic authentication failures. We are continuing to apply additional mitigations and investigate the remaining impact.
29. Aug 17, 2026, 18:23 UTC
    investigating
    The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
30. Aug 17, 2026, 18:48 UTC
    investigating
    API Requests is experiencing degraded availability. We are continuing to investigate.
31. Aug 17, 2026, 19:01 UTC
    investigating
    API Requests is operating normally.
32. Aug 17, 2026, 19:13 UTC
    investigating
    We are continuing to investigate sporadic authentication failures. We have partially disabled authentication token retries and have seen improvement, and we are monitoring impact before fully applying this mitigation.
33. Aug 17, 2026, 20:08 UTC
    investigating
    We are continuing to investigate sporadic failures affecting Copilot authentication in some applications. Copilot usage via the GitHub CLI and GitHub App are unaffected.
34. Aug 17, 2026, 20:22 UTC
    investigating
    Issues is operating normally.
35. Aug 17, 2026, 20:45 UTC
    investigating
    We are continuing to apply mitigations to address sporadic Copilot authentication failures in some applications. We expect full recovery within the next 30 minutes. Copilot usage via the GitHub CLI and GitHub App are unaffected.
36. Aug 17, 2026, 21:15 UTC
    resolved
    On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot. At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%. SAML/OIDC authentication, SCIM, and Team Sync were also affected, as well as Actions workflows in GHEC with Data Residency that depend on public workflow step definitions hosted on GitHub.com. Most services recovered by 16:36 UTC as our Central US datacenter recovered; Actions was degraded until approximately 18:03 UTC; and Copilot Token Service fully recovered by 21:02. Some of the failing traffic was moved from Central US to Northern Virginia where it was served successfully until the network failure in Central US was debugged and resolved. Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service. The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery. The retry storm in Northern VA was fixed by 1) temporarily reducing gateway retry logic with a PR and 2) blocking inbound Copilot Token Service token requests at the load balancers with a 403, and then gradually ramping back up traffic per-site to allow callers to succeed. Residual Copilot authentication failures continued because client retry behavior amplified load: a failed token operation could generate many extra requests and enter a retry loop. Copilot Token Service traffic increased from a normal 7–9K RPS to 70–100K RPS. Reducing gateway authentication retries and blocking retry-triggering responses stabilized Copilot Token Service and completed recovery. Complicating factors that impeded recovery included a number of scraping attacks on codeload endpoints. To prevent recurrence, our follow-up actions include: - Correcting autoscaling policies to account for service-mesh sidecar concurrency and capacity. - Auditing Istio request, concurrency, and scaling limits across affected services. - Reviewing retry limits and backoff behavior across gateways and clients. - Addressing the VS Code retry behavior that amplified Copilot token traffic. - Improving load-balancer capacity monitoring and regional failover safeguards.

Updates as published by GitHub (original).