# Codeberg.org vanished

**URL:** <https://ziggit.dev/t/codeberg-org-vanished/18502>\
**Category:** Media\
**Created:** [November 18, 2026, 8:54am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502 "2026-11-18T08:54:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![FObersteiner](https://ziggit.dev/user_avatar/ziggit.dev/fobersteiner/32/1177_2.png) [@FObersteiner](https://ziggit.dev/u/FObersteiner)\
**Post date:** [November 18, 2026, 8:54am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/1 "2026-11-18T08:54:06Z")

</div>

Seems to be a domain issue: [https://social.anoxinon.de/@Codeberg/117636454915265360](https://social.anoxinon.de/@Codeberg/117636454915265360)

---

<div class="post-metadata">

**Author:** ![hachanuy](https://ziggit.dev/user_avatar/ziggit.dev/hachanuy/32/3619_2.png) [@hachanuy](https://ziggit.dev/u/hachanuy)\
**Post date:** [November 18, 2026, 9:06am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/2 "2026-11-18T09:06:40Z")

</div>

So it’s not always the DNS.

---

<div class="post-metadata">

**Author:** ![Wyvern](https://ziggit.dev/user_avatar/ziggit.dev/wyvern/32/6698_2.png) [@Wyvern](https://ziggit.dev/u/Wyvern)\
**Post date:** [November 18, 2026, 10:30am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/3 "2026-11-18T10:30:15Z")

</div>

> **[codeberg.org Status & Uptime | TheSiteStatus](https://www.thesitestatus.com/codeberg.org)**
>
> Is codeberg.org down? codeberg.org reliability grade is C+ with 100% uptime over 12 months, 32 confirmed incidents, and live status. Get global outage report.

Score: C+ `73/100`

Do you think [codeberg.org](http://codeberg.org) is still a reliable code repository for zig?

## Downtime incident history

**32** in 12 mo MTTR **38m** Total **19h 47m**

| Started | Duration | Severity | Detected by | HTTP codes |
| --- | --- | --- | --- | --- |
| Nov 18, 2026 · 06:30 UTC | Ongoing | Full outage | probe | — |
| Nov 17, 2026 · 17:00 UTC | 29m | Full outage | probe | — |
| Nov 17, 2026 · 11:00 UTC | 29m | Full outage | probe | — |
| Nov 15, 2026 · 17:00 UTC | 29m | Full outage | probe | — |
| Nov 15, 2026 · 11:00 UTC | 29m | Full outage | probe | — |
| Nov 14, 2026 · 17:00 UTC | 5m | Full outage | probe | — |
| Nov 12, 2026 · 11:00 UTC | 29m | Full outage | probe | — |
| Nov 11, 2026 · 17:00 UTC | 29m | Full outage | probe | — |
| Nov 11, 2026 · 11:00 UTC | 29m | Full outage | probe | — |
| Nov 7, 2026 · 11:00 UTC | 29m | Full outage | probe | — |
| Oct 31, 2026 · 16:00 UTC | 29m | Full outage | probe | — |
| Sep 23, 2026 · 18:00 UTC | 59m | Full outage | probe | — |

---

<div class="post-metadata">

**Author:** ![nonzeroq](https://ziggit.dev/user_avatar/ziggit.dev/nonzeroq/32/9106_2.png) [@nonzeroq](https://ziggit.dev/u/nonzeroq)\
**Post date:** [November 18, 2026, 10:32am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/4 "2026-11-18T10:32:39Z")

</div>

As per [Codeberg Service Status](https://status.codeberg.eu/status/codeberg), their domain name was suspended by their registraar (for… ToS violation?). In any case, codeberg is still accessible through their IP addresses.

---

<div class="post-metadata">

**Author:** ![devengel](https://ziggit.dev/letter_avatar_proxy/v4/letter/d/e36b37/32.png) [@devengel](https://ziggit.dev/u/devengel)\
**Post date:** [November 18, 2026, 10:35am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/5 "2026-11-18T10:35:26Z")

</div>

A ToS Violation? Interesting, i wonder which part they are referring to in the TOS.

---

<div class="post-metadata">

**Author:** ![lukeflo](https://ziggit.dev/user_avatar/ziggit.dev/lukeflo/32/7514_2.png) [@lukeflo](https://ziggit.dev/u/lukeflo)\
**Post date:** [November 18, 2026, 10:39am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/6 "2026-11-18T10:39:17Z")

</div>

> [@Wyvern](#):
>
> Do you think [codeberg.org](http://codeberg.org) is still a reliable code repository for zig?

Moving to Codeberg was the right move in my eyes and one of the main reasons for me personally to switch to Zig. The core team surely was aware of the infrastructure vulnerabilities, but decided its worth leaving GitHub.

That said, whats the alternative? Moving back to a BitTech owned, AI-flooeded platform? Which to my understanding was a main reason to leave those.

Maybe the “solution” could be for users of Zig and FOSS to support a platform like Codeberg more, be it with donations or contributions, to make it more resilient and independent. But that’ll take some time.

---

<div class="post-metadata">

**Author:** ![zeeqeeng](https://ziggit.dev/letter_avatar_proxy/v4/letter/z/8baadc/32.png) [@zeeqeeng](https://ziggit.dev/u/zeeqeeng)\
**Post date:** [November 18, 2026, 11:03am UTC](https://ziggit.dev/t/codeberg-org-vanished/18502/7 "2026-11-18T11:03:42Z")

</div>

The solution will not and should not be a foregejo instance. I personally hope it could be a Zig solution if possible. But starting a new Git-host platform would not be a technical issue but social and market one.
