Incident with Actions and Pages
GitHub reports degraded performance and availability for Actions, Pages, and Webhooks. GitHub identified the issue, applied mitigations, and monitored recovery. The incident is resolved and lasted about 56 minutes.
State
Resolved
Started
Lasted
56 min
Worst impact
Partial outage
Timeline
8 updatesInvestigating
46 min 82%
Monitoring
10 min 18%
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.
The degradation has been mitigated. We are monitoring to ensure stability.
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
Actions is experiencing degraded availability. We are continuing to investigate.
Webhooks is experiencing degraded performance. We are continuing to investigate.
We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
We are investigating reports of degraded performance for Actions and Pages
Affected components
3GitHub in the last 90 days
Full historyIncidents in 90 days
52
Days with an incident
37
Median duration
1 h 23 min
This incident
33% shorter than the median
Other GitHub incidents
All incidentsGitHub·Incident with Pull Requests, Git Operations and Issues
GitHub reports a partial outage that affects Pull Requests, Git Operations, Issues, API Requests, and Actions. GitHub mitigated the degradation and then monitored stability. GitHub states that the incident is resolved. The incident lasted 120 minutes.
GitHub·Increased task-related errors for Copilot Mission Control
Copilot Mission Control had increased errors in listing and creating tasks. GitHub reports that the incident is resolved. The incident lasted about 77 minutes.
GitHub·Incident with Git Operations
Git Operations had degraded performance. GitHub reported that the incident is resolved. The incident lasted 1 hour and 45 minutes.
GitHub·Incident with API, Git, and Copilot requests
GitHub reports degraded performance for API Requests, Issues, and Copilot. GitHub reports that the incident is resolved. The incident lasted 31 minutes.
GitHub·Elevated errors on GPT-5.4 Nano
GPT-5.4 Nano had elevated errors in Copilot products and IDE surfaces. The Copilot AI Model Providers component was affected. GitHub reports the incident resolved after 38 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