April 27, 2026
PRs: 0, Drama: 100
GitHub is having issues now
Work stalls, users fume, and the memes are savage
TLDR: GitHub stumbled: pull requests, issues, and search broke, then began recovering after the team killed a heavy load source. Users blasted the outage—some blamed Microsoft and pushed self-hosting, others cracked jokes—and even noted that Codeberg, a popular alternative, had hiccups too, making this a tough day for devs everywhere.
GitHub hit the brakes today and devs let the internet know. Searches sputtered, pages for issues and pull requests showed zero results, and automation jobs limped. The official status page blamed extra load hammering their search system; they disabled the source and said recovery signs appeared at 19:50 UTC. But while GitHub flipped switches, the comments lit up. SenHeng reported pages “loading with 0 items” and a mocking “failure to fetch” pop-up. m_a_t_t_8_6 called it “pretty much unusable” and wondered why it wasn’t bigger news. The spiciest take came from rvz, who declared the Microsoft-owned platform “run into the ground,” blamed chatbots, and yelled “time to self host.” That set off a familiar battle: ditch GitHub now vs. “every site breaks sometimes.”
Then came the plot twist: even escape hatches were jammed. vlugorilla pointed out that GitHub’s indie alternative Codeberg was also wobbling (status), turning migration talk into a meme. The crowd’s comedic relief? ttouch’s deadpan: “we’ll post only when GitHub is 100% up,” guaranteeing instant front-page fame. Cue the mood board: PRs at zero, patience at zero, hot takes at 100. Whether you’re doom-posting or doom-scrolling, everyone agreed on one thing—today was a bad day to ship code.
Key Points
- •GitHub reported an incident causing search failures and degraded performance across multiple components on Apr 27, 2026.
- •Issues, Packages, and Actions experienced degraded performance; Pull Requests faced a major outage and degraded availability.
- •Connectivity issues to ElasticSearch led to intermittent downstream impact while root cause analysis was ongoing.
- •At 19:50 UTC, GitHub disabled the source of additional load stressing ElasticSearch clusters and observed recovery.
- •Operational components during the incident included Git Operations, Webhooks, and API Requests; regional status pages and subscription options were available.