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/incident/1012299 Fri, 14 Aug 2026 22:58:00 -0000 https://status.chainguard.dev/incident/1012299#0bb8d944f9ddfc962c1acbf5a1b52a85921484ca789179947d4695ebd9119be9 The situation has been confirmed to be resolved. https://status.chainguard.dev/incident/1012299 Fri, 14 Aug 2026 20:21:00 -0000 https://status.chainguard.dev/incident/1012299#d1e155d847760db863e92b0be0a9871d545ac33f3ae2ebd2eb391b5770e5a5b2 Access to the Zendesk support portal has been restored. We are continuing to monitor the situation. https://status.chainguard.dev/incident/1012299 Fri, 14 Aug 2026 16:43:00 -0000 https://status.chainguard.dev/incident/1012299#3e4a109f3575436507ce8de383886c5865ca21e3c47dc3161747cf97e607b1a1 A temporary fix has been put in place while we work on a permanent solution. Access to the Zendesk support portal is now working as expected. https://status.chainguard.dev/incident/1012299 Fri, 14 Aug 2026 16:15:00 -0000 https://status.chainguard.dev/incident/1012299#0f72f30c55c266822d9d2c4ea84b5b753369d5b502eb799cb08372a46a4e8e43 Engineering is continuing to investigate the issue. https://status.chainguard.dev/incident/1012299 Fri, 14 Aug 2026 15:00:00 -0000 https://status.chainguard.dev/incident/1012299#03c83ee6f95f9a715d9e790f9b953cb1bfdab1f0a5ec5ae7642928ff572a0050 Engineering is continuing to investigate the issue. https://status.chainguard.dev/incident/1012299 Fri, 14 Aug 2026 14:00:00 -0000 https://status.chainguard.dev/incident/1012299#388f45dae2f33a1e8c1a4f41134534f59d28e51425de93b5baacdaf0e5edcaf6 We are investigating reports of users receiving an error page when accessing our Zendesk support portal. We are working to identify the root cause and a resolution, and will post an update as soon as we have more information. https://status.chainguard.dev/incident/1007862 Tue, 11 Aug 2026 23:46:00 -0000 https://status.chainguard.dev/incident/1007862#f9707094bb69227522698f38c106a5fc0ee9f38e53b203e93a2d9baa4f5afaa7 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. https://status.chainguard.dev/incident/1007862 Tue, 11 Aug 2026 14:17:00 -0000 https://status.chainguard.dev/incident/1007862#105f100e89397f6c4a7232918b611b5b1c0ad7319fa6095280a9357d1f879dcd The malware scan backlog continues to drain and is in its final stage. The vast majority of packages have completed scanning and are available as expected. A small number of remaining packages are being re-processed and we expect them to clear shortly. We will continue to provide updates as the work progresses. https://status.chainguard.dev/incident/1007862 Tue, 11 Aug 2026 08:59:00 -0000 https://status.chainguard.dev/incident/1007862#bb4a01801d7bf8d93cfe1fdc20be2a294e0064685b60d61624800c7b661f1c88 Malware scan is ongoing currently. Until a package's scan completes, requests for it may fail or return MALWARESCANPENDING. We expect this process to take around few more hours. We'll keep this page updated. https://status.chainguard.dev/incident/1007862 Tue, 11 Aug 2026 06:03:00 -0000 https://status.chainguard.dev/incident/1007862#86c2225d9a7aae397478afa7b954c1eb8763dd247f8d76f1d31efa317143583c 95% of malware scan has completed. Until a package's scan completes, requests for it may fail or return MALWARE_SCAN_PENDING. We expect this process to take approximately 3 more hours. https://status.chainguard.dev/incident/1007862 Tue, 11 Aug 2026 02:52:00 -0000 https://status.chainguard.dev/incident/1007862#85edddb69fd88589cb181ab37dba22e52ebabee636c45cebaa1cbd01924891cd We have deployed fixes for the underlying issue, and remaining impact is limited to a backlog of pending malware scans. Until a package's scan completes, requests for it may fail or return MALWARE_SCAN_PENDING. We expect this process to take approximately 3 more hours. Separately, a small number of packages were incorrectly flagged and blocked by malware scanning, i.e., false positives. We are reviewing and unblocking these; if a specific package remains blocked or unavailable for you, please open a support ticket. https://status.chainguard.dev/incident/1007862 Mon, 10 Aug 2026 23:46:00 -0000 https://status.chainguard.dev/incident/1007862#bf1a2e134456703654fcf3fc7d0bb2f572e5876b15b64f6cae6a1c2bd06881e0 We've identified an issue affecting the timing of malware scan completion for some upstream packages, which may cause download errors (MALWARE_SCAN_PENDING) for a subset of packages. We've found no evidence that any customer has downloaded a package later confirmed to be malicious. We've increased scanning capacity and deployed a fix to staging, and are working to fully resolve the backlog. We'll post updates as we have them. https://status.chainguard.dev/incident/999377 Fri, 07 Aug 2026 10:49:00 -0000 https://status.chainguard.dev/incident/999377#7734c99d33024bbc085bf14f1c3fec80ce30f525eba3d53ae103e64b65811c8d 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 MB_ENABLE_PUBLIC_SHARING to true — but only if your instance is not publicly reachable. We intend to restore the previous default once upstream releases a full fix. Please note on vulnerability scanners. Upstream Metabase has not yet cut a versioned release, so the image version number remains within the advisories' affected range. Scanners may therefore flag the patched image as vulnerable even though the fix and mitigations are in place. We will update the version once upstream publishes a release. Recommended actions. If you have not already done so, complete the steps from our earlier update: update to the latest patched image, revoke active sessions, delete any unrecognized API keys, audit administrator accounts, and rotate credentials for any connected databases. Upgrading alone does not remove access an attacker may have already established, so these steps remain important. This incident is now resolved. Thank you for your patience. https://status.chainguard.dev/incident/999377 Fri, 07 Aug 2026 10:22:00 -0000 https://status.chainguard.dev/incident/999377#9c2587e4f38251bef90e9b2787855c267abbade0e94c133319b03ec51ea54a0a We have identified of a security vulnerability in upstream Metabase that affects the Metabase container image published by Chainguard. A small number of customers running the affected image may be exposed until they update. A patched image is currently being built and is expected to be released shortly. We will be monitoring propagation to confirm all affected image tags are updated. Recommended actions for anyone running our Metabase image. These apply regardless of whether you have updated, because some steps address exposure that an update alone does not remove: Update to the latest patched Chainguard Metabase image once available. Block access to the password reset endpoint (/api/session/reset_password) at your ingress. Revoke active sessions. Delete any API keys you do not recognize. Audit administrator accounts for unexpected changes. Rotate credentials for any databases connected to Metabase. Please note: upgrading the image alone is not sufficient, as any attacker-created API keys or previously exposed database credentials will persist after an upgrade. We will post a further update once the patched image has released. https://status.chainguard.dev/incident/998586 Fri, 07 Aug 2026 00:37:00 -0000 https://status.chainguard.dev/incident/998586#3ae010c4514dad94429343ec6eb42aeed2aa78f9e01a892fbd4b8c2ace125ca1 Build activity has returned to normal. Users should see new image and package updates as they are expected. https://status.chainguard.dev/incident/998586 Thu, 06 Aug 2026 23:54:00 -0000 https://status.chainguard.dev/incident/998586#c8b0270dbc8284b10ccae4ddf6a780894e754525079de3c303f7aff9c125f746 We are continuing to see image and package builds are continuing to complete successfully. We will continue monitoring the status and update here. https://status.chainguard.dev/incident/998586 Thu, 06 Aug 2026 23:23:00 -0000 https://status.chainguard.dev/incident/998586#839fe817e4e13d0330eea41ce95848816ef5bfe3c2c4757a917f859bd09824b6 We are beginning to see package and image builds be processed successfully, though some may still experience delays as GitHub continues to drain their backlog and fully restore throughput. GitHub has deployed fixes and is making progress on recovery. They report 99% success rates for workflow runs that are able to start, and are gradually restoring webhook-triggered workflow throughput. We are seeing build activity resume in our internal dashboards, though the recovery process is still ongoing. We are actively monitoring GitHub's recovery progress as well as our internal build processes. We will provide updates as the situation evolves. If you have urgent questions or concerns, please reach out to our support team. https://status.chainguard.dev/incident/998586 Thu, 06 Aug 2026 22:30:00 -0000 https://status.chainguard.dev/incident/998586#bbfd286159a8d444cebed54e2a71d06b31119ad8aa090bf6da20bcd874a16aa9 We continue to experience delays with package and container image builds due to an upstream GitHub outage that began at 19:08 UTC today. GitHub has deployed fixes that have improved job completion rates for workflow runs that are able to start (now at 97% success). However, webhook triggers remain throttled as part of their recovery process, which means many push and pull request events are not yet triggering new build workflows. This is preventing most of package and image builds from starting. We understand this impacts your release schedules and any CVE remediation work with upcoming deadlines. We are actively monitoring GitHub's recovery progress and will resume normal build operations as soon as their service is restore. We will provide updates as the situation evolves. If you have urgent questions or concerns, please reach out to our support team. https://status.chainguard.dev/incident/998586 Thu, 06 Aug 2026 19:22:00 -0000 https://status.chainguard.dev/incident/998586#84fb4355cad07d50382a84e8d3642bdc5f3b050c5bc08ab8c540e0128d56d47e We are currently experiencing delays with package and container image builds due to an upstream GitHub outage. Our build infrastructure remains operational, but we are unable to process new build requests until GitHub service is restored. We understand this may impact your release schedules and CVE remediation timelines. We are actively monitoring the GitHub status page and will resume normal build operations as soon as their service is available. We will provide updates as we learn more about the expected resolution timeline. If you have any urgent questions or concerns, please reach out to our support team. Thank you for your patience as we work through this issue. https://status.chainguard.dev/incident/973393 Wed, 22 Jul 2026 09:47:00 -0000 https://status.chainguard.dev/incident/973393#f8e2002af566ba52a84e74b309341a8fc0ccb3fa9052e1aa467b5b0f4b3ed9d9 Cloudflare have implemented a fix and are monitoring their services. The Chainguard services have recovered and the services are being monitored. https://status.chainguard.dev/incident/969348 Mon, 20 Jul 2026 03:49:00 -0000 https://status.chainguard.dev/incident/969348#f008e7307d8970f1d03d43780efff7c23088f3fca2e473936bce012d20aa669b We've mitigated the issue and are continuing to monitor the affected services. https://status.chainguard.dev/incident/969348 Mon, 20 Jul 2026 03:21:00 -0000 https://status.chainguard.dev/incident/969348#6a65b56e4f83ee1aa96ad0bb12034ff29e34cc2da0190a23e453ee9c52bfd67a We have identified the issue and are actively working on a resolution. https://status.chainguard.dev/incident/969348 Mon, 20 Jul 2026 02:57:00 -0000 https://status.chainguard.dev/incident/969348#de8fef55e7a93e9bb1420eea2c2851903f12c6ef4859eac5645612e8cd05f4c9 We are aware of degradations with the Chainguard API and are actively working to fix these issues. https://status.chainguard.dev/incident/948739 Wed, 15 Jul 2026 02:00:29 -0000 https://status.chainguard.dev/incident/948739#4f1f09a383a50df941ecfc2bcee2924fb10ca64c9831942d3f86a02860bea40f Chainguard authentication and authorization services will be briefly unavailable during this window. Sign-in and permission-based actions may fail. No action required; services will resume automatically after maintenance completes. https://status.chainguard.dev/incident/948173 Thu, 09 Jul 2026 11:46:00 -0000 https://status.chainguard.dev/incident/948173#279f437a6d9de394c5e2551d9c697568dcee231d759c522f7785057598ffc618 After investigation we have identified that the 403 errors were a false positive and the services were not degraded or effected during this time. https://status.chainguard.dev/incident/948173 Thu, 09 Jul 2026 10:37:00 -0000 https://status.chainguard.dev/incident/948173#f27408698181e4fbb374033735a86256267f4eb65546b428202d903aae9c00d0 A small number of customers may see 403 errors when attempting to access Libraries. Chainguard engineering are investigating this issue. Further updates will be published as we progress. https://status.chainguard.dev/incident/941888 Thu, 09 Jul 2026 02:00:00 -0000 https://status.chainguard.dev/incident/941888#ce101560a805f3aec46f380b5069ba89eb1185fcf9a59f275ab3c6e4bfcd4da6 Chainguard authentication and authorization services will be briefly unavailable during this window. Sign-in and permission-based actions may fail. No action required; services will resume automatically after maintenance completes. https://status.chainguard.dev/incident/929025 Tue, 30 Jun 2026 03:00:00 -0000 https://status.chainguard.dev/incident/929025#2071171b5f1901e4cf15be3c6f6c1f56f0db4e47edf4922a2bfc87ba6c786d01 Chainguard authentication and authorization services will be briefly unavailable during this window. Sign-in and permission-based actions may fail. No action required; services will resume automatically after maintenance completes. https://status.chainguard.dev/incident/936482 Fri, 26 Jun 2026 22:41:00 -0000 https://status.chainguard.dev/incident/936482#5ef6a94d17b0484bacf19133bc825caf1aab04a9625805f2d6e3063b516ca0f3 We have identified the root cause of the database connection exhaustion and the issues have been resolved. https://status.chainguard.dev/incident/936482 Fri, 26 Jun 2026 22:08:00 -0000 https://status.chainguard.dev/incident/936482#2ecb7083a2ecd67d61773bfead2fea7d70414c62f739ec86ce437758aa5ed415 Issues with a backend database due to exhausted connections are causing degraded availability for all Chainguard services. Engineers are currently working to mitigate the issue and restore services. We will share more information as is it is available. https://status.chainguard.dev/incident/935990 Fri, 26 Jun 2026 11:43:00 -0000 https://status.chainguard.dev/incident/935990#6bf58e227c47f6d5aa309e0ce55403fd36f30df7ea54516cbb2afc6941060803 We have fixed the cause of the missing Overviews and are starting to repopulate them. https://status.chainguard.dev/incident/935990 Fri, 26 Jun 2026 09:19:00 -0000 https://status.chainguard.dev/incident/935990#fc8cbe3760f04fcab3b24f61edb73cf32bc288cdb4a43603cf093a8deffc4f75 The image 'Overview' section on console.chainguard.dev is currently not rendering end-user usage documentation. This has no impact on overall functionality or image availability. We are working to restore the Overview. https://status.chainguard.dev/incident/935422 Thu, 25 Jun 2026 20:11:00 -0000 https://status.chainguard.dev/incident/935422#dda1ecc6ad892b5621b6d5869c6e0fae313f378279768f5f6c3b626907173bce 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. https://status.chainguard.dev/incident/928226 Fri, 19 Jun 2026 00:04:00 -0000 https://status.chainguard.dev/incident/928226#50a5c67ff3930b74f2947faf6098b5df5f351f72a3f4b91eabb5cadcca8ee23a 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. https://status.chainguard.dev/incident/928226 Thu, 18 Jun 2026 23:39:00 -0000 https://status.chainguard.dev/incident/928226#28e74aae1990185000088aa8b4c91d2769f4cb88171a850d884535abd41ac4a7 We are investigating a service issue affecting platform authentication and related services. Customers may experience issues authenticating to Chainguard services, including impacts to APK fetching, Libraries, and Console access. Our engineering team is actively investigating and working on mitigation and recovery efforts to restore service as quickly as possible. We will continue providing updates as more information becomes available. https://status.chainguard.dev/incident/928226 Thu, 18 Jun 2026 22:59:00 -0000 https://status.chainguard.dev/incident/928226#60e6176e31bf267b1f04694dedbe6b3eee38ebb0b065f05355ef50a05f829972 We’re investigating an issue with platform services that is impacting some users. We’re working to fix the problem as quickly as we can. We’ll share another update shortly. https://status.chainguard.dev/incident/920170 Wed, 10 Jun 2026 18:40:00 -0000 https://status.chainguard.dev/incident/920170#b63b5d20db0622987003a506ac5a98a7199e2868e52dde2bd5d10aee063d3554 The issue has been resolved and we've confirmed that the Vulnerability and Advisory APIs are now accessible. https://status.chainguard.dev/incident/920170 Wed, 10 Jun 2026 18:31:00 -0000 https://status.chainguard.dev/incident/920170#ba6bc090c862bd78267f0af1640ee0c992094480eada7ea06b274f008ff75f11 The Vulnerability and Advisory APIs are currently unavailable and impact certain features within the Chainguard Console and chainctl. We are currently investigating the issue and will update you as soon as we have more information. https://status.chainguard.dev/incident/905964 Wed, 27 May 2026 00:07:00 -0000 https://status.chainguard.dev/incident/905964#03d1cf918c2632114f2c58ac7695cee4b1a433004e8bac1f26369cd053929962 The affected services have now been stabilized. We are continuing to monitor the environment. We sincerely apologize for the disruption caused by the errors impacting the APK registry backend and authentication backend. We will share a full RCA with customers. Thank you for your patience and understanding while we worked through this issue. https://status.chainguard.dev/incident/905964 Tue, 26 May 2026 23:51:00 -0000 https://status.chainguard.dev/incident/905964#b567ae6d331bec17b0daabd4ae54c36cf163a45da94565ac792a1bce6abd2fd7 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. https://status.chainguard.dev/incident/905964 Tue, 26 May 2026 23:23:00 -0000 https://status.chainguard.dev/incident/905964#d0ace6b29015e5822d43b4e1c32f266ae289348252ec667e7a8da3f87f44ab3c We are investigating a service issue affecting platform authentication and related services. Customers may experience issues authenticating to Chainguard services, including impacts to APK fetching, Libraries, and Console access. Our engineering team is actively investigating and working on mitigation and recovery efforts to restore service as quickly as possible. We will continue providing updates as more information becomes available. https://status.chainguard.dev/incident/905964 Tue, 26 May 2026 22:07:00 -0000 https://status.chainguard.dev/incident/905964#e0be219d106687184bf8d11450a88cc2ec73d4d20e4fa27a6eb9eed80de2abee We are aware of customers experiencing issues with authenticating and APK fetching. This issue is currently under investigation. https://status.chainguard.dev/incident/891047 Tue, 12 May 2026 15:32:00 -0000 https://status.chainguard.dev/incident/891047#e862b6f0fbbfbf70d7ea77cadbb163683ae0f392aa0adc416d7119553c311ee3 We sincerely apologize for the disruption caused by elevated 5XX error rates impacting the APK registry backend. Since enabling package deduplication, memory utilization has stabilized between 10–30%, and 5XX error rates have returned to near-zero levels, with only occasional brief spikes observed. Overall service health has significantly improved, and we are continuing to monitor the platform closely to ensure stability. Thank you for your patience while we worked through this issue. https://status.chainguard.dev/incident/891047 Fri, 08 May 2026 23:00:00 -0000 https://status.chainguard.dev/incident/891047#63ef25f4e7b64736bdf0af774aa85d92299d6aa0481c84c636ce70826d3ed241 The overall error rate and impact on CI workflows is now much lower and less disruptive for affected customers. We are actively monitoring error and memory metrics to confirm sustained stability before declaring a full resolution. https://status.chainguard.dev/incident/891047 Fri, 08 May 2026 19:14:00 -0000 https://status.chainguard.dev/incident/891047#1e53522636a1d9ffce7043c36b85b0b4c53d103ff0a7890edac3fe962bab7896 We've deployed the APKINDEX LRU cache update to production, which has led to a significant drop in 503 errors and error-rate spikes for APK downloads from virtualapk.cgr.dev. Some 503s are still being observed because the cache size appears to be larger than ideal, and the average entry size was underestimated. However, overall service reliability has improved and error rates are much lower than before the change. We will lower the cache size to better reflect the average cache entry size and lower the rate of 503s even further today. https://status.chainguard.dev/incident/891047 Fri, 08 May 2026 13:11:00 -0000 https://status.chainguard.dev/incident/891047#028fbeba99f54ea55f36fc5c6d0fe15a52ecf9e6fa6c1592d405efe0df59ea51 We are investigating intermittent failures affecting virtualapk.cgr.dev, where some APK index and package fetch requests may return temporary errors during short periods of elevated load. We have identified the root cause and are rolling out mitigations to improve stability. During impacted windows, retries typically succeed. The most reliable workaround is having retry-on-failure logic around CI/CD jobs. Reruns almost always succeed once the backend is healthy. We will provide additional updates as mitigation rollout progresses. https://status.chainguard.dev/incident/875898 Tue, 21 Apr 2026 00:10:22 -0000 https://status.chainguard.dev/incident/875898#c71a4ee1ae739b0621aafe29a69d686ed328d499c7ea732a00cd9c6340b4d699 Maintenance completed https://status.chainguard.dev/incident/875898 Tue, 21 Apr 2026 00:00:22 -0000 https://status.chainguard.dev/incident/875898#74a101c4e4f3a352d27263d80602cb01ec1fad8e1e9e1b7d788644f593d36c13 🔧 Quick heads up — we'll be performing a scheduled update to our Console and Chainguard Support system today at 5:00 PM PST. Expect approximately 5 minutes of downtime. We'll be back up shortly after. Thanks for your patience! 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/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/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 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.