Incidents reported on status page for Chainguard, Inc. https://status.chainguard.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/0cf9c5bd2084860bdcb42ff9bc19e06f.png https://status.chainguard.dev/ en https://status.chainguard.dev/ Tue, 24 Mar 2026 21:06:06 +0000 https://status.chainguard.dev/#08dc620107b247edab00ea36d9dd35b9e0861ed281dbdaa50b0eac9b5c93bd53 APK Registry recovered https://status.chainguard.dev/ Tue, 24 Mar 2026 21:03:28 +0000 https://status.chainguard.dev/#b2e6c2670e64842d280068401cd62cc9ca7fe468a937bc5f64f3e77eae058c81 OCI Registry recovered https://status.chainguard.dev/ Tue, 24 Mar 2026 20:43:19 +0000 https://status.chainguard.dev/#b2e6c2670e64842d280068401cd62cc9ca7fe468a937bc5f64f3e77eae058c81 OCI Registry went down https://status.chainguard.dev/ Tue, 24 Mar 2026 20:41:06 +0000 https://status.chainguard.dev/#08dc620107b247edab00ea36d9dd35b9e0861ed281dbdaa50b0eac9b5c93bd53 APK Registry went down https://status.chainguard.dev/ Tue, 24 Mar 2026 19:35:56 +0000 https://status.chainguard.dev/#486b8b8e1b2af9820b45cee074a18b9bef59f1a6787491bce2e9f5a47664e7a9 APK Registry recovered https://status.chainguard.dev/ Tue, 24 Mar 2026 19:33:03 +0000 https://status.chainguard.dev/#486b8b8e1b2af9820b45cee074a18b9bef59f1a6787491bce2e9f5a47664e7a9 APK Registry went down https://status.chainguard.dev/ Tue, 24 Mar 2026 16:28:18 +0000 https://status.chainguard.dev/#4d25180fd4f822a8623b73b920217c30b255692059d6f35f771c514a227d3e2a Java Libraries recovered https://status.chainguard.dev/ Tue, 24 Mar 2026 16:24:15 +0000 https://status.chainguard.dev/#4d25180fd4f822a8623b73b920217c30b255692059d6f35f771c514a227d3e2a Java Libraries went down https://status.chainguard.dev/incident/841399 Thu, 05 Mar 2026 15:18:00 -0000 https://status.chainguard.dev/incident/841399#e97b2ae83578f672572029e71e8a87dd43fa4c9196c579eee2af40de537fa4e5 Issues are now resolved. https://status.chainguard.dev/ Thu, 05 Mar 2026 15:13:53 +0000 https://status.chainguard.dev/#e4e84f3a6ed8384a8c570203d961c108de76adb421306bf5659bbffb6d3833c2 API recovered https://status.chainguard.dev/incident/841399 Thu, 05 Mar 2026 14:31:00 -0000 https://status.chainguard.dev/incident/841399#9c45acbfae5717ebba482660eb7767bab668575c84ca40c7ebe4e0a5e7bc1713 We are seeing elevated errors rates for chainguard.platform.registry.Vulnerabilities APIs. Other API services are unaffected. https://status.chainguard.dev/ Thu, 05 Mar 2026 13:59:46 +0000 https://status.chainguard.dev/#e4e84f3a6ed8384a8c570203d961c108de76adb421306bf5659bbffb6d3833c2 API went down https://status.chainguard.dev/incident/824447 Thu, 12 Feb 2026 23:41:00 -0000 https://status.chainguard.dev/incident/824447#48c9a368963eeeed33672254832095d118ba6100eac20112cccc70b7a7e6db36 Between February 10 and 11, we experienced elevated error rates across internal services, which impacted authentication and registry availability. The issue has been resolved, and we are continuing to investigate the root cause. https://status.chainguard.dev/incident/818778 Wed, 11 Feb 2026 16:27:00 -0000 https://status.chainguard.dev/incident/818778#766d694456165154c75378f9f79f23e5013f24f28ff061237bd09aa113d17756 A glibc change has been deployed that will prevent duplicate glibc sbom detection for all future builds. Existing binaries will need to be rebuilt to drop such detection. As this is deployed, the incident is declared closed. If additional rebuilds are desired, please open a support ticket. https://status.chainguard.dev/incident/818778 Wed, 04 Feb 2026 23:58:00 -0000 https://status.chainguard.dev/incident/818778#4df6ecc1665b61fbb0c105029d72f1d57cd47433011a242839284b14fb085e21 We are investigating multiple duplicate SBOM detections for the glibc package in unrelated binaries which lead to false positive detections for recent glibc CVEs such as CVE-2025-15281 https://status.chainguard.dev/incident/817827 Tue, 03 Feb 2026 19:07:00 -0000 https://status.chainguard.dev/incident/817827#090dd4658172d223460933a0cf48667ad4e15348b5ca47c9b0d7f6e3279ac187 We identified a typographical issue in our feeds that caused scanners to report false positives for CVE-2025-59466 in images containing NodeJS 22. An incorrectly formatted “fixed” version was published, leading scanners to conclude that the CVE had not been addressed in the latest release, 22.22.0-r0. The issue has now been corrected in our feeds. Downstream scanners will need to ingest the updated data and refresh their databases. Since most scanners rebuild their databases daily, we expect the corrected information to be reflected in many cases by the next overnight update. In addition to correcting the data, we are implementing safeguards to prevent incorrectly formatted values from being accepted in the future. A full root cause analysis will be shared with customers in due course. https://status.chainguard.dev/incident/714227 Thu, 04 Sep 2025 02:30:00 -0000 https://status.chainguard.dev/incident/714227#5f3d43a9a8bfdde8291398ae3a672e6c7787735824b27c7c54a05080b3264678 Maintenance completed https://status.chainguard.dev/incident/714227 Thu, 04 Sep 2025 01:30:00 -0000 https://status.chainguard.dev/incident/714227#cde403b465a97bf10529a4bfa3a032926f29dfca0e7d1676f0ddfa380b70c260 While we perform the database maintenance, we expect a short period of disruption. Thank you for your understanding. https://status.chainguard.dev/incident/712989 Tue, 26 Aug 2025 19:40:00 -0000 https://status.chainguard.dev/incident/712989#4267fd5d3ed0aebe1ad8484984da31c9038b54bd3059702f205bffbfe9a35723 We saw a brief outage period as our database was going through a maintenance update. All services have since recovered. https://status.chainguard.dev/incident/701517 Wed, 06 Aug 2025 16:50:00 -0000 https://status.chainguard.dev/incident/701517#c24f7e3bbfcb0ce4fc33b9cc3e3dff53671ac3e7142cd363b95da9200dc5792a We've released a change that we anticipate will solve the immediate issue. We're monitoring closely, but metrics indicate the fix was successful. https://status.chainguard.dev/incident/701517 Wed, 06 Aug 2025 15:48:00 -0000 https://status.chainguard.dev/incident/701517#d7563200e5a613b900303d98e383289d058585ca47bec0fe7b6c80d4bb40778d We're experiencing elevated error rates for APK package serving from apk.cgr.dev and virtualapk.cgr.dev. Customers may be experiencing intermittent errors pulling packages and indexes. We're monitoring and releasing a fix soon. We will provide an update in an hour. https://status.chainguard.dev/incident/602053 Thu, 12 Jun 2025 19:56:00 -0000 https://status.chainguard.dev/incident/602053#07e32b17f598ccf36ada3da930e3c5d7e25702b374ccfe390a99cc5d778b4d11 Cloudlfare and GCP have completed their monitoring and we can confirm that all services have returned to normal. This incident is now resolved. Thank you for your patience throughout the process. If you have any remaining questions or concerns, feel free to reach out via support.chainguard.dev.