GitHub: Incident with Pull Requests
Affected components: ActionsPull Requests
Discussed on Hacker News
- 2 points · 0 comments · posted · posted 16 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Timeline of updates
- investigating
We are investigating reports of degraded performance for Pull Requests
- investigating
We’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify the cause and restore normal performance.
- investigating
We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. We’ll share another update as we learn more.
- investigating
We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not restored normal performance, and our teams are continuing to investigate. We’ll share another update as we learn more.
- investigating
We’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more.
- investigating
We’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more.
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating
We’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more.
- investigating
We’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more.
- monitoring
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
- monitoring
We’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance.
- resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Changes Rewindex caught on this incident
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
- Incident updated: Incident with Pull Requests
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub, started 2026-11-16 12:00 UTC, resolved after 4.4 h, 12 update(s); edited after publishing.
- Title
- Incident with Pull Requests
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/2zfqmghmg3s3
GitHub profileRecent GitHub incidentsAll outages on November 16, 2026GitHub in November 2026MarkdownJSON