AI Weekly Malaysia

Back to items Summaries

Codeberg.org Not Reachable

ID
48150
Status
summarized
Published
18 Nov 2026, 6:02 PM
Fetched
19 Nov 2026, 9:23 AM
Provider
Hacker News
Category
dev-community
Original URL
https://social.anoxinon.de/@codebergstatus/117636437840688845
Source URL
https://hnrss.org/best

Summary

Score
7.0
Created
19 Nov 2026, 9:24 AM
Tags
Audience
developersvibe_coderssaas_founders

What happened

Codeberg's status account reports that codeberg.org is "entirely unreachable" after the domain, registered with NameSilo, disappeared from their account. They state they did not forget to renew, there are no suspicious logins in the login history, and the account's domain history shows no entry about the situation; they are waiting on NameSilo support and will try a workaround on codeberg.eu. The post drew 969 boosts and a Hacker News thread with 296 points and 296 comments.

Why it matters

The failure mode here defeats the usual checklist: no suspicious login, no renewal lapse, no domain-history record — so the standard "check your registrar login history" advice would have told Codeberg nothing. Concretely: if any of your repos, packages, or CI pulls from codeberg.org, add a second remote or mirror today rather than waiting for codeberg.eu; and for your own domains, verify registrar lock status and confirm which account email actually controls the domain, because a domain can vanish from an account while the audit trail stays empty.

Discussion angle

If your registrar silently dropped your primary domain with no login-history evidence, how long before you'd notice — and does your current setup (registry lock, secondary remote, uptime check on the domain itself) actually shorten that window?

Top