Codeberg Status
codebergstatus@social.anoxinon.de
<p>Service status announcements from the <a href="https://codeberg.org" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">codeberg.org</span><span class="invisible"></span></a> system administrators.</p><p>Replies to this account are not monitored. For more exciting news, make sure to follow <span class="h-card" translate="no"><a href="https://social.anoxinon.de/@Codeberg" class="u-url mention">@<span>Codeberg</span></a></span>. :)</p>
Posts
-
View post
We had to temporarily restrict pulling images from the Codeberg container registry due to an abuse wave. This is related to authenticated traffic being slow earlier today. We're sorry for the inconvenience. No ETA for a fix, but we're working on it. ~dmi EDIT: resolved
-
View post
We have temporarily stopped serving pages that are served via the the old Pages Server (v2), to preserve the uptime of the unauthenticated servers.
-
View post
https://codeberg.org and legacy Codeberg Pages server has seen a long outage since yesterday, with blips of uptime. We are still investigating the problem, but it is unlikely to be resolved any time soon, as there is no clear cause to explain the disruption. We apologize for the inconvenience and for not providing an update on this disruption since it started happening.
-
View post
We're excited to see @forgejo@floss.social releasing v16. We already deployed it to our internal staging environment and have not found any regressions. We plan to deploy it later today in the evening at 21:00 CEST (19:00 UTC) which requires downtime of around 10 minutes. We'll keep you updated in this thread.
-
View post
Hello everyone, All the services we offer are down and unreachable. We are currently investigating the cause. For the time being, it appears that all three servers are without power.
-
View post
We are struggling to keep Codebreg.org available for unauthenticated users due to massive abuse of expensive endpoints. Our current priority is keeping Codeberg.org responsive for authenticated users.
-
View post
We&#39;re investigating a downtime of our primary instance.
-
View post
It has been in the works for months, but the recent increase of downtime has accelerated work. We&#39;ve moved from Caddy to HAProxy for codeberg.org traffic. Starting over with a new reverse proxy has enabled us to make choices that enable us to set up HAProxy to scale with our increasing traffic. For example, traffic is split (when possible, decided via heuristics) over several instances to load balance expensive traffic. We hope to share more details at a later time about this change.
-
View post
Codeberg.org appears to be very slow right now, we are trying to resolve this as we speak.
-
View post
Codeberg.org will be upgraded to Forgejo v15 in a few minutes. We expect downtime to be at most a few minutes, according to migration tests in the staging environment.
-
View post
Hi all, we&#39;re aware that Codeberg is down right now and are investigating.
-
View post
We are aware of reports of Codeberg being down and are investigating. Thank you for your patience.
-
View post
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&#39;re still investigating different mitigation strategies. As always, we are very grateful for your support and patience.
-
View post
We are entering a next phase. Codeberg Pages and Weblate and Hosted Woodpecker CI/CD will become unavailable. Forgejo will remain online.
-
View post
Maintenance is starting. Hosted Forgejo Actions logs will not be running. Performance degradation is possible