Amazee incident

Degraded: cert-manager unavailable - TLS certificate issuance affected

Minor Ongoing View vendor source →

Amazee is currently experiencing a minor incident affecting jp1.lagoon and ca1.lagoon and 1 more component, which began 3h ago. The vendor's full update timeline is below.

Started
May 07, 2026, 06:08 PM UTC
Resolved
Ongoing
Duration
● 3h 3m
Detected by Pingoru
May 07, 2026, 06:08 PM UTC

Affected components

jp1.lagoonca1.lagoonie1.lagoonDeployment Infrastructurede3.lagoonfi2.lagoonau2.lagoonus2.lagoonuk3.lagoonus3.lagoonAMERAPACEMEAch4.lagoonamazee.ai infrastructure: au103amazee.ai infrastructure: de-eu101amazee.ai infrastructure: de103amazee.ai infrastructure: uk103amazee.ai infrastructure: us103amazee.ai infrastructure: us104amazee.ai infrastructure: ch103amazee.ai infrastructure

Update timeline

  1. identified May 07, 2026, 06:08 PM UTC

    We are currently experiencing an issue with cert-manager in affected clusters. The cert-manager controller pod is failing to start due to an image pull failure from quay.io (502 Bad Gateway), which is an external registry. Impact: New TLS certificates cannot be issued or renewed while cert-manager is unavailable. Existing certificates remain valid until their expiry. Services relying on automatic certificate provisioning may be affected if certificates expire during this window. https://status.redhat.com/

  2. monitoring May 07, 2026, 06:24 PM UTC

    All clusters are able to pull cert-manager image, we are currently monitoring statuspage https://status.redhat.com/