Skip to main content
GitHub

Incident with Git Operations and Pull Requests

Major outage Lasted 1h 44m · started · GitHub's page

Level
confirmed
Worst impact
Major outage
Components
Pull Requests, Actions
Down Index
59of 100

What to do

  • Check whether you use GitHub Pull Requests, Actions. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 44m it lasted.

    Anything that failed between 2026-11-10 16:10 UTC and 2026-11-10 17:55 UTC may need a replay.
  • Subscribe to GitHub's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
  • Watch for the root-cause report GitHub said it would publish (said 2026-11-10 17:55 UTC); it shows on this page when it lands.

Root cause

GitHub said 2026-11-10 17:55 UTC that it would publish a root-cause report; none published yet.

Updates from GitHub 9

  1. investigating

    We are investigating reports of degraded performance for Actions and Pull Requests

    provider

  2. investigating

    Actions and Pull Requests are experiencing degraded availability. We are continuing to investigate.

    provider

  3. investigating

    We're investigating elevated response times for Git operations and pull requests. GitHub Actions workflows that are triggered from Pull Requests are delayed. We're working to mitigate the impact and will share updates as we learn more.

    provider

  4. investigating

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

    provider

  5. investigating

    We continue to investigate elevated response times for Git operations and pull requests. Some pull-request processing and Actions workflows are improving, but delays and failures persist. We're monitoring the impact and working to restore normal service.

    provider

  6. investigating

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

    provider

  7. investigating

    Actions is operating normally.

    provider

  8. investigating

    We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service.

    provider

  9. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-01c140c065

Is GitHub still down?

No, this incident was resolved 2026-11-10 17:55 UTC. For GitHub's live state, see https://down.guide/providers/github.

How long did it last?

1h 44m, from 2026-11-10 16:10 UTC to 2026-11-10 17:55 UTC, by the times GitHub posted.

What was affected?

GitHub named Pull Requests, Actions.

What caused it?

GitHub said 2026-11-10 17:55 UTC that it would publish a root-cause report; none is published yet.

Where does this come from?

GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.