Amazee outage history

We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

This incident has been resolved.

amazee.io is aware of an upcoming critical PHP security release that will fix two CVEs: CVE-2026-109618 and CVE-2026-109619. The release is scheduled for Wednesday, 21 October 2026 at 14:00 UTC. As soon as a patch is available, Lagoon base images will be updated and customers are encouraged to redeploy as soon as possible. For more information, see the upstream PHP announcement: https://www.php.net/archive/2026.php#2026-10-20-1 We are monitoring the situation and investigating platform-level mitigations. We will update this status page with additional information as it becomes available.

We have enabled the virtual patch for customers using our managed NGWAF. You should still upgrade your Lagoon base images as soon as a patch is available.

The fixed PHP versions have been released, and more details have been announced, including mitigations https://www.php.net/archive/2026.php#2026-10-21-5. We are waiting for the new versions to get released to all our upstream dependencies before we can release a new version of the Lagoon base images.

New Lagoon images are currently building. The required upstream Docker images have been released. We are currently building and testing version 26.10.0 of our Lagoon base images. The new images will be published shortly. We will provide a final update as soon as they are available for deployment.

Lagoon base images v26.10.0 are now published and available. Customers are advised to deploy their environments to patch the PHP vulnerabilities. We have increased resources to help reduce build queues, but expect wait times while all deployments are processed. We will continue to monitor deployment queues until operations normalize.

We are investigating an issue with our internal docker registry

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're going to be rolling back the traefik migration in CH4 to investigate issues

Rollback has completed. Some sites may have experienced longer outage during the rollback than others.

This incident has been resolved.

We are performing an ingress migration. Minimal outage is expected, and we'll be back to normal service shortly.

This incident has been resolved.

We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

This incident has been resolved.

We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We have noticed an increase in the wait times for deployments and are currently investigating this issue.

We have identified the cause for the delay and are implementing the fix.

A fix has been implemented and we are monitoring the issue.

The issue has been resolved.

We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

This incident has been resolved.

There is a delay in log processing and recent logs for events generated since July 1st may not be available. Real time logs can be accessed through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and we are working to address it.

A fix has been implemented and we are monitoring the results.

The access roles are resyncing and we are monitoring progress.

We are continuing to monitor the resync progress.

This incident has been resolved.

TLS certificate provisioning and renewal may be delayed on affected clusters during this window. We are monitoring the upstream incident and will provide updates as the situation evolves. https://status.redhat.com/

This incident has been resolved.

There is a delay in log processing and recent logs for events generated since June 1st may not be available. Real time logs can be accessed through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

This incident has been resolved.

Drupal has announced an upcoming highly critical Drupal core security release affecting Drupal 10 and 11 (and EOL versions 8 and 9). Customer impact - Prepare now: Update to the latest patch release on your current supported Drupal version ahead of time to reduce time-to-patch. - Schedule a maintenance window: May 20, 17:00 - 21:00 UTC. Customers should be prepared to apply the security update immediately once released. - EOL Drupal versions: Drupal 8.9 and 9.5 will receive patch files only (temporary mitigation). Plan an urgent upgrade to a supported version. Drupal 7 is not affected. What we're doing We're treating this as a priority security event and preparing WAF/CDN mitigations ("virtual patches") where possible. These may provide partial/temporary protection; applying the upstream Drupal security update remains the primary mitigation. We’ll share updates here as more information becomes available. For more information, see the Drupal PSA: https://www.drupal.org/psa-2026-05-18

We’ve reviewed today’s Drupal-related release and do not currently anticipate deploying WAF/CDN mitigations ("virtual patches"). Based on our assessment, overall exposure appears more limited than initial thoughts. Customers should review the security release notes to determine their potential impact and update as soon as practical: https://www.drupal.org/sa-core-2026-004. We will continue monitoring the situation and provide updates necessary.

This incident has been resolved.

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/

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

This incident has been resolved.

We are aware of CVE-2026-31431 / "Copy Fail" and have completed an initial assessment. We have not identified evidence of customer impact, service compromise, or active exploitation at this stage. We are prioritizing Linux kernel upgrades and will provide further updates if our assessment changes or if maintenance becomes necessary.

Mitigations at the Linux kernel level have been rolled out across all regions.

We are currently investigating a high error rate on the Fastly management API. This impacts deployments of new domains that are routed through Fastly. Existing setups on Fastly or traffic routing are not impacted.

Fastly is investigating the API issues and updating their status page at: https://www.fastlystatus.com/incident/378511 Impact: Deployments with new domains that are routed through Fastly will continue to work, but the actual domain setup in Fastly will be delayed.

Fastly resolved the issue with their management API and we'll keep monitoring the situation.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

There was an issue with an EKS rollout during maintenance, we are actively addressing this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We have identified an issue causing Lagoon builds to fail and are actively working to resolve.

We have applied a fix for this issue and are monitoring deployments.

The incident has been resolved.