Codeberg Is Down
Postedabout 1 month agoActive27 days ago
status.codeberg.orgTech Discussionstory
informativeneutral
Debate
0/100
CodebergOutageStatus Update
Key topics
Codeberg
Outage
Status Update
Discussion Activity
Very active discussionFirst comment
N/A
Peak period
45
0-12h
Avg / period
16.3
Key moments
- 01Story posted
Dec 3, 2025 at 3:26 AM EST
about 1 month ago
Step 01 - 02First comment
Dec 3, 2025 at 3:26 AM EST
0s after posting
Step 02 - 03Peak activity
45 comments in 0-12h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 7, 2025 at 2:26 PM EST
27 days ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 46131693Type: storyLast synced: 12/3/2025, 8:38:08 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
:D
Edit: Funny enough GitLab is down 9% in pre-market and near all-time lows.
Currently Zig is the second most "stared" project on Codeberg (1443 stars). The first one is forgejo/forgejo (3154 stars) which is powering Codeberg, and the third one is dnkl/foot terminal emulator (1434). (see https://codeberg.org/explore/repos?q=&only_show_relevant=tru...)
It's always interesting to see big and significant projects moving away from major commercial platforms. Could it be a sign of something new on the horizon?
"We are currently fighting against a DDoS attack against our service and our status page. We are analyzing network traffic with the help of our ISP at the moment and let you know once we have updates to share."
(Yes, I'm aware DDoS attacks are nothing new)
> At around 06:00 UTC on January 10th [2024], a layer 3 distributed denial-of-service (DDoS) attack began to target SourceHut’s PHL infrastructure. We routinely deal with and mitigate application layer (layer 7) DDoS attacks, however, a layer 3 attack takes place at a lower level and is not within our ability to mitigate without the assistance of our network provider.
Congrats to Codeberg for having a real status page and not a made up one like AWS and many others.
A CI that's completely broken and not building anything cannot produce incorrect results.
If it's producing no result at all, you know it's broken, not simply incorrect.
Uptime Kuma is really nice: https://github.com/louislam/uptime-kuma
Supports all sorts of alerts and can even tell you if it ever looks like your TLS certs will soon expire (if any automation is broken, or you use commercial certs with manual rotation).
Thanks Gary, I'll use that next time.
I don't care for Zig at all, and had never heard of Codeberg, they are now solidified in my mind aha
I haven't followed closely; but the few times I did, it seemed that he had reasonably nuanced opinions translating into upholdable values, rather than overzealous cancel-fever, whether I agreed with his opinions or not. To me this is not reason enough to not use his product, and I happen to like his product (much more than the alternatives anyway).
Also, it would be remiss of me not to appreciate the irony that you're effectively suggesting "cancelling" his business over his opinions which you consider of a "cancelly" nature ...
> All users who host projects on SourceHut are expected to pay according to their means. choose the subscription plan most appropriate to your means — there is no difference between the subscriptions besides price.
Interesting approach and asking for some money upfront to cover the actual hosting costs and other stuff feels pretty good - rather than having to worry about shady monetization and about whether your data is the product.
There's plenty of screenshots on the main page of the UI: https://sourcehut.org/
Some people will enjoy that kind of minimalism, definitely not everyone's cup of tea - feels really fast and reminds me a bit of Kanboard, though.
No idea about owner, not my place to comment.
Both Codeberg and sourcehut are good options when escaping the walled gardens of Big Tech :)
That doesn’t make it impossible to buy it, but all profits from a sale must flow into recognized public good efforts. The incentive to sell for huge sums is just much lower for all people involved.
I always like to move as much as possible into the repo itself, 'issues' etc in a TODO, build scripts, or however you want to achieve that, so you can at least carry on uninterrupted when the host is down.