GitHub: Incident with Pull Requests
Is it fixed? Yes.
Resolved after 2 h 42 min. First reported Nov 13, 15:47 UTC, resolved Nov 13, 18:29 UTC. The vendor posted it on its status page first.
What happened
GitHub experienced an incident affecting Pull Requests where merge attempts timed out. The issue has since been resolved.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on status page
Incident with Pull Requests
Source - Official statement
Investigating: We are investigating reports of degraded availability for Pull Requests Update: We’re investigating an issue with Pull Requests where some attempts to merge are timing out.
Source - Official statement
⚠️ GitHub is reporting an incident: Incident with Pull Requests Update: We’re investigating an issue with Pull Requests where some attempts to merge are timing out. t.lpl.dev/yx7ZNpG
Source - Official statement
✅ Resolved: GitHub - Incident with Pull Requests
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Show all 6 updatesHide the full timeline
- First report on status page
Incident with Pull Requests
Source - Official statement
Investigating: We are investigating reports of degraded availability for Pull Requests Update: We’re investigating an issue with Pull Requests where some attempts to merge are timing out.
Source - Confirmed on Bluesky post
⚠️ GitHub is reporting an incident: Incident with Pull Requests
Source - Official statement
⚠️ GitHub is reporting an incident: Incident with Pull Requests Update: We’re investigating an issue with Pull Requests where some attempts to merge are timing out. t.lpl.dev/yx7ZNpG
Source - Official statement
✅ Resolved: GitHub - Incident with Pull Requests
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Evidence
4 reports · 1 Status, 3 BlueskyShow
- [1]Status First reportIncident with Pull Requests(opens official status page in a new tab)
Investigating: We are investigating reports of degraded availability for Pull Requests Update: We’re investigating an issue with Pull Requests where some attempts to merge are timing out.
by github status
- [2]Bluesky⚠️ GitHub is reporting an incident: Incident with Pull Requests(opens the official status page in a new tab)
⚠️ GitHub is reporting an incident: Incident with Pull Requests Update: We’re investigating an issue with Pull Requests where some attempts to merge are timing out. t.lpl.dev/yx7ZNpG
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments96% match
- [3]Bluesky🟠 GitHub: Incident with Pull Requests(opens Bluesky post in a new tab)
🟠 GitHub: Incident with Pull Requests Partial outage · Source Code Hosting · since 15:47 UTC Affected: Pull Requests Our probes: github.com reachable from all 17 regions Details ↗ · #GitHub
by outagewatch.flarewarden.com 0upvotes 1comments94% match
- [4]Bluesky✅ Resolved: GitHub - Incident with Pull Requests(opens the official status page in a new tab)
✅ Resolved: GitHub - Incident with Pull Requests
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments91% match
FAQ
What happened in the GitHub outage?
GitHub experienced an incident affecting Pull Requests where merge attempts timed out. The issue has since been resolved.
What is affected by the GitHub outage?
GitHub.
When did the GitHub outage start and end?
It started Nov 13, 15:47 UTC and was resolved Nov 13, 18:29 UTC, after 2 h 42 min.
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 4 reports from 2 independent sources, including the vendor’s own status page.