GitHub's API Requests, Issues, Pull Requests and Actions degraded for 12 minutes on 26 October 2026. GitHub's own status page confirms the fault sat on their side, not yours.
Started
18:48 UTC
Duration
Lasted 12m
Source
IsDown
Next time
GitHub is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Issues, API Requests, Actions, Pull Requests
What happened?
GitHub logged one incident on 26 October 2026, starting at 18:48 UTC and lasting 12 minutes. The title names four affected components: API Requests, Issues, Pull Requests and Actions. GitHub's first update, posted at 18:48, said they were investigating reports of degraded performance across those four areas. Two minutes later, at 18:50, they reported the degradation had already been mitigated and said they were monitoring for stability. A further update at 18:54 gave more detail: elevated latency hit REST API requests, including Checks, plus some Actions, Issues, Pull Requests and GraphQL functionality, with some requests slow or timing out, and notifications delayed from 17:59 UTC to 18:40 UTC. That same update said all services had recovered. The incident was marked resolved at 18:57, with GitHub promising a root cause analysis once one is available. No such analysis has been published since. No user reports were filed during this window, so there is no independent account of how this felt to use. GitHub's 90 day history shows 61 incidents with a median duration of 1 hour 21 minutes, which makes this 12 minute incident shorter than most. Over the same period UptimeRobot's own probes against GitHub recorded 19 incidents with a median duration of 1 hour 13 minutes, all resolved.
Learning
UptimeRobot's probes against GitHub's api-auth and raw-cdn endpoints, run from the EU and North America every 60 seconds, show 100% uptime over the last 24 hours and 7 days, and 99.999% over 30 days, with this incident not registered against those probes at all. That is not a contradiction. The fault GitHub described was latency and timeouts on REST API and GraphQL calls tied to specific features like Checks and notifications, a narrower slice than the raw connectivity and authentication paths UptimeRobot's probes test. A service can answer a basic health check cleanly while a particular request type, under particular load, slows down or times out for real users elsewhere in the stack. This is the general shape of a provider side outage that external monitoring is not built to catch: the endpoint is reachable, but the feature behind it is degraded. Watching your own application would only show you the symptom, slow requests or failed Actions runs, without telling you whether the fault was yours or GitHub's. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.