Outage in amazee.io

Changes in un-idling behavior

Resolved Minor
May 13, 2024 - Started over 1 year ago - Lasted about 2 months
Official incident page

Incident Report

Workloads in non-production environments will only be un-idled when a client accessing them can run JavaScript. This change will prevent most cases of undesired un-idling triggered by automated requests. More information on environment idling can be found in the Lagoon documentation https://docs.lagoon.sh/concepts-advanced/environment-idling/.

Need to monitor amazee.io outages?

One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.

Start Free Trial
Latest Updates ( sorted recent to last )
RESOLVED over 1 year ago - at 06/28/2024 02:39PM

This incident has been resolved.

INVESTIGATING over 1 year ago - at 05/13/2024 10:33PM

Workloads in non-production environments will only be un-idled when a client accessing them can run JavaScript. This change will prevent most cases of undesired un-idling triggered by automated requests.

More information on environment idling can be found in the Lagoon documentation https://docs.lagoon.sh/concepts-advanced/environment-idling/.

Latest amazee.io outages

Public statement on CVE-2025-55182 - 21 days ago
Logging partially unavailable - 24 days ago
CH4: Workloads unable to start - about 1 month ago
Logging inaccessible - about 1 month ago
Postgresql CH4 upgrade to 14 - about 2 months ago

Status Aggregator for All Your Third-Party Services

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4600 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook