Amazee had 39 outages in the last 2 years totaling 1270h 12m of downtime — averaging 1.6 incidents per month.
There were 39 Amazee outages since September 10, 2024 totaling 1270h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some workloads require more time than expected to start up after the maintenance. We are monitoring the startup processes closely.
All workloads completed their startup.
We are currently investigating this issue.
A failover was preformed on the database to help improve performance, we are monitoring the status.
We are monitoring the database performance.
The incident has been resolved.
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.
Most workloads are available again. We are continuing the work on a permanent solution.
A temporary fix has been implemented and we are closely monitoring the availability of workloads.
The permanent fix was applied during the extra maintenance.
We are currently investigating some discrepancies in our Fastly certificate automation. While existing certificates remain unaffected, you may encounter errors during deployment.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.
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.
We are continuing to monitor for any further issues.
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.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
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.
We applied a patch that resolves the read-only issue which some workloads experienced.
With the latest applied patch the issue has been resolved.
Some image builds on DE3 are timing out due to an issue with the build cache. We are working on a solution.
The caching issue has been resolved and image builds are fully operational.
We are monitoring updates from Atlassian for JSM Cloud customers concerning a sync issue with Assist, you might experience delays awaiting responses from our Support team.
The issue has been resolved by Atlassian.
Logs might not appear in the logging system as quick as usual due to a larger backlog that is currently being processed. Real time logs through the Lagoon CLI (https://docs.amazee.io/cloud/logging/#real-time-logs-via-lagoon-cli) are not affected by this.
The backlog of logs was processed completely and logs are showing up as usual in the logging system.
Hello Team! We are upgrading Mysql 8 from Mysql5.7. We expect limited downtime during maintenance window.
This incident has been resolved.
Customers with valid certificates are not impacted only newly issued certificates seem to take longer than usual to load the certificate onto the route. If you see immediate issues please get in touch with Support.
A fix has been implemented and we are monitoring the results.
New certificates are again issued without any delays.
We are currently investigating this issue.
A database failover was executed to resolve the performance issue and we are monitoring the situation.
This incident has been resolved.