Skip to main content
GitHub

Incident with Git Operations, Issues, Actions and Pull Requests

Major outage Lasted 48m · started · GitHub's page

Level
confirmed
Worst impact
Major outage
Components
Git Operations, Issues, Pull Requests, Actions
Down Index
46of 100

What to do

  • Check whether you use GitHub Git Operations, Issues, 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 48m it lasted.

    Anything that failed between 2026-10-07 17:17 UTC and 2026-10-07 18:04 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.

Root cause

We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause.
Read the postmortem

Updates from GitHub 5

  1. investigating

    We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

    provider

  2. investigating

    We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.

    provider

  3. monitoring

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

    provider

  4. monitoring

    All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

    provider

  5. resolved

    On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7

    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-f092aff10c

Is GitHub still down?

No, this incident was resolved 2026-10-07 18:04 UTC. For GitHub's live state, see https://down.guide/github.

How long did it last?

48m, from 2026-10-07 17:17 UTC to 2026-10-07 18:04 UTC, by the times GitHub posted.

What was affected?

GitHub named Git Operations, Issues, Pull Requests, Actions.

What caused it?

GitHub wrote: "We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause." The postmortem: https://stspg.io/4p8x0jnnsx7m

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.