GitHub incident

Latency issues across a number of services

Major Resolved View vendor source →

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

Started
Jul 23, 2026, 07:53 AM UTC
Resolved
Jul 23, 2026, 09:39 AM UTC
Duration
1h 45m
Detected by Pingoru
Jul 23, 2026, 07:53 AM UTC

Affected components

WebhooksIssuesPull RequestsActions

Update timeline

  1. investigating Jul 23, 2026, 07:53 AM UTC

    We are investigating reports of degraded availability for Actions, Issues and Webhooks

  2. investigating Jul 23, 2026, 08:25 AM UTC

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

  3. investigating Jul 23, 2026, 08:34 AM UTC

    We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

  4. investigating Jul 23, 2026, 09:18 AM UTC

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

  5. investigating Jul 23, 2026, 09:19 AM UTC

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

  6. investigating Jul 23, 2026, 09:22 AM UTC

    We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

  7. investigating Jul 23, 2026, 09:27 AM UTC

    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

  8. investigating Jul 23, 2026, 09:35 AM UTC

    Webhooks is operating normally.

  9. monitoring Jul 23, 2026, 09:39 AM UTC

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

  10. resolved Jul 23, 2026, 09:39 AM 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.