GitHub had four separate incidents on 4 November 2026, touching Git Operations, Pull Requests, Issues, Actions, API Requests, GitHub Pages and Webhooks. The longest ran 2 hours 4 minutes. All four were GitHub's own infrastructure, not anything in your repository or workflow.
Started
09:49 UTC
Duration
Lasted 2h 4m
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: Actions, GitHub Pages, Webhooks, Git Operations, Issues, Pull Requests, API Requests
What happened?
The day opened at 08:45 UTC with increased errors in Copilot Mission Control, where GitHub said listing and creating tasks was failing at around a 2.5% error rate because of upstream database throttling tied to a specific client version. That one took 1 hour 17 minutes to resolve. Less than an hour later, at 09:49, a second and larger incident began, hitting Pull Requests, Git Operations and Issues, then spreading to Actions and API Requests as the morning went on. GitHub's updates on that incident describe "elevated errors and intermittent failures" and note that some requests could fail or be delayed while they worked toward mitigation. That incident ran 2 hours 4 minutes, the longest of the day, with the API Requests, Git Operations, Issues and Pull Requests degradation mitigated at 11:30 and the remaining Actions piece mitigated 13 minutes later. Things stayed quiet through the afternoon until 16:05, when Actions and Pages began degrading, soon joined by Webhooks. GitHub traced that one to "an issue with events that might trigger Actions" and applied mitigations, warning that customers might see delayed status updates for their jobs. That incident closed at 17:01, 57 minutes after it started. A fourth incident started at 17:40, again affecting Actions, with GitHub citing the same event-trigger issue and mitigating it by 18:07, for a total run of 38 minutes. Across all four incidents, GitHub filed 27 updates and no root cause analysis has been published for any of them yet. No user reports were logged during the window on this page.
Learning
UptimeRobot's own probes against GitHub's api-auth and raw-cdn components, checked every 60 seconds from both EU and NA regions, show 100% uptime across the last 24 hours, 7 days and 30 days, and this incident was not registered against those checks. That is not a contradiction. The parts of GitHub that broke on 4 November, task queuing in Copilot Mission Control, Actions event triggers, Pull Request and Git Operations throughput, sit behind layers that a simple endpoint check does not exercise. A probe can confirm the front door is open while the specific workflow you depend on, like triggering a build or pushing a commit, is degraded inside. That is the general shape of this kind of failure: availability looks fine from outside, but the operation you actually need is throttled or erroring upstream. Your own monitoring tells you whether your product responded to a user, but it cannot tell you whether the delay or error traces back to GitHub rather than your code. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.