Amazee incident

Limited workload scaling and deployments

Minor Resolved View vendor source →

Amazee experienced a minor incident on October 20, 2025 affecting jp1.lagoon and ca1.lagoon and 1 more component, lasting 4h 27m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 09:34 AM UTC
Resolved
Oct 20, 2025, 02:02 PM UTC
Duration
4h 27m
Detected by Pingoru
Oct 20, 2025, 09:34 AM UTC

Affected components

jp1.lagoonca1.lagoonie1.lagoonDeployment Infrastructurede3.lagoonfi2.lagoonau2.lagoonus2.lagoonuk3.lagoonus3.lagoon

Update timeline

  1. monitoring Oct 20, 2025, 09:34 AM UTC

    Due to an upstream issue within AWS some workloads could not be scaled or deployed. The issue also affects our support system which is only partially available.

  2. monitoring Oct 20, 2025, 11:17 AM UTC

    Some workloads in us2.lagoon are blocked from starting up due to the upstream issue. Other regions are no longer affected by this.

  3. resolved Oct 20, 2025, 02:02 PM UTC

    We are no longer seeing workloads affected by this issue.