The Codeberg DNS outage lasted about five hours on 18 November after its registry record showed a registrar hold. The timeline points to one registrar status as the immediate reason codeberg.org stopped resolving, while the available records do not explain why the hold was applied.
The Codeberg DNS outage affected the domain name itself, rather than showing a problem with Codeberg’s servers. That distinction matters for services hosted under one address: when a domain does not resolve, users and automated tools cannot reach the service through that hostname.
One Registrar Status Removed the Name From DNS
The registry record changed at 05:52:56Z on 18 November and showed clientHold alongside client transfer prohibited. Codeberg posted at 08:17:31Z that the domain was gone from its account. The organization said it was “completely gone from our account,” not expired or transferred, and that it was then in clientHold.

At 08:42:29Z, Codeberg responded to a question about registrar abuse action. It said it had received no prior warning according to the registrar’s processes and described a technical issue as the most likely explanation. That was Codeberg’s assessment; the records supplied for this article do not establish the cause.
The registry’s last-changed stamp moved again at 11:02:51Z. At that point, clientHold was no longer listed, while client transfer prohibited remained. The interval between the two recorded changes was five hours and ten minutes.
What Resolvers Showed During the Codeberg DNS Outage
Two public DNS resolver captures returned NXDOMAIN for codeberg.org, meaning they had no answer for the name. In the later capture, after the hold was removed, the domain resolved again to 217.197.84.140. The samples match the registry timeline: the name failed while clientHold appeared and answered again after it disappeared.
ICANN describes this status as instructing a domain’s registry not to activate the domain in DNS, with the result that it will not resolve. That mechanism explains why the effects appeared across services using the hostname, without evidence in these records that Codeberg’s servers had changed.
Records Do Not Show a Transfer or Expiration
The same records do not show a transfer event. Client transfer prohibited remained in place throughout the captured interval, and the listed expiration date stayed 2028-07-05. The registration date remained 2018-07-05. Those details do not support describing the event as an expired or transferred domain.
The registrar was listed as NameSilo. The source says NameSilo was not asked for comment and made no statement in the material reviewed. It therefore leaves the reason for the hold unresolved. Codeberg’s statement that a technical issue was most likely remains an attributed assessment, not a confirmed explanation.
Domain Availability Reaches Beyond the Server
During the Codeberg DNS outage, people and tools using codeberg.org would have encountered a DNS failure. The source notes that pushes and CI fetches relying on the hostname failed, documentation links broke, and the incident did not require a change to Codeberg’s own servers. These are consequences of the hostname becoming unavailable, not evidence of a forge server outage.
For operators, the Codeberg DNS outage illustrates why domain registration and DNS belong in service availability planning. A separate server health check cannot establish that a domain remains active in the registry. Organizations tracking domain changes can also review related domain holder requirements, while infrastructure teams may find context in our coverage of WordPress security updates and PHP server fixes.
The Codeberg DNS outage ended with the domain resolving again after clientHold was removed. The source report documents the timeline. No source provided here identifies why NameSilo’s registry record acquired the hold, so the cause remains open.









