WhatBrokeToday
GTA 6FAQ
GitHub

GitHub: Incident with Pull Requests

medium

Is it fixed? Yes.

Resolved after 4 h 26 min. First reported Nov 16, 11:59 UTC, resolved Nov 16, 16:26 UTC. The vendor posted it on its status page first.

What happened

GitHub is investigating elevated timeouts and degraded performance when merging pull requests, causing some users to be unable to complete merges successfully.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix

Timeline

  1. Investigating(done)
  2. Workaround available(skipped)
  3. Resolved(current)
  1. First report on status page

    Incident with Pull Requests

    Source
  2. Official statement

    Investigating: We are investigating reports of degraded performance for Pull Requests Update: We’re investigating elevated timeouts when merging pull requests.

    Source
  3. Official statement

    ⚠️ GitHub is reporting an incident: Incident with Pull Requests Update: We’re investigating elevated timeouts when merging pull requests.

    Source
  4. Official statement

    ✅ Resolved: GitHub - Incident with Pull Requests

    Source
  5. Status changed

    Status changed: investigating → resolved (official status page reports resolution).

Show all 7 updates
  1. First report on status page

    Incident with Pull Requests

    Source
  2. Official statement

    Investigating: We are investigating reports of degraded performance for Pull Requests Update: We’re investigating elevated timeouts when merging pull requests.

    Source
  3. Confirmed on Bluesky post

    ⚠️ GitHub is reporting an incident: Incident with Pull Requests

    Source
  4. Official statement

    ⚠️ GitHub is reporting an incident: Incident with Pull Requests Update: We’re investigating elevated timeouts when merging pull requests.

    Source
  5. Confirmed on Hacker News thread

    Incident with Pull Requests

    Source
  6. Official statement

    ✅ Resolved: GitHub - Incident with Pull Requests

    Source
  7. Status changed

    Status changed: investigating → resolved (official status page reports resolution).

Evidence

5 reports · 1 Status, 1 HN, 3 BlueskyShow
  1. [1]
    Status First report
    Incident with Pull Requests(opens official status page in a new tab)

    Investigating: We are investigating reports of degraded performance for Pull Requests Update: We’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify the cause and restore normal performance.

    by github status

  2. [2]
    Bluesky
    ⚠️ GitHub is reporting an incident: Incident with Pull Requests(opens the official status page in a new tab)

    ⚠️ GitHub is reporting an incident: Incident with Pull Requests Update: We’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify th… t.lpl.dev/O0Rg0Lp

    by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments96% match

  3. [3]
    HN
    Incident with Pull Requests(opens Hacker News thread in a new tab)

    by dorianmariewo 2upvotes 0comments89% match

  4. [4]
    Bluesky
    👻 A eulogy for GitHub, down since Nov 16, 2026, 11:59 UTC(opens Bluesky post in a new tab)

    👻 A eulogy for GitHub, down since Nov 16, 2026, 11:59 UTC Oh, GitHub, you slumbered, sweet and deep, With pull requests tangled in a sleep. A timeout’s hush, a pause so brief, While merging dreams met with disbelief. Source: www.githubstatus.com

    by downtimeghost.bsky.social 0upvotes 1comments86% match

  5. [5]
    Bluesky
    ✅ Resolved: GitHub - Incident with Pull Requests(opens the official status page in a new tab)

    ✅ Resolved: GitHub - Incident with Pull Requests

    by telescope.littleplanetlabs.comOpens the official status page 0upvotes 0comments91% match

FAQ

What happened in the GitHub outage?

GitHub is investigating elevated timeouts and degraded performance when merging pull requests, causing some users to be unable to complete merges successfully.

What is affected by the GitHub outage?

GitHub. Also affected at the same time: Kubernetes, Bun.

When did the GitHub outage start and end?

It started Nov 16, 11:59 UTC and was resolved Nov 16, 16:26 UTC, after 4 h 26 min.

How do I get alerts for GitHub?

Subscribe to the GitHub RSS feed for every new GitHub incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether GitHub is down. GitHub feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 5 reports from 3 independent sources, including the vendor’s own status page.