GitHub favicon

GitHub outage on 2026-11-13

github.com
November 2026 13 Major incident

GitHub had two separate incidents on 13 November 2026. One hit Pull Requests for 2h 45m with merges timing out, and a second affected Copilot's GPT model availability for 1h 15m. Both were GitHub's side of the service, not yours.

Started

15:47 UTC

Duration

Lasted 2h 45m

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: Pull Requests

What happened?

The first incident started at 15:47 UTC with GitHub investigating degraded availability for Pull Requests, and within two minutes they'd narrowed it to merge attempts timing out. By 16:12 GitHub said the issue had initially hit 3% of requests and was down to less than 1%, with the team continuing to monitor recovery. GitHub moved to monitoring status at 17:28, said the degradation had been mitigated, and kept watching stability until it marked the incident resolved at 18:29, 2h 45m after it began. No root cause has been published yet, GitHub only said a detailed analysis would follow when available. The second incident started separately at 20:13 UTC and concerned Copilot, not Pull Requests. GitHub said gpt-5.6-sol-fast, gpt-5.6-sol, gpt-6.1-terra and gpt-6-luna were degraded in Copilot products and IDE surfaces, and attributed this to an issue with an upstream model provider. GitHub recommended switching models or using 'Auto' while they worked with that provider. The upstream provider made mitigations by 21:17, and GitHub resolved the incident at 21:27, 1h 15m after it opened. Across both incidents GitHub logged 13 updates and listed Pull Requests as the only affected component on its status page, though the Copilot incident's title names a second area not reflected in that component list. No user reports were filed during either window.

Learning

GitHub's status page is the only record of either incident, since no user reports came in during either window, and your own uptime checks against GitHub would most likely have stayed green through both. The Pull Requests fault only affected a small percentage of merge attempts at its worst, a partial degradation that an external check hitting a healthy endpoint could easily miss. The Copilot incident sat one layer further out still: GitHub traced it to an upstream model provider, meaning the fault wasn't even inside GitHub's own infrastructure, it was a dependency of a dependency. Either way, a check that confirms GitHub's API or CDN is reachable tells you nothing about whether a specific feature like merging or a specific AI model is actually working for the people using it. This is the shape worth remembering: core reachability and feature-level correctness are different things, and only one of them shows up in a simple ping. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.