GitHub outage on October 22, 2026: Errors loading Issues, Pull Requests, and search results
GitHub has reported an incident affecting GitHub since 15:28 UTC on 22 October 2026 (5 hours 59 minutes so far).
Open
Official incident reported by GitHub
- Started
- 15:28
- 22 Oct 2026 UTC
- Status
- Open
- not resolved yet
- Duration
- 5h 59m
- 5 hours 59 minutes so far
- Impact
- Minor
- as rated by GitHub
- Updates
- 14
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Errors loading Issues, Pull Requests, and search results
-
Official
Investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
-
Official
Investigating
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.
-
Official
Investigating
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.
-
Official
Investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
-
Official
Investigating
Packages is experiencing degraded performance. We are continuing to investigate.
-
Official
Investigating
API Requests is operating normally.
-
Official
Investigating
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.
-
Official
Investigating
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.
-
Official
Investigating
Actions, Issues, Packages and Pull Requests are operating normally.
-
Official
Investigating
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.
-
Official
Investigating
The other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
-
Official
Investigating
Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
-
Official
Investigating
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.
-
Official
Investigating
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.
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.
Does your product depend on GitHub?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.