Disruption with GitHub services
On October 30, 2026, between 14:20 and 14:29 UTC, customers experienced errors across multiple GitHub services. Affected services include Git operations, GraphQL and REST API, Pull Requests, and Issues. At peak, about 3.5% of API requests failed. <br /><br />The incident was caused by slow database requests that held connections open longer than expected, which used all available connections to one of our primary databases. Service recovered at 14:29 UTC once connections were released. <br /><br />Since the incident, we have fixed the code path that held connections open and increased the processing capacity of our database connection layer. We are also improving alerting for this type of overload.
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
A temporarily overloaded component triggered a burst of errors between 14:21 and 14:30 UTC across numerous services. Component health has returned to normal and we continue to monitor while investigating the root cause.<br />
Issues is operating normally.
Pages is experiencing degraded performance. We are continuing to investigate.
Issues is experiencing degraded performance. We are continuing to investigate.
We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation.
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