Amazee incident

Volumes in read-only mode

Minor Resolved View vendor source →

Amazee experienced a minor incident on February 18, 2025 affecting au2.lagoon and us2.lagoon, lasting 1h 33m. The incident has been resolved; the full update timeline is below.

Started
Feb 18, 2025, 05:40 PM UTC
Resolved
Feb 18, 2025, 07:14 PM UTC
Duration
1h 33m
Detected by Pingoru
Feb 18, 2025, 05:40 PM UTC

Affected components

au2.lagoonus2.lagoon

Update timeline

  1. investigating Feb 18, 2025, 05:40 PM UTC

    We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications. While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

  2. identified Feb 18, 2025, 06:31 PM UTC

    We have rolled out a patch and will restart possibly affected workloads.

  3. identified Feb 18, 2025, 06:35 PM UTC

    We have updated the impacted regions to include au2.lagoon

  4. resolved Feb 18, 2025, 07:14 PM UTC

    All potentially affected workloads have been restarted.