‹ Back to incident history

Increase in timeouts for some unauthenticated users

ResolvedMinor incidentGitHub
Sunday, November 8, 2026 18:36 – Sunday, November 8, 2026 20:32 (1 hr 56 min)
Affected components
API Requests
Updates
ResolvedSunday, November 8, 2026 20:32

On November 8, 2026, between 08:43 and 12:29 UTC, unauthenticated requests to github.com and the GitHub REST API experienced elevated error rates. During this period, 11.3% of unauthenticated requests and 46.1% of release asset download requests failed. Authenticated requests were largely unaffected.<br /><br />Initial errors occurred in a backend service handling unauthenticated web traffic. A subsequent traffic spike caused high CPU utilization on servers in our caching layer. Some servers remained unhealthy after the spike ended, prolonging the disruption. We restored service by restarting caching software and rebooting affected servers.<br /><br />We are improving monitoring to detect these failures sooner, investigating why affected servers did not recover automatically, and reviewing caching behavior to better protect backend services during failures.

MonitoringSunday, November 8, 2026 20:29

The degradation has been mitigated. We are monitoring to ensure stability.

InvestigatingSunday, November 8, 2026 19:56

The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

InvestigatingSunday, November 8, 2026 19:50

We've identified a problematic component and are working to redeploy it.

InvestigatingSunday, November 8, 2026 19:20

API Requests is experiencing degraded performance. We are continuing to investigate.

InvestigatingSunday, November 8, 2026 19:16

We are continuing to investigate degraded performance primarily for unauthenticated users.

InvestigatingSunday, November 8, 2026 18:36

We are investigating reports of impacted performance for some GitHub services.

Incident data from the GitHub official status page:Read the official incident

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