GitHub incident

Incident with GitHub.com

Critical Resolved View vendor source →

GitHub experienced a critical incident on August 17, 2026 affecting Git Operations and Webhooks and 1 more component, lasting 7h 35m. The incident has been resolved; the full update timeline is below.

Started
Aug 17, 2026, 01:40 PM UTC
Resolved
Aug 17, 2026, 09:15 PM UTC
Duration
7h 35m
Detected by Pingoru
Aug 17, 2026, 01:40 PM UTC

Affected components

Git OperationsWebhooksAPI RequestsIssuesPull RequestsActionsPagesCopilot

Update timeline

  1. investigating Aug 17, 2026, 01:40 PM UTC

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

  2. investigating Aug 17, 2026, 01:41 PM UTC

    API Requests is experiencing degraded performance. We are continuing to investigate.

  3. investigating Aug 17, 2026, 01:42 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  4. investigating Aug 17, 2026, 01:44 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  5. investigating Aug 17, 2026, 01:45 PM UTC

    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. investigating Aug 17, 2026, 01:46 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  7. investigating Aug 17, 2026, 01:58 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  8. investigating Aug 17, 2026, 02:04 PM UTC

    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. investigating Aug 17, 2026, 02:24 PM UTC

    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. investigating Aug 17, 2026, 02:31 PM UTC

    Copilot is experiencing degraded availability. We are continuing to investigate.

  11. investigating Aug 17, 2026, 02:45 PM UTC

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

  12. investigating Aug 17, 2026, 02:49 PM UTC

    Issues is experiencing degraded availability. We are continuing to investigate.

  13. investigating Aug 17, 2026, 02:54 PM UTC

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

  14. investigating Aug 17, 2026, 02:58 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  15. investigating Aug 17, 2026, 02:58 PM UTC

    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. investigating Aug 17, 2026, 02:58 PM UTC

    Webhooks is experiencing degraded availability. We are continuing to investigate.

  17. investigating Aug 17, 2026, 03:01 PM UTC

    API Requests is experiencing degraded availability. We are continuing to investigate.

  18. investigating Aug 17, 2026, 03:10 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

  19. investigating Aug 17, 2026, 03:21 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  20. investigating Aug 17, 2026, 03:40 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  21. investigating Aug 17, 2026, 03:42 PM UTC

    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. investigating Aug 17, 2026, 04:16 PM UTC

    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. investigating Aug 17, 2026, 04:36 PM UTC

    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. investigating Aug 17, 2026, 04:59 PM UTC

    The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

  25. investigating Aug 17, 2026, 05:30 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  26. investigating Aug 17, 2026, 05:34 PM UTC

    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. investigating Aug 17, 2026, 05:36 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  28. investigating Aug 17, 2026, 06:11 PM UTC

    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. investigating Aug 17, 2026, 06:23 PM UTC

    The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.

  30. investigating Aug 17, 2026, 06:48 PM UTC

    API Requests is experiencing degraded availability. We are continuing to investigate.

  31. investigating Aug 17, 2026, 07:01 PM UTC

    API Requests is operating normally.

  32. investigating Aug 17, 2026, 07:13 PM UTC

    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. investigating Aug 17, 2026, 08:08 PM UTC

    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. investigating Aug 17, 2026, 08:22 PM UTC

    Issues is operating normally.

  35. investigating Aug 17, 2026, 08:45 PM UTC

    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. resolved Aug 17, 2026, 09:15 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.