Project updates delayed
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 latest update from GitHub.
State
Resolved
Started
10 d ago
2026-10-22 15:28 UTC
Lasted
11 h 2 min
until 2026-10-23 02:30 UTC
Worst impact
Degraded
Timeline
18 updatesInvestigating
9 h 27 min 86%
Monitoring
1 h 35 min 14%
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.
GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. We're continuing to work on the remaining delays and monitor recovery.
Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed. We have seen some recovery, and are working to add more capacity to accelerate the recovery.
Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed. We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.
Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.
Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
The other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.
Actions, Issues, Packages and Pull Requests are operating normally.
We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. We're continuing to work towards full recovery and monitoring for stability.
Some users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. We're working through multiple mitigation efforts and continuing to investigate.
API Requests is operating normally.
Packages is experiencing degraded performance. We are continuing to investigate.
API Requests is experiencing degraded performance. We are continuing to investigate.
Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and evaluating mitigation options to restore normal service.
Some users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. We're investigating and working to restore normal service.
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
Affected components
5GitHub in the last 90 days
Full historyIncidents in 90 days
46
Days with an incident
34
Median duration
1 h 29 min
This incident
7.4× the median
Other GitHub incidents
All incidentsGitHub·Incident with Dependabot
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.
GitHub·Incident with Actions, Pages, and Webhooks
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.
GitHub·Disruption with GitHub services
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.
GitHub·Disruption with Copilot Cloud services
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.
GitHub·Disruption with some Copilot services
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.
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