Disruption with some GitHub services
On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages.<br /><br />This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mitigated the incident by shifting the database traffic to a healthy region.<br /><br />We are working to make regional database failover faster and more complete, reduce timeouts so these pages fail fast instead of hanging, and add latency-based alerting to reduce our time to detection and mitigation of issues like this one in the future. We continue to partner with our cloud provider to understand the underlying network failure.
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
We are investigating reports of impacted performance for some GitHub services.
About this data
Where does the incident data for GitHub come from?
Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.
How do I read the component status bars?
Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.
Why is history missing for some services?
Only services with a public official status page are included.
How is duration calculated?
Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.
See the full service list and live status in the status overview