Incident with Actions
GitHub Actions had degraded performance. Some workflow runs had delays or errors when they started. GitHub reports that the incident is resolved and that it lasted 52 minutes.
State
Resolved
Started
Lasted
52 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
16 min 31%
Monitoring
36 min 69%
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 affecting Actions has been mitigated. We are monitoring to ensure stability.
Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
We are investigating reports of degraded performance for Actions
Affected components
1GitHub in the last 90 days
Full historyIncidents in 90 days
55
Days with an incident
39
Median duration
1 h 15 min
This incident
31% shorter than the median
Other GitHub incidents
All incidentsGitHub·Degraded performance for multiple GitHub services
GitHub reports degraded performance and errors for Issues, Actions, and Pages. GitHub applied a mitigation and monitored the services. The incident is resolved. It lasted 45 minutes.
GitHub·Incident with Actions
GitHub Actions had degraded availability and some jobs had delayed status updates. GitHub identified the issue, applied mitigations, and monitored recovery. The incident is resolved and lasted 36 minutes.
GitHub·Incident with Actions and Pages
GitHub reported degraded performance and availability for Actions, Pages, and Webhooks. GitHub identified the issue and applied mitigations. The incident is resolved and lasted 56 minutes.
GitHub·Incident with Pull Requests, Git Operations and Issues
GitHub reports a partial outage. Pull Requests, Git Operations, Issues, API Requests and Actions do not work correctly. GitHub reports that the incident is resolved. The incident lasted 2 hours.
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.
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.cc/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.cc/feed.xml?providers=github/feed subscribe https://outages.cc/feed.xml?providers=githubFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane