Oh, it's even more fun than that. If you sit there hitting F5, sooner or later you will get a proper page load. So some small subset of the servers is vending the correct data, and the rest not

speak for yourself, we are celebrating having completed all our PR's for a change :D

Or last week's "If you use merge queue, oopsie, we accidentally destroyed your trunk", which also failed silently.

why is this green for today, even though the offical page shows error.

Go ahead. We've been self-hosting Gitea with Drone/Woodpecker for years; either it or Forgejo will do fine if you're okay with their feature set. I sometimes wander into these GitHub threads to have a laugh; our Gitea instance has had several minutes of downtime combined over the last few years, all of them planned (to upgrade Gitea) and in the middle of the night.

I'm now self-hosting Git and CI with Forgejo, works like a charm. ;)

If you want a GitHub-like UI (with org/repo structure limitations) use either Forgejo or Gitea.

If you want a similar but different experience use GitLab.

If you want something more akin to the kernel experience (i.e. hosting, flexible repository structure, user auth via ssh keys, and a simple web UI) use gitolite with cgit, or alternatively gitweb.

I'm surprised GitLab isn't getting more attention. Yes, its not a carbon copy, but it is close. Apples and pears instead of oranges.

Seems like every week or so there's status issues. Often at what feels like the start of the week too.

That's damning. I wonder what it will look like over the next 13 months as more and more code is written by ai

seems like it couldve been covid instead? look closer at the months and also we need a y bar for "msft makes github do xyz"

Wtf. Why is that?

This is not to say that things haven't gotten worse over time, but...

I don't think that chart shows what it seems like it shows. There were plenty of pre-2018 outages that don't show up there: https://hn.algolia.com/?dateEnd=1545696000&dateRange=custom&...

An alternate interpretation of that chart is "After the microsoft acquisition, they got serious about actually tracking outages."

That said, anecdotally, it's felt much worse over the last 6 months. I'd guess it's a combination of MS-induced quality drops and AI-induced scale increases.

And when they introduced "Free" for everyone including teams, well I tried to warn everyone that centralizing everything to GitHub was not a good idea [0] 6 years ago.

[0] https://news.ycombinator.com/item?id=22867803

How is sourcehut different? It’s just yet another centralized service.

I like the experience of exploring new repositories so I switched everything to codeberg which is where most of the projects I'm interested with are

Another happy self hosted Gitea user here for ~3 years now.

Came from Gitlab which started pushing out basic users in 2022 with massive price hikes. I weighed Github as an option but was like "no I don't want to be dealing with this same problem in another 5 years" when some other rug pull or degradation happens with that service. So I'm feeling pretty validated for that decision these days.

The speed improvement was massive (super low latency), and was worth the switch on it's own, but we also saved 90% in immediate cost... probably more in secondary effects from the git host just not being a pain point. The only long or unplanned downtime we've had was 2 hours in that whole 3 years where the tiny Linode VPS host had a total hardware failure and got migrated, which is a pretty damn good number of 9s for a simple easy to host single server solution. We also gained more durable and fast offsite backups (zfs) that Gitlab could never offer, but that's more of a custom self hosted thing not specific to Gitea.

What's your general increase of cost and maintenance overhead? How many devs and repos do you have?

I guess a full postmortem like any other company would be too much as they have outages each week, sometimes multiple times a week.

All that reliability work must have paid off if it’s only happening weekly these days! lol

Syncing the code is the easy and trivial part and your CI job is only solving that. And in my opinion, it's not even that necessary for most projects.

The difficult part is all what's around the code:

* the tickets/PR (including the closed ones)

* the links referencing the project

* the CI setup

* for large projects, the committers permission setup

* if applicable, the push/commit/branch rules

All that will be deeply annoying to migrate on a per project basis, or might get lost.

But that's not even the worst on my opinion. Losing the go-to platform for finding software is (fediverse for software when?).