GitHub outage, November 2026: Pages: degraded performance
GitHub marks Pages as degraded performance on its status page. Other parts of GitHub may still work; the GitHub page shows any wider incident.
OKResolved
Recorded from the status of Pages on GitHub's status page.
What happened
- Started
- Resolved
- Duration
- 3 minutes
- Impact
- minor
- Affected
- Pages
- Problem recorded
- Back to normal
Why it happened
GitHub has not given a cause in its updates. We never guess one.
How it was resolved
Pages went back to working normally on GitHub's status page at 5 Nov 2026, 3:08 am, 3 min after it was marked degraded. GitHub did not post an explanation for this part.
Timeline
Oldest first, from the first notice to the resolution. Recorded from the status of Pages on GitHub's status page.
- identified
GitHub marked Pages as degraded performance (it was working normally).
- resolved
GitHub marked Pages as working normally again.
What this means for a business (and what to check now)
- Retry anything that failed during the 3 minutes.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other GitHub incidents
- Actions: partial outage, resolved after 27 minutes
- Incident with Actions, resolved after 36 minutes
- Webhooks: degraded performance, resolved after 33 minutes
- Actions: degraded performance, resolved after 3 minutes
- Incident with Actions and Pages, resolved after 56 minutes
Hear about the next GitHub incident as it starts
Free email alerts when the official status changes, with what to do while it is down.