Previous incidents

The situation has been confirmed to be resolved.

The malware scan backlog has been fully processed. All packages have completed their initial scans and are now available as expected.

If you are experiencing issues with a specific package, please reach out to our support team.

Thank you for your patience while we completed this work.

A patched Chainguard Metabase image has been released and has propagated across all affected image tags.

What was addressed. This update remediates three upstream Metabase advisories: GHSA-vwf4-m7j8-wcjf (fixed directly in the image), and GHSA-8hmm-hrhg-ppqp and GHSA-r8h2-qpfx-mx59 (mitigated by disabling public dashboard sharing by default).

Public dashboard sharing is now off by default. If you need to re-enable it, set the environment variable MBENABLEPUBLIC_SHARING to true — but only ...

Build activity has returned to normal. Users should see new image and package updates as they are expected.

Cloudflare have implemented a fix and are monitoring their services.

The Chainguard services have recovered and the services are being monitored.

We've mitigated the issue and are continuing to monitor the affected services.

After investigation we have identified that the 403 errors were a false positive and the services were not degraded or effected during this time.

We have identified the root cause of the database connection exhaustion and the issues have been resolved.

We have fixed the cause of the missing Overviews and are starting to repopulate them.

Authentication is currently experiencing issues impacting new logins for the Console, API, OCI Registry, APK Registry, and all Libraries ecosystems. Existing sessions appear to be unaffected. We are currently investigating and will update the status page with more information soon.

We are monitoring recovery as services continue to stabilize. Customers may begin seeing improvements when authenticating to Chainguard services, including APK fetching, Libraries, and Console access. Our engineering team continues to closely monitor service health and investigate the underlying cause, and we will share another update as more information becomes available.

The issue has been resolved and we've confirmed that the Vulnerability and Advisory APIs are now accessible.