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/ 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/ Thu, 12 Jun 2025 20:38:10 +0000 https://status.enforce.dev/#6cf2bc9cae50665ad377ed3f45194f0633ee625f351a46742e36317efbfc8770 API recovered https://status.enforce.dev/ Thu, 12 Jun 2025 18:00:54 +0000 https://status.enforce.dev/#6cf2bc9cae50665ad377ed3f45194f0633ee625f351a46742e36317efbfc8770 API went down https://status.enforce.dev/ Thu, 17 Apr 2025 01:22:22 +0000 https://status.enforce.dev/#0910cfba98082eb632faf61efa5081681fa666a0145791eb45fe12e48ad3f239 API recovered https://status.enforce.dev/ Thu, 17 Apr 2025 01:16:19 +0000 https://status.enforce.dev/#0910cfba98082eb632faf61efa5081681fa666a0145791eb45fe12e48ad3f239 API went down https://status.enforce.dev/ Thu, 17 Apr 2025 01:15:31 +0000 https://status.enforce.dev/#69a4b5fb3904e4f4c4c973d5fc679c891ea4a83749867859e427a3f5d434002f API recovered https://status.enforce.dev/ Thu, 17 Apr 2025 01:10:19 +0000 https://status.enforce.dev/#69a4b5fb3904e4f4c4c973d5fc679c891ea4a83749867859e427a3f5d434002f API went down https://status.enforce.dev/ Thu, 17 Apr 2025 01:08:21 +0000 https://status.enforce.dev/#7d69639d62fe2af35bdcab81a1be5ad96f72e26ffa05522b05c76ac14e8f21ec API recovered https://status.enforce.dev/ Thu, 17 Apr 2025 01:02:19 +0000 https://status.enforce.dev/#7d69639d62fe2af35bdcab81a1be5ad96f72e26ffa05522b05c76ac14e8f21ec API went down https://status.enforce.dev/ Thu, 17 Apr 2025 01:01:41 +0000 https://status.enforce.dev/#e779d9340bdb05a48df5c10a223ffa5261929020d3408b78c4234700fcb9cd8a API recovered https://status.enforce.dev/ Thu, 17 Apr 2025 00:56:17 +0000 https://status.enforce.dev/#e779d9340bdb05a48df5c10a223ffa5261929020d3408b78c4234700fcb9cd8a API went down https://status.enforce.dev/ Thu, 17 Apr 2025 00:54:23 +0000 https://status.enforce.dev/#a6937f3bd1b7a081a48354c86f2cece621fec699a44b6c8ea1a5898c1f402004 API recovered https://status.enforce.dev/ Thu, 17 Apr 2025 00:48:18 +0000 https://status.enforce.dev/#a6937f3bd1b7a081a48354c86f2cece621fec699a44b6c8ea1a5898c1f402004 API went down https://status.enforce.dev/ Thu, 17 Apr 2025 00:47:18 +0000 https://status.enforce.dev/#51d45eeec4dd2e9947f62df912ff6775722a1c5ddd6609895ec9241a1c19a8ec API recovered https://status.enforce.dev/ Thu, 17 Apr 2025 00:12:19 +0000 https://status.enforce.dev/#51d45eeec4dd2e9947f62df912ff6775722a1c5ddd6609895ec9241a1c19a8ec API went down 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.