Amazee Outage History
Amazee is up right nowPingoru has recorded 47 incidents for Amazee: 32 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 60 of 720 (8%) |
| May 2026 | 2 | 604 of 744 (81%) |
| June 2026 | 3 | 79 of 720 (11%) |
| July 2026 | 5 | 41 of 744 (6%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 3 | 23 of 720 (3%) |
| October 2026 | 1 | 79 of 562 (14%) |
Incidents, newest first
Critical September 21, 2026 Issues with pulling images 3h 43m Deployment Infrastructure
Started Sep 21, 2026, 11:06 AM UTC· resolved Sep 21, 2026, 02:49 PM UTC
- investigating Sep 21, 2026, 11:06 AM UTC
We are investigating an issue with our internal docker registry
- identified Sep 21, 2026, 11:43 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 21, 2026, 11:43 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Sep 21, 2026, 11:44 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 21, 2026, 02:49 PM UTC
This incident has been resolved.
Major September 15, 2026 CH4 Traefik Migration Rollback 17h 8m ch4.lagoon
Started Sep 15, 2026, 04:25 AM UTC· resolved Sep 15, 2026, 09:33 PM UTC
- investigating Sep 15, 2026, 04:25 AM UTC
We're going to be rolling back the traefik migration in CH4 to investigate issues
- monitoring Sep 15, 2026, 05:07 AM UTC
Rollback has completed. Some sites may have experienced longer outage during the rollback than others.
- resolved Sep 15, 2026, 09:33 PM UTC
This incident has been resolved.
Notice September 7, 2026 Traefik Ingress Migration (UK3) 1h 57m uk3.lagoon
Started Sep 07, 2026, 10:16 PM UTC· resolved Sep 08, 2026, 12:14 AM UTC
- investigating Sep 07, 2026, 10:16 PM UTC
We are performing an ingress migration. Minimal outage is expected, and we'll be back to normal service shortly.
- resolved Sep 08, 2026, 12:14 AM UTC
This incident has been resolved.
Notice July 27, 2026 Regular Maintenance - amazee.ai Infrastructure 2h 12m amazee.ai infrastructure: au103, amazee.ai infrastructure: de-eu101, amazee.ai infrastructure: de103, amazee.ai infrastructure: uk103 and 4 more
Started Jul 27, 2026, 09:01 PM UTC· resolved Jul 27, 2026, 11:13 PM UTC
- investigating Jul 27, 2026, 09:01 PM UTC
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.
- resolved Jul 27, 2026, 11:13 PM UTC
This incident has been resolved.
Notice July 17, 2026 Increased Deployment Status Update Wait Times 21h 10m Lagoon API
Started Jul 17, 2026, 04:50 PM UTC· resolved Jul 18, 2026, 02:01 PM UTC
- investigating Jul 17, 2026, 04:50 PM UTC
We have noticed an increase in the wait times for deployments and are currently investigating this issue.
- identified Jul 17, 2026, 04:55 PM UTC
We have identified the cause for the delay and are implementing the fix.
- monitoring Jul 17, 2026, 08:34 PM UTC
A fix has been implemented and we are monitoring the issue.
- resolved Jul 18, 2026, 02:01 PM UTC
The issue has been resolved.
Notice July 1, 2026 Delayed log ingestion 3h 5m Lagoon Logs (OpenSearch)
Started Jul 01, 2026, 02:03 PM UTC· resolved Jul 01, 2026, 05:09 PM UTC
- monitoring Jul 01, 2026, 02:03 PM UTC
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
- resolved Jul 01, 2026, 05:09 PM UTC
This incident has been resolved.
Minor June 17, 2026 access issues with Lagoon Logs (kibana) 1d 23h Lagoon Logs (OpenSearch), Lagoon Logs (OpenSearch)
Started Jun 17, 2026, 02:39 AM UTC· resolved Jun 19, 2026, 02:32 AM UTC
- investigating Jun 17, 2026, 02:39 AM UTC
We are currently investigating this issue.
- identified Jun 17, 2026, 03:37 AM UTC
The issue has been identified and we are working to address it.
- monitoring Jun 17, 2026, 04:56 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 17, 2026, 04:57 AM UTC
The access roles are resyncing and we are monitoring progress.
- monitoring Jun 18, 2026, 02:00 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 19, 2026, 02:32 AM UTC
This incident has been resolved.
Minor June 1, 2026 Degraded certificate provisioning 16h 10m EMEA
Started Jun 01, 2026, 02:44 PM UTC· resolved Jun 02, 2026, 06:54 AM UTC
- monitoring Jun 01, 2026, 02:44 PM UTC
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/
- resolved Jun 02, 2026, 06:54 AM UTC
This incident has been resolved.
Notice May 19, 2026 Drupal security release (PSA-2026-05-18) 14d 4h
Started May 19, 2026, 02:09 AM UTC· resolved Jun 02, 2026, 06:54 AM UTC
- identified May 19, 2026, 02:09 AM UTC
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
- monitoring May 20, 2026, 07:26 PM UTC
We’ve reviewed today’s Drupal-related release and do not currently anticipate any required changes to customer environments. Based on our assessment, overall exposure appears limited, and we will continue monitoring the situation closely. We’ll provide additional updates if conditions change or further action becomes necessary.
- resolved Jun 02, 2026, 06:54 AM UTC
This incident has been resolved.
Minor May 7, 2026 Degraded: cert-manager unavailable - TLS certificate issuance affected 3h 6m jp1.lagoon, ca1.lagoon, ie1.lagoon, Deployment Infrastructure and 18 more
Started May 07, 2026, 06:08 PM UTC· resolved May 07, 2026, 09:14 PM UTC
- 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/
- 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/
- resolved May 07, 2026, 09:14 PM UTC
This incident has been resolved.
Minor April 30, 2026 CVE-2026-31431 / Copy Fail 13d 4h jp1.lagoon, ca1.lagoon, ie1.lagoon, de3.lagoon and 9 more
Started Apr 30, 2026, 01:33 AM UTC· resolved May 13, 2026, 06:01 AM UTC
- identified Apr 30, 2026, 01:33 AM UTC
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.
- resolved May 13, 2026, 06:01 AM UTC
Mitigations at the Linux kernel level have been rolled out across all regions.
Minor April 29, 2026 High error rate on Fastly Management API 3h 31m CDN
Started Apr 29, 2026, 09:19 AM UTC· resolved Apr 29, 2026, 12:51 PM UTC
- investigating Apr 29, 2026, 09:19 AM UTC
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.
- investigating Apr 29, 2026, 09:58 AM UTC
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.
- monitoring Apr 29, 2026, 11:15 AM UTC
Fastly resolved the issue with their management API and we'll keep monitoring the situation.
- resolved Apr 29, 2026, 12:51 PM UTC
This incident has been resolved.
Notice April 21, 2026 Degraded Performance 53m de3.lagoon, uk3.lagoon
Started Apr 21, 2026, 12:09 PM UTC· resolved Apr 21, 2026, 01:03 PM UTC
- investigating Apr 21, 2026, 12:09 PM UTC
We are currently investigating this issue.
- resolved Apr 21, 2026, 01:03 PM UTC
This incident has been resolved.
Notice April 15, 2026 Post-maintenance Rollout 3h 5m de3.lagoon
Started Apr 15, 2026, 04:19 AM UTC· resolved Apr 15, 2026, 07:24 AM UTC
- identified Apr 15, 2026, 04:19 AM UTC
There was an issue with an EKS rollout during maintenance, we are actively addressing this issue.
- monitoring Apr 15, 2026, 06:16 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 15, 2026, 07:24 AM UTC
This incident has been resolved.
Notice April 7, 2026 Increased Build Failures 1d 5h Deployment Infrastructure
Started Apr 07, 2026, 04:18 PM UTC· resolved Apr 08, 2026, 09:54 PM UTC
- identified Apr 07, 2026, 04:18 PM UTC
We have identified an issue causing Lagoon builds to fail and are actively working to resolve.
- monitoring Apr 07, 2026, 05:27 PM UTC
We have applied a fix for this issue and are monitoring deployments.
- resolved Apr 08, 2026, 09:54 PM UTC
The incident has been resolved.
Minor March 18, 2026 Increased Lagoon API error rate 1d 1h Lagoon API, Lagoon Dashboard
Started Mar 18, 2026, 01:41 PM UTC· resolved Mar 19, 2026, 02:52 PM UTC
- investigating Mar 18, 2026, 01:41 PM UTC
We are investigating increased error rates on the Lagoon API.
- identified Mar 19, 2026, 03:27 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 19, 2026, 02:52 PM UTC
This incident has been resolved.
Critical March 17, 2026 Lagoon API slow or degraded 14h 5m Lagoon API
Started Mar 17, 2026, 06:42 AM UTC· resolved Mar 17, 2026, 08:48 PM UTC
- investigating Mar 17, 2026, 06:42 AM UTC
We are currently investigating this issue.
- identified Mar 17, 2026, 07:45 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 17, 2026, 07:45 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 17, 2026, 08:48 PM UTC
This incident has been resolved.
Notice February 18, 2026 Changed processing of HTTP 425 responses in Google Chrome 49d 1h CDN
Started Feb 18, 2026, 07:01 AM UTC· resolved Apr 08, 2026, 08:10 AM UTC
- monitoring Feb 18, 2026, 07:01 AM UTC
In the latest release of Google Chrome (v145) the handling of HTTP 425 responses was changed. Should you see this affecting your sites, please reach out to our support and we'll look into applying mitigations for your specific use-case. Related status page from Fastly: https://www.fastlystatus.com/incident/378300#
- resolved Apr 08, 2026, 08:10 AM UTC
This incident has been resolved.
Minor February 9, 2026 Elevated Errors on Fastly level 12h 13m CDN
Started Feb 09, 2026, 07:38 PM UTC· resolved Feb 10, 2026, 07:52 AM UTC
- monitoring Feb 09, 2026, 07:38 PM UTC
Fastly has reported elevated errors affecting Fastly Applications. Existing certificates do not appear to be impacted; however, some services are experiencing issues when adding new domains. We are monitoring the Fastly status page: https://www.fastlystatus.com/
- resolved Feb 10, 2026, 07:52 AM UTC
This incident has been resolved.
Notice January 30, 2026 Intermittent SSH access issues 2d 23h Lagoon API
Started Jan 30, 2026, 02:59 PM UTC· resolved Feb 02, 2026, 02:29 PM UTC
- investigating Jan 30, 2026, 02:59 PM UTC
We're investigating intermittent SSH access to cloud clusters
- monitoring Jan 30, 2026, 03:58 PM UTC
We have identified and mitigated the cause for the SSH access issues, and are currently monitoring the portal.
- resolved Feb 02, 2026, 02:29 PM UTC
This incident has been resolved.
Notice January 28, 2026 HTTP Connection Errors 10h 20m us2.lagoon
Started Jan 28, 2026, 08:25 PM UTC· resolved Jan 29, 2026, 06:45 AM UTC
- monitoring Jan 28, 2026, 08:25 PM UTC
We found an HTTP connection errors issue. The underlying issue was resolved, and we are actively monitoring the status.
- resolved Jan 29, 2026, 06:45 AM UTC
This incident has been resolved.
Minor January 12, 2026 Increase in failed deployments 20h 2m Deployment Infrastructure
Started Jan 12, 2026, 11:05 AM UTC· resolved Jan 13, 2026, 07:08 AM UTC
- investigating Jan 12, 2026, 11:05 AM UTC
We have seen an increase in failed deployments and are currently investigating the cause for this.
- identified Jan 12, 2026, 11:33 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Jan 13, 2026, 07:08 AM UTC
This incident has been resolved.
Notice December 5, 2025 Public statement on CVE-2025-55182 75d 5h
Started Dec 05, 2025, 01:08 AM UTC· resolved Feb 18, 2026, 06:59 AM UTC
- monitoring Dec 05, 2025, 01:08 AM UTC
Summary We are aware of CVE-2025-55182, a critical vulnerability impacting certain versions of React Server Components and Next.js. Our priority is to protect customer workloads while upstream patches are applied. What we've done For customers using the Advanced WAF solution provided by amazee.io, we have enabled virtual patching in blocking mode to mitigate exploit attempts while application upgrades proceed. At this time, there is no mitigation available at the CDN layer. Customer action If your applications use affected React packages or frameworks (for example, Next.js 15.x or 16.x App Router), upgrade to patched versions as soon as possible per vendor guidance. * Continue standard secure development practices and monitor your application logs for anomalies. * Virtual patches reduce risk, but code upgrades remain the definitive fix. Support If you have questions about exposure, upgrade paths, or rule coverage, contact our support team through your standard channel. Our Commitment Security is central to our mission. We continuously work to strengthen protections, reduce risk, and keep our customers informed. References * CVE-2025-55182 record: https://www.cve.org/CVERecord?id=CVE-2025-55182 * React Server Components advisory: https://github.com/advisories/GHSA-fv66-9v8q-g76r * Next.js advisory: https://github.com/advisories/GHSA-9qr9-h5gf-34mp
- monitoring Dec 05, 2025, 07:23 AM UTC
We are continuing to monitor for any further issues.
- monitoring Dec 15, 2025, 04:50 PM UTC
Our review shows the affected React packages are present only in non-production amazee.io resources.
- resolved Feb 18, 2026, 06:59 AM UTC
This incident has been resolved.
Major December 1, 2025 Logging partially unavailable 1d 23h Lagoon Logs (OpenSearch)
Started Dec 01, 2025, 07:06 AM UTC· resolved Dec 03, 2025, 06:22 AM UTC
- identified Dec 01, 2025, 07:06 AM UTC
The logging infrastructure is rebalancing due to the new month starting which causes some requests to fail.
- monitoring Dec 02, 2025, 08:19 AM UTC
There is a backlog of logs to be ingested into the system. While this is happening in the background, some recent logs might not be visible in the logging system right away.
- resolved Dec 03, 2025, 06:22 AM UTC
The backlog has been processed and the logging system is fully available again.
Major November 16, 2025 CH4: Workloads unable to start 5h 49m ch4.lagoon
Started Nov 16, 2025, 05:32 PM UTC· resolved Nov 16, 2025, 11:21 PM UTC
- investigating Nov 16, 2025, 05:32 PM UTC
New workloads on CH4 are unable to start. Deployments are expected to fail currently.
- investigating Nov 16, 2025, 06:54 PM UTC
We have escalated the issue to the infrastructure provider and are working with them to resolve the issue.
- monitoring Nov 16, 2025, 09:16 PM UTC
We applied a fix which restored all functionality around the starting of workloads and doing deployments.
- resolved Nov 16, 2025, 11:21 PM UTC
This incident has been resolved.