Key takeaways
- GitHub opened a major incident at 09:49 UTC on November 4 for pull requests, Git operations and issues.
- Pull requests are in partial outage; Git operations, issues and Actions are degraded.
- At 10:38 UTC GitHub was still investigating and had given no cause or fix time.
GitHub is down for some users on Wednesday, November 4. GitHub's status page shows a major incident, "Pull Requests, Git Operations and Issues", that began at 09:49 UTC and was still marked "investigating" at 10:38 UTC, almost an hour later.
What the status page says
GitHub first reported degraded performance for Git operations, issues and pull requests at 09:49 UTC. One minute later it added Actions. At 09:53 UTC it raised pull requests to a partial outage, meaning some requests fail while others go through.
The latest update, posted at 10:38 UTC, reads: "We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues." GitHub has not given a cause or an estimate for when it will be fixed.
| Component | Status at 10:38 UTC |
|---|---|
| Pull Requests | Partial outage |
| Git Operations | Degraded performance |
| Issues | Degraded performance |
| Actions | Degraded performance |
What you may see
GitHub has not listed specific error messages. Degraded Git operations usually show up as slow or failing pushes, pulls and clones. Failed requests in pull requests and issues can mean pages that don't load or comments that don't save. "Intermittent" means the same action can fail once and work on the next try.
Earlier on November 4, GitHub also resolved a separate incident that raised task errors in Copilot Mission Control. It closed at 10:01 UTC, before this one was updated. GitHub said a root cause analysis will follow for that one.
What to do while it lasts
- Check the GitHub status page for the current state. It is the only source for what GitHub has confirmed.
- Retry failed pushes and pulls after a short wait. With intermittent failures, a retry often works.
- Hold off on merging or re-running important Actions jobs if you can. Degraded components can leave a job half finished.
- Keep local commits. Git stores them on your machine, so you lose nothing by waiting to push.
For an earlier GitHub incident, see our report on the October 30 disruption to Actions, Pages and webhooks. This article will be updated when GitHub marks the current incident resolved.
