GitHub incident

Disruption with some GitHub services

Major Resolved View vendor source →

GitHub experienced a major incident on July 24, 2026 affecting API Requests and Issues and 1 more component, lasting 1h 19m. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2026, 04:17 PM UTC
Resolved
Jul 24, 2026, 05:36 PM UTC
Duration
1h 19m
Detected by Pingoru
Jul 24, 2026, 04:17 PM UTC

Affected components

API RequestsIssuesPull RequestsActionsPagesCopilot

Update timeline

  1. investigating Jul 24, 2026, 04:17 PM UTC

    We are investigating reports of degraded performance for API Requests and Issues

  2. investigating Jul 24, 2026, 04:19 PM UTC

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

  3. investigating Jul 24, 2026, 04:20 PM UTC

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

  4. investigating Jul 24, 2026, 04:22 PM UTC

    We are investigating timeouts to some GitHub services

  5. investigating Jul 24, 2026, 04:26 PM UTC

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

  6. investigating Jul 24, 2026, 04:27 PM UTC

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

  7. investigating Jul 24, 2026, 04:28 PM UTC

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

  8. investigating Jul 24, 2026, 04:40 PM UTC

    We have applied a mitigation and are monitoring for recovery

  9. investigating Jul 24, 2026, 04:41 PM UTC

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

  10. investigating Jul 24, 2026, 05:16 PM UTC

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

  11. investigating Jul 24, 2026, 05:24 PM UTC

    We are seeing recovery across all services

  12. resolved Jul 24, 2026, 05:36 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.