Comment by gen220
4 hours ago
Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.
4 hours ago
Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.
It's not physically possible to run post-mortems for issues at those rates.
They should install OpenClaw for that as well.
Perhaps best to simply declare indefinite-mortem
AI: The cause of, and solution to, all of your tech debt.
The UI of that page is so nice, should build a github competitor.
The user profile / contributions and PR UX is pretty much the entire "hub" product since git is a fully separate offline app.
> The UI of that page is so nice
Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with.
I think most of us who've tried using LLMs for web-design can recognize that style and design at this point, regardless of model actually used.
Oh wow, I'm in the position to be able to give a peek behind the curtain of something (validly!!) critiqued as AI slop! Exciting.
I originally made the core data functionality of this site for myself because I was curious what the uptime stats for each service were (I build something that heavily depends on GitHub), and to viz the distribution/severity of those incidents, again per-service, over time.
It involved a lot of back-and-forth, and is not a one-shotter; maybe closer to 40-50 shots over maybe ~10 hours of human time. A couple memorable things that made it complicated, irrespective of the UI: sneaky bugs around double-counting time for overlapping incidents, no GitHub API for incidents so you need to puppeteer-scrape the backlog of incidents to get historical data. Although, you all are right to call out that the CSS was three shots, though, and it shows :) I thought it looked so cool in ~January 2026 and now it gives me the ick, too!
For people who are curious about how much direction went into the information architecture/presentation, it was fairly substantial. I wanted a contribution graph style viz and it took many turns to get it working the way I wanted. The swimlane viz for selected-day-incident visualization was also me, because I love swimlane graphs.
I ended up sharing it with some folks and they wanted to reference it, so I put it on a website. So it's jokey for sure, but I take my jokes seriously! I'm grateful that people have feedback on how it can better functionally and visually :)
Compared to near unusable pages that large organizations produce, yes this page is highly effective at conveying information. Who cares how it was produced?
3 replies →
The Bootstrap of 2020s.
1 reply →
What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.
6 replies →
I’m actively working on an alternative Frontend for Forgejo at the moment, completely self hostable, free, and open source.
Moving everything from GitHub to Forgejo and Tangled for now. These outages haven’t effected me for the past month because of this.
Can you elaborate on how your Forgejo frontend will be different than the default one? I'm asking because I've only ever used GitHub, GitLab and Forgejo for longer periods and Forgejo was the fastest and easiest to use for me.
The UI is in the default claude code style
>"The UI of that page is so nice"
Most part screen is taken by picture. Contrast ratio is really low. Hard to read Should they remove that useless banner, current status which is the most interesting part coud've been made visible right away.
I would call this whole thing highly un-ergonomic
Lol it's pretty bad UI
May has been filled with critical issues. It seems it's getting worse over time.
Commits are up 14x year-over-year
https://x.com/kdaigle/status/2040164759836778878
Not a valid excuse without knowing what their historical growth rate has been. And how much of the instability is load related.
Yea but thats not really an excuse, is it? They offer a service, (some) people pay for that service and should therefore expect it to work. If GitHub cannot keep up with the growth then they could disable new account registrations or start reducing free tiers so people either use the free tier more mindfully or need to pay for usage-base products like Actions which would GitHub allow to scale.
3 replies →
Is the “streak” days of continuous uptime, or of days with at least one downtime incident? I think it’s the latter :]
It's a streak for continuous uptime, and yeah it is fairly depressing to imagine overseeing that :/
It looks like it is the number of consecutive days with no incident. If you look at 31 Dec 2025, that corresponds to an 8-day period with no incidents.
I guess that also means this year GitHub has not yet made it a single week without an outage of some kind.
Name one thing Microsoft didn't run into the ground post-acquisition
hey now, LinkedIn was terrible before Microsoft.
Java or Bedrock edition, and have you tried logging into your EntraID Microsoft Teams for Xbox account lately? Make sure to check the box to keep you logged in!
2 replies →
Not as bad as it is now. All I see are suggested posts from people I never connected with and those are full of instagramesque self-promoting banal vibes.
TBH, even LinkedIn seemed to provide me with posts advertising events that happened two weeks ago a bit less pre-acquisition.
I think Minecraft is still in good shape
I wouldn't know, somehow this game I bought maybe 15 years ago is no longer playable for me, my account was supposed to be migrated from Mojang to Microsoft or similar, but then that never happened or something, and trying to login now asks me to contact Microsoft support, which I've tried 3-4 times, never had anyone respond to me so who knows how the game is today? I stopped trying at this point...
Personally, once a game I own is janked from my hands because of organizational decisions, that's the time I'll stop consider the game "in good shape", but I'm sure the people who had to buy the same game a second time still enjoy it.
1 reply →
They deleted my account from 2010 because I didn't convert it to a Microsoft one. They baked an incredibly aggressive chat filter into multiplayer, even if you're not playing on official servers. They've added microtransactions for things that we previously free (skins, resource packs). They force you into their shitty, bloated, user-hostile launcher with adverts.
It's been nonstop content-slop since the acquisition. New mobs, new blocks, new items, new blocks, new items, new mobs, new mobs, new biomes. Some of them are good but the totality of adding a bunch of stuff has been to destroy the simplicity that was one of the draws of the original game. Now it's an exploration and niche-mechanics-exploitation game more than a virtual legos game. You don't go mining any more, you find trading loops with villagers.
This was happening to some degree pre-acquisition, but since the acquisition it's been this non-stop.
Some of it's good. The Nether and the oceans were really boring before their respective updates.
They should have called Minecraft "done" around the acquisition time and started on Minecraft 2.
[dead]
GH was acquired by microsoft some eight years ago. It has been working quite well until recently.
People may have had complaints about functionality, features, commercial issues, but the thing used to at least have a decent uptime until recently.
Has nothing to do with Microsoft acquisition... AI usage has increased demand and load. More PRs, more Action runners, more of everything firing. GitHub just wasn't ready for the scale and are now having issues catching up with it as it continues to increase exponentially.
6 replies →
> It has been working quite well until recently.
I'm not sure how reliable the data is, but average uptime seems to have dipped measurably starting within a year of the aquisition, according to https://damrnelson.github.io/github-historical-uptime/
1 reply →
It also used to be run as an independent company with access to MS's resources.
Now it's a unit in their AI hype machine.
MSFT was pretty arms length for the first 5-6 years. I was honestly kind of impressed and it made my opinion of MSFT better. But then AI made it too attractive of a target and MSFT couldn't help but make it a place the former CEO wanted to leave (and it has been running headless for about a year now).
It's quite disappointing objectively, but I expected worse from MSFT.
They are already cooked as this has been happening ever since the Microsoft acquisition and it was run to the ground before 2023.
At this point you would get better uptime by just self-hosting your own GitLab, Forgejo or Codeberg instance instead of dealing with Github's unreliablity.
There is no defending them with their clear neglet and carelessness of the platform.
If all you need is a repository, you don't even need any of these. You need SSH access to a server, and optionally, one of several web front-ends. Git comes with a CGI script that handles public anonymous checkouts via HTTP(S) although since nginx doesn't support CGI, integrating those is a little bit tricky (you need a FastCGI wrapper daemon).
I moved most of my projects off GitHub to Forgejo and will be using Tangled too for public repositories. I don’t think people realize that if you self host Forgejo, you get 99% of the functionality of GitHub with zero of the limitations. Especially if you have the hardware to spare for CI runners. And if self hosting isn’t your thing you can always just use Codeberg and Tangled directly.
I’m working on an open source Forgejo browser called Joui. It’s coming along nicely, and is so much snappier than GitHub in every single way.