GitHub had three separate incidents on 30 October 2026, affecting Issues, Pages, Webhooks, Actions and Dependabot at different points in the day. The longest ran 2 hours 32 minutes. All three were GitHub-side faults, confirmed and resolved by GitHub's own status page.
Started
14:31 UTC
Duration
Lasted 35m
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: Webhooks, Actions, GitHub Pages, Issues
What happened?
The day started at 14:31 UTC with GitHub investigating reports of impacted performance across several services. GitHub's own updates describe a temporarily overloaded component that triggered a burst of errors between 14:21 and 14:30 UTC across numerous services, with Issues and Pages both flagged as degraded before recovering. That incident was resolved by 15:02, lasting 35 minutes. A second incident began at 17:50 UTC, this time hitting Actions, Pages and Webhooks together. GitHub's updates describe delays in Actions workflows, Pages deployments and webhook events, plus errors in code search and live updates, with mitigation steps taken before a return to normal by 19:23 UTC, a run of 1 hour 36 minutes. The third incident started at 20:59 UTC and centred on Dependabot, with elevated errors when viewing some Dependabot alerts. That one took the longest to clear, running 2 hours 32 minutes before resolution at 23:29 UTC. Across all three incidents, GitHub followed the same pattern: investigate, mitigate, monitor, resolve, each with a note that a detailed root cause analysis would follow. No such analysis is included in what's shown here, so the underlying cause of any of the three remains on GitHub's side to explain, not stated on the record. No user reports were filed during the window on this page.
Learning
UptimeRobot's own probes against GitHub's api-auth and raw-cdn components in the EU and North America stayed at 100% uptime over 24 hours and 7 days, and 99.999% over 30 days, with this incident day not registering against those checks. That is not a contradiction. The probes watch specific endpoints that kept answering normally while separate components, Issues, Pages, Webhooks, Actions and Dependabot, degraded one after another on GitHub's side. This is the shape outages often take with large platforms: the core API and content delivery paths can hold steady while feature-specific services queue, error, or delay behind the scenes. If your product depends on Actions runs completing, Pages deploying, or Dependabot alerts rendering, a green check on GitHub's main endpoints would have told you nothing about those failures. Your own monitoring covers whether your product is reachable. UptimeRobot now also watches the provider's side, so when something breaks you know which half it was without guessing.