rewindex

ChangesGitHubIncident with Pull Requests

GitHub: Incident silently edited: Incident with Pull Requests

Silent editNot classified yetChanged www.githubstatus.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Discussed on Hacker News

Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.

Incident page: the full timeline of updates

What changed

Struck in red is what GitHub removed; blue is what they added. Muted text is unchanged context.

ChangedUpdateresolved#1
Before: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
After: On November 16, 2026, between 09:30 and 15:55 UTC, some pull request merges on GitHub timed out. On average, 2.9% of merge attempts timed out, with a peak of 7.1% at 15:17 UTC. Some GitHub Actions workflow runs triggered by pull requests were also delayed. Git operations such as push and fetch stayed available, with higher latency. This was a repeat of a shorter event on November 13, between 13:15 and 17:50 UTC, when 1.7% of merges timed out. Both events had the same cause: some of the storage servers that hold Git repository data reached their disk read bandwidth limits. A merge must be written to every copy of a repository, so one overloaded server slowed merges for every repository it hosts. Read load on these servers had been growing as part of a planned move of repositories to new infrastructure. A disk configuration setting on those servers also made them read far more data than necessary, which cut their usable bandwidth roughly in half. We mitigated the incident by correcting that setting and moving some load away from the busiest servers. The corrected setting is now applied permanently across our storage fleet. We are adding storage capacity in the affected region and ale …

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

History of this incident

TodayFriday, November 20Fri, Nov 20

1 rewrite

Monday, November 16

10 incident changes

Cite this

Incident silently edited: Incident with Pull Requests on GitHub’s status page, changed 2026-11-20 18:53 UTC (change 11 of 11).

Title
Incident silently edited: Incident with Pull Requests
Vendor
GitHub
Date
URL
https://rewindex.com/change/ref0bd56c1be687

All GitHub changesGitHub profileMarkdownJSON