Key takeaways
- GitHub reported a burst of errors across several services at 14:31 UTC on October 30, resolved at 15:02 UTC.
- A second incident from 17:50 UTC delayed Actions, Pages and webhooks, and was in monitoring at 18:32 UTC.
- GitHub has not yet given a root cause for either incident.
GitHub had two incidents on October 30, 2026, according to its status page. If you are asking whether GitHub is down, the second one hit Actions, Pages and webhooks, and services had recovered by 18:32 UTC, though GitHub was still monitoring and had not found a root cause.
What the status page says
The first incident, titled "Disruption with GitHub services", began at 14:31 UTC. GitHub says a temporarily overloaded component caused a burst of errors across several services between 14:21 and 14:30 UTC. Issues and Pages ran degraded. It was marked resolved at 15:02 UTC, and a root cause analysis is pending.
The second incident, "Incident with Actions, Pages, and Webhooks", started at 17:50 UTC. GitHub reported delays in Actions workflows, Pages deployments and webhook events, along with errors in code search and live updates. At 18:32 UTC the status was "monitoring": services had recovered after a mitigation, and GitHub was still investigating the cause.
What to do if your workflows are stuck
Delayed Actions runs and webhooks usually catch up on their own once the incident clears. Check the status page before re-running jobs or changing your configuration, since the delay may not be your setup. If a run still looks stuck after the incident is marked resolved, re-run it.
This follows GitHub's announcement that Enterprise now includes Copilot for every licensed user and its capacity expansion earlier this week.
GitHub's status page lists code search and live updates among the affected features, so some pages may have shown stale data during the incident.
GitHub has said a root cause analysis for the first incident is pending. The status page is where any update will appear.
