Incidents reported on status page for Chainguard, Inc. https://status.enforce.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/575c0a90b7515886c682f0109ca28f07.png https://status.enforce.dev/ en https://status.enforce.dev/ Tue, 02 Sep 2025 08:05:48 +0000 https://status.enforce.dev/#c9314da05a0b41a37947e734f010bc5e831823b13cc413453e6ae559e0792a37 Registry recovered https://status.enforce.dev/ Tue, 02 Sep 2025 07:00:36 +0000 https://status.enforce.dev/#c9314da05a0b41a37947e734f010bc5e831823b13cc413453e6ae559e0792a37 Registry went down https://status.enforce.dev/ Tue, 26 Aug 2025 19:20:14 +0000 https://status.enforce.dev/#4ec27a0d4136069f3048421c412fc1c3053fcc63e0507e72dda2dd45c69743fd Issuer recovered https://status.enforce.dev/ Tue, 26 Aug 2025 19:20:01 +0000 https://status.enforce.dev/#3baf63bdb354e49963aa356dd677d53d3b825faa162b8d18c80886eb153a9b89 Registry recovered https://status.enforce.dev/ Tue, 26 Aug 2025 19:18:56 +0000 https://status.enforce.dev/#05f87ab76ed64af74ea321c545878f1f9f496cde4f3bce16ba3b0fecaf5b5132 API recovered https://status.enforce.dev/ Tue, 26 Aug 2025 19:05:57 +0000 https://status.enforce.dev/#4ec27a0d4136069f3048421c412fc1c3053fcc63e0507e72dda2dd45c69743fd Issuer went down https://status.enforce.dev/ Tue, 26 Aug 2025 19:05:38 +0000 https://status.enforce.dev/#3baf63bdb354e49963aa356dd677d53d3b825faa162b8d18c80886eb153a9b89 Registry went down https://status.enforce.dev/ Tue, 26 Aug 2025 19:04:21 +0000 https://status.enforce.dev/#05f87ab76ed64af74ea321c545878f1f9f496cde4f3bce16ba3b0fecaf5b5132 API went down https://status.enforce.dev/ Thu, 14 Aug 2025 16:30:28 +0000 https://status.enforce.dev/#e37e6b74524a8f5568ab4514e5a7fe29f14656297ade6597ecafed4093461a23 Issuer recovered https://status.enforce.dev/ Thu, 14 Aug 2025 16:29:49 +0000 https://status.enforce.dev/#04c3187bedd7d0248c3d74f6e9904d59957f3a00015c7f22e1e2700dd1ec7530 Registry recovered https://status.enforce.dev/ Thu, 14 Aug 2025 16:29:26 +0000 https://status.enforce.dev/#0ea867fbac2e0b98e1b934dc681bb854720c9199f283b1bdb64eb0ea61e6ad50 API recovered https://status.enforce.dev/ Thu, 14 Aug 2025 16:26:43 +0000 https://status.enforce.dev/#04c3187bedd7d0248c3d74f6e9904d59957f3a00015c7f22e1e2700dd1ec7530 Registry went down https://status.enforce.dev/ Thu, 14 Aug 2025 16:26:10 +0000 https://status.enforce.dev/#e37e6b74524a8f5568ab4514e5a7fe29f14656297ade6597ecafed4093461a23 Issuer went down https://status.enforce.dev/ Thu, 14 Aug 2025 16:24:13 +0000 https://status.enforce.dev/#0ea867fbac2e0b98e1b934dc681bb854720c9199f283b1bdb64eb0ea61e6ad50 API went down https://status.enforce.dev/ Mon, 11 Aug 2025 07:20:37 +0000 https://status.enforce.dev/#7a620fc8832be5b1b72e372b8898170fd9acf11f19ea0952179c41b4273af716 API recovered https://status.enforce.dev/ Mon, 11 Aug 2025 07:14:33 +0000 https://status.enforce.dev/#7a620fc8832be5b1b72e372b8898170fd9acf11f19ea0952179c41b4273af716 API went down https://status.enforce.dev/ Sun, 10 Aug 2025 23:13:05 +0000 https://status.enforce.dev/#548620c567bb7d45fd262fbae79f337efd301bf99ae4250d7d7a4bd83ea8473f Issuer recovered https://status.enforce.dev/ Sun, 10 Aug 2025 23:10:59 +0000 https://status.enforce.dev/#548620c567bb7d45fd262fbae79f337efd301bf99ae4250d7d7a4bd83ea8473f Issuer went down https://status.enforce.dev/ Sun, 10 Aug 2025 19:48:03 +0000 https://status.enforce.dev/#09a4542ee0d3e6e01d487468d600382db60ed64fe37f331941e8498bfc44fe7d Issuer recovered https://status.enforce.dev/ Sun, 10 Aug 2025 19:47:49 +0000 https://status.enforce.dev/#c22ca3946ca2d527a72ab0319c341e59e04507bad526c308c6626b8da0363b22 Registry recovered https://status.enforce.dev/ Sun, 10 Aug 2025 19:43:05 +0000 https://status.enforce.dev/#09a4542ee0d3e6e01d487468d600382db60ed64fe37f331941e8498bfc44fe7d Issuer went down https://status.enforce.dev/ Sun, 10 Aug 2025 19:42:47 +0000 https://status.enforce.dev/#c22ca3946ca2d527a72ab0319c341e59e04507bad526c308c6626b8da0363b22 Registry went down https://status.enforce.dev/ Sun, 10 Aug 2025 19:36:42 +0000 https://status.enforce.dev/#5e57f1c0db23076102713c299385c8d1f12944f260a42d1a43a0fa0598941e2d Registry recovered https://status.enforce.dev/ Sun, 10 Aug 2025 19:32:57 +0000 https://status.enforce.dev/#e2ab765aaba7b63b61f8e5328ce85e86036520b750cbd3bf80443a792bd0e22d Issuer recovered https://status.enforce.dev/ Sun, 10 Aug 2025 19:27:56 +0000 https://status.enforce.dev/#e2ab765aaba7b63b61f8e5328ce85e86036520b750cbd3bf80443a792bd0e22d Issuer went down https://status.enforce.dev/ Sun, 10 Aug 2025 19:27:40 +0000 https://status.enforce.dev/#5e57f1c0db23076102713c299385c8d1f12944f260a42d1a43a0fa0598941e2d Registry went down https://status.enforce.dev/ Sun, 10 Aug 2025 09:13:05 +0000 https://status.enforce.dev/#f4b1083bfd0e72fd15b4a10e7669a4761495ca337af84f5b9f2eeb0cf7bdda5b Registry recovered https://status.enforce.dev/ Sun, 10 Aug 2025 09:12:53 +0000 https://status.enforce.dev/#78749d79fe3fd5bd451b032d96c9a7d8b5fc49e7407509a23fc4c258d4ddc7bf Issuer recovered https://status.enforce.dev/ Sun, 10 Aug 2025 09:08:04 +0000 https://status.enforce.dev/#78749d79fe3fd5bd451b032d96c9a7d8b5fc49e7407509a23fc4c258d4ddc7bf Issuer went down https://status.enforce.dev/ Sun, 10 Aug 2025 09:07:39 +0000 https://status.enforce.dev/#f4b1083bfd0e72fd15b4a10e7669a4761495ca337af84f5b9f2eeb0cf7bdda5b Registry went down https://status.enforce.dev/ Sun, 10 Aug 2025 08:57:53 +0000 https://status.enforce.dev/#ab1a4a4e94c7cd414ee985f0206e6224adaf31b8e4824e722e81ee46f7a5fd84 Issuer recovered https://status.enforce.dev/ Sun, 10 Aug 2025 08:54:59 +0000 https://status.enforce.dev/#a1bd8015b6a3c4ae4c7bbac3a9e5bf8695efd3e81b6c4d667ff449d651a87616 Registry recovered https://status.enforce.dev/ Sun, 10 Aug 2025 08:47:54 +0000 https://status.enforce.dev/#ab1a4a4e94c7cd414ee985f0206e6224adaf31b8e4824e722e81ee46f7a5fd84 Issuer went down https://status.enforce.dev/ Sun, 10 Aug 2025 08:47:39 +0000 https://status.enforce.dev/#a1bd8015b6a3c4ae4c7bbac3a9e5bf8695efd3e81b6c4d667ff449d651a87616 Registry went down https://status.enforce.dev/ Fri, 08 Aug 2025 10:25:49 +0000 https://status.enforce.dev/#292e2e2b282723c58b01a32a2ec0f03b3101cc26984c64f273404ab9d26a16fc Registry recovered https://status.enforce.dev/ Fri, 08 Aug 2025 10:20:47 +0000 https://status.enforce.dev/#292e2e2b282723c58b01a32a2ec0f03b3101cc26984c64f273404ab9d26a16fc Registry went down https://status.enforce.dev/ Fri, 08 Aug 2025 04:30:14 +0000 https://status.enforce.dev/#71e7bff5f03fefa3ca91912bc83d541db02feab1cb89208bcfc0b198da2d0e5e Issuer recovered https://status.enforce.dev/ Fri, 08 Aug 2025 04:29:55 +0000 https://status.enforce.dev/#b5eb3a1f08c1398e50e1c801984984043eade611bd99b15971449cf830a2c89f Registry recovered https://status.enforce.dev/ Fri, 08 Aug 2025 04:25:13 +0000 https://status.enforce.dev/#71e7bff5f03fefa3ca91912bc83d541db02feab1cb89208bcfc0b198da2d0e5e Issuer went down https://status.enforce.dev/ Fri, 08 Aug 2025 04:24:53 +0000 https://status.enforce.dev/#b5eb3a1f08c1398e50e1c801984984043eade611bd99b15971449cf830a2c89f Registry went down https://status.enforce.dev/ Sat, 02 Aug 2025 03:06:06 +0000 https://status.enforce.dev/#2daad22d007b71332f663e9834098f351e74154ef8833557d841ce7b758c6d11 Registry recovered https://status.enforce.dev/ Sat, 02 Aug 2025 03:03:10 +0000 https://status.enforce.dev/#2daad22d007b71332f663e9834098f351e74154ef8833557d841ce7b758c6d11 Registry went down https://status.enforce.dev/ Wed, 30 Jul 2025 21:48:07 +0000 https://status.enforce.dev/#d91b146614eb4c2a81dcd243b64b7daf6876a0198d8d3908f8e7a69829e0d147 Issuer recovered https://status.enforce.dev/ Wed, 30 Jul 2025 21:47:52 +0000 https://status.enforce.dev/#ad0ba3c67b433f2b8f8a6b2b060d0f8fa9889e81bd098a15f3ef986751c76422 Registry recovered https://status.enforce.dev/ Wed, 30 Jul 2025 21:44:44 +0000 https://status.enforce.dev/#ad0ba3c67b433f2b8f8a6b2b060d0f8fa9889e81bd098a15f3ef986751c76422 Registry went down https://status.enforce.dev/ Wed, 30 Jul 2025 21:44:12 +0000 https://status.enforce.dev/#d91b146614eb4c2a81dcd243b64b7daf6876a0198d8d3908f8e7a69829e0d147 Issuer went down https://status.enforce.dev/ Mon, 21 Jul 2025 22:16:54 +0000 https://status.enforce.dev/#346d16f6699e972bbcb39ffe137594b50dd425ec4043b0346202dd034fc4365c API recovered https://status.enforce.dev/ Mon, 21 Jul 2025 21:56:47 +0000 https://status.enforce.dev/#346d16f6699e972bbcb39ffe137594b50dd425ec4043b0346202dd034fc4365c API went down https://status.enforce.dev/ Mon, 21 Jul 2025 18:22:54 +0000 https://status.enforce.dev/#28b39bc64ae74c54e478d1a2b5d912a6d99206003638f2fdd379c3fb7e2465b7 API recovered https://status.enforce.dev/ Mon, 21 Jul 2025 17:57:44 +0000 https://status.enforce.dev/#28b39bc64ae74c54e478d1a2b5d912a6d99206003638f2fdd379c3fb7e2465b7 API went down https://status.enforce.dev/ Mon, 30 Jun 2025 21:47:27 +0000 https://status.enforce.dev/#64551c53753e723ac8cf1c26a886ccb0ac212238d9173f107f783886114b8bc9 Registry recovered https://status.enforce.dev/ Mon, 30 Jun 2025 21:42:27 +0000 https://status.enforce.dev/#64551c53753e723ac8cf1c26a886ccb0ac212238d9173f107f783886114b8bc9 Registry went down https://status.enforce.dev/incident/602079 Thu, 12 Jun 2025 20:42:00 -0000 https://status.enforce.dev/incident/602079#1bb2b50fc9c2295a847fcfd43115890adcc3437152d2f1ca571255a643dc204a We’ve completed our monitoring and can confirm that all services have returned to normal. The 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. https://status.enforce.dev/incident/602079 Thu, 12 Jun 2025 20:42:00 -0000 https://status.enforce.dev/incident/602079#1bb2b50fc9c2295a847fcfd43115890adcc3437152d2f1ca571255a643dc204a We’ve completed our monitoring and can confirm that all services have returned to normal. The 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. https://status.enforce.dev/incident/602079 Thu, 12 Jun 2025 20:42:00 -0000 https://status.enforce.dev/incident/602079#1bb2b50fc9c2295a847fcfd43115890adcc3437152d2f1ca571255a643dc204a We’ve completed our monitoring and can confirm that all services have returned to normal. The 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. https://status.enforce.dev/incident/602079 Thu, 12 Jun 2025 20:42:00 -0000 https://status.enforce.dev/incident/602079#1bb2b50fc9c2295a847fcfd43115890adcc3437152d2f1ca571255a643dc204a We’ve completed our monitoring and can confirm that all services have returned to normal. The 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. https://status.enforce.dev/incident/530882 Wed, 19 Mar 2025 15:58:00 -0000 https://status.enforce.dev/incident/530882#db76b2b75bd06e0b4d3333ca064f8bd0be6418c7d480d1e1c77cf0539596234e Due to a recent refactoring, the prober were misconfigured for the duration of Mar 17-18, 2025. The issue has been corrected. All services were operating normally during the noted duration. https://status.enforce.dev/incident/530882 Wed, 19 Mar 2025 15:58:00 -0000 https://status.enforce.dev/incident/530882#db76b2b75bd06e0b4d3333ca064f8bd0be6418c7d480d1e1c77cf0539596234e Due to a recent refactoring, the prober were misconfigured for the duration of Mar 17-18, 2025. The issue has been corrected. All services were operating normally during the noted duration. https://status.enforce.dev/incident/530882 Wed, 19 Mar 2025 15:58:00 -0000 https://status.enforce.dev/incident/530882#db76b2b75bd06e0b4d3333ca064f8bd0be6418c7d480d1e1c77cf0539596234e Due to a recent refactoring, the prober were misconfigured for the duration of Mar 17-18, 2025. The issue has been corrected. All services were operating normally during the noted duration.