What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusAffected services
Updates (9)
- Oct 6, 2026, 11:40 PMSeveral services are degraded
On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximately 19:50 UTC once the migration's calls stopped; GEI migrations were reenabled at 23:32 UTC after a c
GitHub ↗ - Oct 6, 2026, 10:40 PMSeveral services are degraded
We are deploying a mitigation and plan to resume migrations shortly thereafter
GitHub ↗ - Oct 6, 2026, 09:29 PMSeveral services are degraded
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
GitHub ↗ - Oct 6, 2026, 08:57 PMSeveral services are degraded
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
GitHub ↗ - Oct 6, 2026, 08:26 PMSeveral services are degraded
The degradation has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Oct 6, 2026, 08:22 PMSeveral services are degraded
A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
GitHub ↗ - Oct 6, 2026, 08:12 PMSeveral services are degraded
Pull Requests is operating normally.
GitHub ↗ - Oct 6, 2026, 08:04 PMSeveral services are degraded
Webhooks is operating normally.
GitHub ↗ - Oct 6, 2026, 07:57 PMSeveral services are degraded
We are investigating reports of degraded performance for Pull Requests and Webhooks
GitHub ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow GitHub's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.