Codeberg.org Not Reachable
https://social.anoxinon.de/@codebergstatus/117636437840688845It was registered with namesilo and entirely disappeared from our account. We're waiting for their customer support to investigate the situation.
Update: We have received the confirmation that our domain was suspended and our case got forwarded to the abuse team. We're still waiting for a final decision.
I got attention by creating a post on social media, some higher level people reached out to me and resolved the issue.
Is there anything one can do to prevent the entire company from going dark?
- What if my registrar suspends my account? => Use different registrars for different domains. - What if the whole TLD has an outage (DENIC had that before)? => Fallback tld?
Should I really setup all SaaS apps with fallback-domain support that is registered by a different registrar on a different tld?
What happens to my company mails?
I wanna be a plumber!
> We do not give in, no matter the cost to us in legal fees, security arrangements or peace of mind.
https://1984.hosting/policy/ https://litigation.1984.hosting/
Is this something specific to the `.org` domains? I don't think you can "suspend" a `.com`?
With all these outages I am keeping a running list to discern wha the actual pattern is at the end. Incompetence, real attacks, bad change management, amateur operations, bad architecture and so on.
This is so crazy.
How are high-availability services supposed to block this failure mode? Become your own registrar?
Why do people use these penny ante companies for anything important?
Fight the system!
> The domain is slowly recovering. Many users are able to connect to our systems again. Some might need to wait for DNS propagation.
> Thank you so much for your patience. We're sorry for the serious disruption.
> We haven't yet received an official response from Namesilo's abuse department about the incident.
If you have a 3600-second-cacheable response, then what you are waiting for is for the remaining time to elapse - long after the now-current response has finished propagating to all the places that were willing to receive it.
I believe it's much easier to get your domain suspended in Germany vs in the US.
Anyway CodeBerg decided they won't accept any AI contributions so I opted for CodeFloe which is in the EU and seems to be hosted, registrared on Hetzner and with Bunny.net as CDN.
"The domain is slowly recovering. Many users are able to connect to our systems again. Some might need to wait for DNS propagation. We haven't yet received an official response from Namesilo's abuse department about the incident."
https://mastodon.social/@codebergstatus@social.anoxinon.de/1...
$ dig @v0n0.pir-ns.org. codeberg.org. NS
[...]
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29631
[...]
;; QUESTION SECTION:
;codeberg.org. IN NS
;; AUTHORITY SECTION:
org. 3600 IN SOA v0n0.pir-ns.org. hostmaster.donuts.email. 1794998113 7200 900 1209600 3600
$ whois codeberg.org
Domain Name: codeberg.org
Registry Domain ID: REDACTED
Registrar WHOIS Server: http://whois.namesilo.com
Registrar URL: http://www.namesilo.com
Updated Date: 2026-11-18T05:52:56Z
[...]
Domain Status: clientHold https://icann.org/epp#clientHold
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
> clientHold: This status code tells your domain's registry to not activate your domain in the DNS and as a consequence, it will not resolve. It is an uncommon status that is usually enacted during legal disputes, non-payment, or when your domain is subject to deletion. # /etc/hosts
217.197.84.140 codeberg.org
217.197.84.140 www.codeberg.org
217.197.84.140 blog.codeberg.org
217.197.84.140 docs.codeberg.orgThis is only going to get worse, but we can fix it. The system was designed for a world that doesn't exist anymore, but we can build one that is designed for the one that does.
While we're at it, maybe we can also fix the whole CA HTTPS nonsense?
Secure and human-readable: DNS
Secure and decentralised: .onion
Decentralised and human-readable: petnames or hosts files
this is crazy, guess i'll wait for codeberg to come back
Why update all the remotes if you can just add a `HostName` entry to your OpenSSH client config?
2a0a:4580:103f:c0de::1 codeberg.org
217.197.84.140 codeberg.org---
r/Codeberg is banned
This community was banned for violating Rule 2.
You agree that use of this site constitutes acceptance of Reddit’s User Agreement and acknowledge our Privacy Policy.
---
https://web.archive.org/web/20250214215322/https://old.reddi...
I'd guess it was taken over by spambots at some point.
> Abide by community rules. Participate authentically in communities where you have a personal interest, and do not spam or engage in disruptive behaviors (including content manipulation) that interfere with Reddit communities.
I was also surprised that Codeberg would use it instead of an EU-based registrar.
https://www.iana.org/domains/root/files
https://www.iana.org/domains/root/servers
I know UN's ITU might not be the best org for this but this has to come out of USA.
The problem is that all non-country TLDs are USA-controlled, and that the USA prints new ones for profit. Yes this includes ones like .tokyo and .berlin
(https://letsencrypt.org/2026/01/15/6day-and-ip-general-avail...)
I wonder how many projects will move back after this?
Also codeberg is up again.
did the emulators move to codeberg?
Codeberg.org was my backup/alt git forge provider, in migration from and mitigation of GitHub/MS clownery
You can use SSH directly, but using something like gitolite makes managing the git repos easier.
My main gripe with this setup (gitolite + cgit) is the lack of repository labels/tags. You can define a namespaced/scoped category, but that's not as flexible as a hierarchical tag system.
The syntax for SSH access is user@hostname:/path/to/git/repo which you might recognise from github. You can use this syntax with any machine, not just GitHub. It invokes a real ssh subprocess to do the connection, so all of your .ssh config and private keys apply. It runs an internal git command on the server to do the data transfer (git receive-pack or git upload-pack).
Whatever you do, don't go back to big tech. They're causing this.