Incident with Pull Requests
GitHub Pull Requests and Actions had degraded performance. Some users had difficulty merging pull requests. GitHub reports that the incident is resolved. It lasted 4 hours and 27 minutes.
State
Resolved
Started
Lasted
4 h 27 min
Worst impact
Degraded
Timeline
12 updatesInvestigating
4 h 10 min 94%
Monitoring
17 min 6%
Updates
Times in UTCAs posted by GitHub
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.
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.
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
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.
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.
Actions is experiencing degraded performance. We are continuing to investigate.
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.
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.
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.
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.
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.
We are investigating reports of degraded performance for Pull Requests
Affected components
2GitHub in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
45
Median duration
1 h 15 min
This incident
3.5× the median
Other GitHub incidents
All incidentsGitHub·Copilot experiencing degraded model availability for some GPT models
GitHub Copilot has degraded availability for the GPT models gpt-5.6-sol-fast, gpt-5.6-sol, gpt-6.1-terra, and gpt-6-luna in Copilot products and IDE surfaces. GitHub reports that the incident is resolved. The outage lasted about 74 minutes. GitHub stated that an upstream model provider caused the issue.
GitHub·Incident with Pull Requests
GitHub Pull Requests had degraded availability. Some merge attempts timed out. GitHub reported the incident as resolved. The incident lasted about 2 hours and 42 minutes.
GitHub·Disruption with Email Delivery
GitHub email delivery did not work for account sign-in, new account sign-up, email address verification, password resets, and email notifications. GitHub reports that the incident is resolved and that it lasted 2 hours and 7 minutes.
GitHub·Incident with Webhooks API
GitHub Webhooks API had timeouts and errors that affected about 1% of customer traffic. GitHub mitigated the degradation and monitored stability. The incident is resolved and lasted about 51 minutes.
GitHub·Impact across multiple GitHub products including Actions, Pages, and Copilot products.
GitHub reports a major outage that affected Webhooks, Actions, Pages, and Copilot. GitHub later reported recovery across all services and monitored the fix. GitHub marked the incident resolved. The outage lasted 33 minutes.
Follow GitHub
Your coding agent knows when GitHub is down, and tells you when a failure is theirs, not yours. You can also get GitHub incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "github" and tell me if GitHub has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=github/feed subscribe https://outages.live/feed.xml?providers=githubFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane