GitHub had a 1h 8m incident on 19 October 2026 that degraded Actions, Pages and Webhooks. The fault sat on GitHub's side, in the systems that process workflow runs, build sites and deliver webhook events.
Started
15:49 UTC
Duration
Lasted 1h 8m
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: GitHub Pages, Actions, Webhooks
What happened?
GitHub's status page opened an investigation at 15:49 UTC, flagging degraded performance for Actions and Pages. One minute later it added Webhooks to the list. By 15:56 GitHub had widened the description to say customers could see delays in workflow processing, site builds and webhook delivery, which covers three separate components rather than one. At 16:30 GitHub reported recovery following mitigation, but warned that delays could still affect Actions workflow status updates, Pages deployments, and check and webhook events tied to Actions runs. The incident was marked resolved at 16:56 UTC, a total of 1h 8m from first report to close. GitHub said a detailed root cause analysis would follow, but as of the resolved update none had been published, so the specific cause is not on the record. No user reports were filed during the window on this page. Over the last 90 days GitHub has logged 63 incidents with a median duration of 1 hour 21 minutes, which puts this one slightly below that median. Across all time GitHub averages 13 incidents a month, so an incident touching three components for a bit over an hour sits within its normal pattern rather than outside it.
Learning
UptimeRobot's own probes against GitHub's api-auth and raw-cdn components, run every 60 seconds from the EU and NA, stayed at 100% uptime over the past 24 hours and 7 days, and 99.999% over 30 days, with this incident not registered against those checks. That is not a contradiction. Actions, Pages and Webhooks are separate processing pipelines sitting behind GitHub's core API and CDN, so a delay in workflow runs or webhook delivery can happen while the authentication and content-serving paths you'd typically ping stay fully responsive. This is the general shape of a provider-side degradation: the parts you can reach from outside look fine, while the parts doing asynchronous work, builds, and event delivery back up. Watching your own endpoints only tells you whether your product can reach GitHub, not whether GitHub's queues behind the scenes are running on time. Over the last 30 days UptimeRobot recorded 15 such incidents on GitHub, all resolved, with a median duration of 1h 46m, so this kind of gap between "reachable" and "fully working" recurs regularly. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.