GitHub Security Incident Reported
Is it fixed? Not yet.
Ongoing since Nov 18, 18:43 UTC. First reported Nov 18, 18:43 UTC. Not on the vendor’s status page yet.
What happened
Reports indicate a security incident affecting GitHub, prompting expressions of support for GitHub security staff.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Timeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on Bluesky post
okay yeah probably security incident then.
Source
Evidence
1 report · 1 BlueskyShow
- [1]Bluesky First reportokay yeah probably security incident then.(opens Bluesky post in a new tab)
okay yeah probably security incident then. #hugops to Github security
by lizthegrey.com 4upvotes 0comments
FAQ
What happened in the GitHub outage?
Reports indicate a security incident affecting GitHub, prompting expressions of support for GitHub security staff.
What is affected by the GitHub outage?
GitHub.
When did the GitHub outage start and end?
It started Nov 18, 18:43 UTC and is still ongoing (9 h 32 min so far). This page updates as it develops.
How do I get alerts for GitHub?
Subscribe to the GitHub RSS feed for every new GitHub incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether GitHub is down. GitHub feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.