Codeberg Status

Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.

As always, we are very grateful for your support and patience.

We're currently suffering from performance degradation due to heavy traffic. We are still investigating.

We're entering Ceph filesystem maintenance. Please expect performance degradation or (in worst case) some downtime.

We are currently struggling with database performance and investigating.

Tonight, we shipped a new server to the datacenter and started restoring Galera cluster on the node (since the hardware breakage last week, we were running on 2/3 nodes only).

We are not yet sure what is causing the sudden performance drop.

Codeberg.org is up again. Issue search results will remain inaccurate. Hosted Woodpecker CI/CD and Forgejo Actions job will be queued up and processed later.

Maintenance is starting. Hosted Forgejo Actions logs will not be running. Performance degradation is possible

Hardware maintenance on 2026-01-28 (tomorrow), starting 19.00 CET (18.00 UTC)

Expected duration: 1 - 2 hours overall operation. Downtime per service will be smaller.
Expected impact:

* Forgejo: Brief moments of unavailability or performance issues. Issue search results will be temporarily inaccurate.
* Pages, Hosted CI/CD (Forgejo Actions and Woodpecker), Weblate, other services: Unavailable for about 30 minutes during the maintenance window.

Details: https://codeberg.org/Codeberg/changelog/issues/1#issuecomment-10214869

Hey! We are introducing a centralized changelog for various Codeberg services: News, scheduled maintenance and more, delivered into your Codeberg notifications.

Check it out at https://codeberg.org/Codeberg/changelog and make sure to subscribe the general notifications.

This Fediverse account will continue to post about scheduled or unexpected maintenance.