Incident with Actions and Checks API
GitHub Actions, the Checks API, Webhooks, and Pages had an outage. GitHub reports that the incident is resolved. It lasted 47 minutes.
State
Resolved
Started
Lasted
47 min
Worst impact
Major outage
Timeline
8 updatesInvestigating
33 min 70%
Monitoring
14 min 30%
Updates
Times in UTCAs posted by GitHub
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
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.
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, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
Pages is experiencing degraded performance. We are continuing to investigate.
We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.
Webhooks is experiencing degraded performance. We are continuing to investigate.
Actions is experiencing degraded availability. We are continuing to investigate.
Affected components
3GitHub in the last 90 days
Full historyIncidents in 90 days
60
Days with an incident
42
Median duration
1 h 16 min
This incident
38% shorter than the median
Other GitHub incidents
All incidentsGitHub·Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
GitHub reports degraded availability for the GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol models in Copilot products and IDE surfaces. GitHub mitigated the issue and monitored the service for stability. The outage is resolved and lasted 50 minutes.
GitHub·Incident with Webhooks and Actions
GitHub reports a partial outage that affects Webhooks and Actions. Actions runs and webhook deliveries had delays and degraded availability. GitHub resolved the incident in 1 hour and 50 minutes.
GitHub·Increased timeouts due to surge in anonymous users
GitHub reports 504 Gateway Timeout errors for anonymous and unauthenticated requests. The errors affect users who are not logged in and release downloads. Logged-in users and authenticated requests are unaffected. GitHub resolved the incident after 3 hours and 11 minutes.
GitHub·Increase in timeouts for some unauthenticated users
GitHub reports timeouts for some unauthenticated users on API Requests. GitHub identified a problem component and redeployed it. The incident is resolved. It lasted 1 hour and 57 minutes.
GitHub·Degraded performance for multiple GitHub services
GitHub Issues, Actions, and Pages had degraded performance. GitHub reports that the incident is resolved. The incident lasted 45 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