Skip to content

GitHub Pull Request Merges Time Out: Status Page Reports Major Incident on Nov. 13

By Outages Now Editors

Colorful workspace featuring a laptop with code editor and vibrant screens.
Photo: Daniil Komov / Pexels

Some attempts to merge pull requests on GitHub were timing out on Nov. 13, according to an incident GitHub’s status page first posted at 10:47 a.m. ET (15:47 UTC). As of Nov. 13 at 11:05 a.m. ET (16:05 UTC), the page rated the incident major, said GitHub was investigating and showed an overall status of “Minor Service Outage.” GitHub Copilot is tracked on the same status page.

What the status page says

GitHub filed the incident under Pull Requests and posted its last official update at 10:49 a.m. ET (15:49 UTC): “We’re investigating an issue with Pull Requests where some attempts to merge are timing out.”

At the time of the data, Pull Requests was the only component the page marked as not fully operational. GitHub had not said what caused the problem, how many users were affected or when it expected a fix.

What our checks show

Outages Now’s checks found that the GitHub Copilot front page at github.com/features/copilot answered from both of our checkpoints in Germany at the time of the data, with a fastest response of 502 ms. These checks only test whether the public website loads. They cannot see sign-in or anything inside GitHub, so a responding front page tells you nothing about whether merges go through.

Recent incidents

GitHub’s status page listed these earlier incidents in the past 30 days:

  • Nov. 12: a disruption with email delivery (minor)
  • Nov. 12: an incident with the Webhooks API (minor)
  • Nov. 11: impact across several GitHub products, among them Actions, Pages and Copilot products (critical)
  • Nov. 11: an incident with Webhooks (minor)

Why it matters

The reported problem was with merging pull requests, and the status page did not list Copilot itself as degraded. You can follow updates on GitHub’s status page or on our live GitHub Copilot status page. If a merge fails while the incident is open, waiting is usually the fix, and there is no need to reset a password or reinstall an app while GitHub says it is working on the problem.

Source: GitHub Copilot status page, as of Nov. 13 at 11:05 a.m. ET (16:05 UTC), and Outages Now’s own checks. This article is a snapshot and is not updated: see the live status of GitHub Copilot for the current data.

More outage news