Post · bonfire.cafe

Post

@codebergstatus@social.anoxinon.de · yesterday

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

Codeberg.org

General availability (all services)

Subscribe to this issue if you want to receive notifications for all services at Codeberg (e.g. scheduled downtimes).

Codeberg Status

@codebergstatus@social.anoxinon.de replied · 4 hours ago

Maintenance is starting.

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

Codeberg Status

@codebergstatus@social.anoxinon.de replied · 3 hours ago

Codeberg will briefly go down for a moment, but will return momentarily from another server.

Due to technical complications, we noticed that a zero-downtime failover is unfortunately not possible.

Issue search results will be inaccurate.

Codeberg Status

@codebergstatus@social.anoxinon.de replied · 3 hours ago

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.

Codeberg Status

@codebergstatus@social.anoxinon.de replied · 2 hours ago

We are entering a next phase.

Codeberg Pages and Weblate and Hosted Woodpecker CI/CD will become unavailable.
Forgejo will remain online.

Codeberg Status

@codebergstatus@social.anoxinon.de replied · 1 hour ago

Unfortunately, unexpected hardware issues made the maintenance much longer than expected. On the first serviced host, we only wanted to add some memory, but upon booting it again, we realized that one of the SSDs died unexpectedly, causing a lot more debugging and improvisation efforts and delaying the overall maintenance efforts.

Codeberg Status

@codebergstatus@social.anoxinon.de replied · 1 hour ago

During the following steps, we did an elevated amount of human errors (likely attributed to increased stress) and had more downtime of Codeberg.org than initially expected.

This was due to a configuration error that made the "failover" instance still depend on a service hosted on the primary server, and so the failover also became unavailable when the primary went down for maintenance.

It took us a few minutes to realize and correct the mistake.

1 more replies (not shown)

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.2-alpha.7 no JS en

Automatic federation enabled