GitHub outage on 28 October 2026
CriticalAn email when it goes down, and when it’s back.
“Disruption with some Copilot services”
On 28 October, GitHub had a disruption with some Copilot services from 14:13 to 16:08 UTC (1 h 55 min), during which several models, including GPT-5.3-Codex and MAI Code 1.1 Flash, had degraded availability in Copilot products and IDE surfaces. GitHub's status page said the problem was with an upstream model provider. The page reported recovery at 15:15, a brief renewed degradation at 15:24, and resolution at 15:28, earlier than the end time above, and it marked the Copilot component as having a minor issue only from 15:24 to 15:26. Musixmatch, Zoom and ClubReady also had problems at the same time.
GitHub’s own incident page ↗- When
- 14:13–16:08 UTC
- How long
- 1 h 55 min
- Incident open on its page
- 14:12–15:28 UTC
- Components affected
- 1
- GitHub, 30 days before
- 8 other outages
What broke when
From GitHub’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 129 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Copilot: degraded performance
- Fix in place, monitoring
- Copilot: back to normal
- Resolved
Where this comes from
Stackpulse reads GitHub’s official status page at www.githubstatus.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with GitHub. Names and logos belong to their owners.