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 | 100 of 584 (17%) |
Incidents, newest first
Major November 14, 2025 Logging inaccessible 3h 44m Lagoon Logs (OpenSearch)
Started Nov 14, 2025, 07:56 AM UTC· resolved Nov 14, 2025, 11:40 AM UTC
- investigating Nov 14, 2025, 07:56 AM UTC
We are currently investigating this issue.
- identified Nov 14, 2025, 08:18 AM UTC
There was an unexpected rise in load on the logging system. We are now stabilizing the different components.
- resolved Nov 14, 2025, 11:40 AM UTC
This incident has been resolved.
Minor November 3, 2025 Connection interruption for CH4 database 2h 44m ch4.lagoon
Started Nov 03, 2025, 11:27 AM UTC· resolved Nov 03, 2025, 02:11 PM UTC
- investigating Nov 03, 2025, 11:27 AM UTC
We have received multiple reports of connection interruptions when using the production databases on CH4. We are investigating the cause of these interruptions.
- monitoring Nov 03, 2025, 11:44 AM UTC
Since these issues are related to elevated resource usage we are doing an emergency resource increase. We expect a short interruption for existing connection which will help to prevent further disruptions.
- resolved Nov 03, 2025, 02:11 PM UTC
This incident has been resolved.
Major November 3, 2025 Logs access degraded 1d Lagoon Logs (OpenSearch)
Started Nov 03, 2025, 06:24 AM UTC· resolved Nov 04, 2025, 06:46 AM UTC
- investigating Nov 03, 2025, 06:24 AM UTC
We have identified a problem with logs ingestion and access. Engineers are investigating. We will provide an update within the next 90 minutes.
- investigating Nov 03, 2025, 07:52 AM UTC
The logging system is working through a backlog of ingested logs that need to be allocated and indexed. While the backlog is being worked on, more data will become available over time. As the indexing is a resource intensive task, some requests can occasionally result in an error.
- resolved Nov 04, 2025, 06:46 AM UTC
Due to the large backlog of logs, some log messages from 2025-11-01 to 2025-11-03 could not be loaded into the new logging system and had to be dropped. These logs are however still available in the old logging system at https://kibana-legacy.amazeeio.cloud.
Minor October 20, 2025 Limited workload scaling and deployments 4h 27m jp1.lagoon, ca1.lagoon, ie1.lagoon, Deployment Infrastructure and 10 more
Started Oct 20, 2025, 09:34 AM UTC· resolved Oct 20, 2025, 02:02 PM UTC
- 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.
- 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.
- resolved Oct 20, 2025, 02:02 PM UTC
We are no longer seeing workloads affected by this issue.
Critical September 25, 2025 Lagoon API Outage 1h 6m Lagoon API, Lagoon Dashboard
Started Sep 25, 2025, 12:28 AM UTC· resolved Sep 25, 2025, 01:34 AM UTC
- investigating Sep 25, 2025, 12:28 AM UTC
The Lagoon UI and API are currently experiencing an issue, we're investigating.
- monitoring Sep 25, 2025, 01:05 AM UTC
We experienced an issue with image pulls during maintenance that resulted in the prolonged outage. This has been resolved now and we will continue to monitor.
- resolved Sep 25, 2025, 01:34 AM UTC
This incident has been resolved.
Major September 22, 2025 Unresponsive workloads on UK3 3h 15m uk3.lagoon
Started Sep 22, 2025, 11:50 AM UTC· resolved Sep 22, 2025, 03:05 PM UTC
- investigating Sep 22, 2025, 11:50 AM UTC
Some workloads on UK3 are not responding as expected due to high load across a part of the compute infrastructure.
- monitoring Sep 22, 2025, 12:01 PM UTC
The situation has been stabilized and we continue to monitor the system closely
- resolved Sep 22, 2025, 03:05 PM UTC
This incident has been resolved.
Major July 16, 2025 Delayed log processing 17h 56m Lagoon API, Lagoon Logs (OpenSearch)
Started Jul 16, 2025, 02:55 PM UTC· resolved Jul 17, 2025, 08:52 AM UTC
- investigating Jul 16, 2025, 02:55 PM UTC
There is a delay in log processing and recent logs are not available in the logging system. Real time logs can be access through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli
- identified Jul 16, 2025, 04:02 PM UTC
We are rolling out a potential solution which can cause connectivity issues with the Lagoon API.
- monitoring Jul 16, 2025, 04:14 PM UTC
While the logs are being processed the logging system can be unavailable at times.
- monitoring Jul 17, 2025, 04:59 AM UTC
The processing of some older logs is still ongoing.
- resolved Jul 17, 2025, 08:52 AM UTC
The historical logs have been processed and are available in the logging stack.
Notice July 8, 2025 DNS issues 2h 10m Deployment Infrastructure, Nameservers
Started Jul 08, 2025, 11:31 AM UTC· resolved Jul 08, 2025, 01:41 PM UTC
- identified Jul 08, 2025, 11:31 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 08, 2025, 12:24 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 08, 2025, 01:41 PM UTC
During the rollout of enabling DNS-01 challenges in our infrastructure, the image registry was unavailable due to temporary DNS misconfiguration.
Minor June 17, 2025 US2 - slow workload starts 33m us2.lagoon
Started Jun 17, 2025, 02:02 PM UTC· resolved Jun 17, 2025, 02:36 PM UTC
- monitoring Jun 17, 2025, 02:02 PM UTC
Some workloads require more time than expected to start up after the maintenance. We are monitoring the startup processes closely.
- resolved Jun 17, 2025, 02:36 PM UTC
All workloads completed their startup.
Minor June 16, 2025 Degraded performance on UK3 production MySQL databases 5h 7m uk3.lagoon
Started Jun 16, 2025, 04:29 PM UTC· resolved Jun 16, 2025, 09:36 PM UTC
- investigating Jun 16, 2025, 04:29 PM UTC
We are currently investigating this issue.
- identified Jun 16, 2025, 05:23 PM UTC
A failover was preformed on the database to help improve performance, we are monitoring the status.
- monitoring Jun 16, 2025, 05:44 PM UTC
We are monitoring the database performance.
- resolved Jun 16, 2025, 09:36 PM UTC
The incident has been resolved.
Major June 10, 2025 Partially available workloads after maintenance 19h 23m us2.lagoon
Started Jun 10, 2025, 04:39 PM UTC· resolved Jun 11, 2025, 12:03 PM UTC
- investigating Jun 10, 2025, 04:39 PM UTC
After the maintenance on us2, some workloads are only partially available. We are investigating the issue and are working on mitigations to make these workloads available again.
- identified Jun 10, 2025, 05:20 PM UTC
Most workloads are available again. We are continuing the work on a permanent solution.
- monitoring Jun 10, 2025, 09:05 PM UTC
A temporary fix has been implemented and we are closely monitoring the availability of workloads.
- resolved Jun 11, 2025, 12:03 PM UTC
The permanent fix was applied during the extra maintenance.
Major April 24, 2025 Fastly Certificate Error 1h 38m fi2.lagoon, au2.lagoon, us2.lagoon, us3.lagoon and 5 more
Started Apr 24, 2025, 09:46 PM UTC· resolved Apr 24, 2025, 11:24 PM UTC
- investigating Apr 24, 2025, 09:46 PM UTC
We are currently investigating some discrepancies in our Fastly certificate automation. While existing certificates remain unaffected, you may encounter errors during deployment.
- investigating Apr 24, 2025, 10:52 PM UTC
We are continuing to investigate this issue.
- investigating Apr 24, 2025, 11:24 PM UTC
We are continuing to investigate this issue.
- resolved Apr 24, 2025, 11:24 PM UTC
This incident has been resolved.
Minor April 18, 2025 Varying support coverage during holiday season 10d 1h Lagoon API, jp1.lagoon, Deployment Infrastructure, de3.lagoon and 13 more
Started Apr 18, 2025, 07:35 AM UTC· resolved Apr 28, 2025, 09:08 AM UTC
- monitoring Apr 18, 2025, 07:35 AM UTC
From April 18th to April 21st our support coverage varies due to the holiday season. While we monitor the platform as usual, you might experience slower response times on support cases. For critical issues that affect production services, please open a support ticket and call the emergency number noted in your contract.
- monitoring Apr 18, 2025, 07:38 AM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 18, 2025, 07:39 AM UTC
From April 18th to April 21st our support coverage varies due to the holiday season. While we monitor the platform as usual, you might experience slower response times on support cases. For critical issues that affect production services, please open a support ticket and call the emergency number noted in your contract.
- resolved Apr 28, 2025, 09:08 AM UTC
This incident has been resolved.
Minor April 8, 2025 Global docker image registry errors 33m Deployment Infrastructure
Started Apr 08, 2025, 11:03 AM UTC· resolved Apr 08, 2025, 11:36 AM UTC
- investigating Apr 08, 2025, 11:03 AM UTC
We are currently investigating this issue.
- investigating Apr 08, 2025, 11:03 AM UTC
We are continuing to investigate this issue.
- monitoring Apr 08, 2025, 11:18 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 08, 2025, 11:36 AM UTC
This incident has been resolved.
Minor March 13, 2025 Logging partially available 17h 26m Lagoon Logs (OpenSearch)
Started Mar 13, 2025, 02:19 PM UTC· resolved Mar 14, 2025, 07:46 AM UTC
- monitoring Mar 13, 2025, 02:19 PM UTC
We identified a higher than usual load on the logging system and assigned it more resources. The logging system is partially available while it is restarting.
- resolved Mar 14, 2025, 07:46 AM UTC
This incident has been resolved.
Minor February 20, 2025 Volumes in read-only mode 11d 15h us2.lagoon
Started Feb 20, 2025, 05:48 PM UTC· resolved Mar 04, 2025, 09:47 AM UTC
- identified Feb 20, 2025, 05:48 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.
- monitoring Feb 21, 2025, 01:46 PM UTC
We applied a patch that resolves the read-only issue which some workloads experienced.
- resolved Mar 04, 2025, 09:47 AM UTC
With the latest applied patch the issue has been resolved.