Is Amazee down?

Last checked 2m ago
Current status
Amazee is up

No incidents right now.

Official status page: https://status.amazee.io · Polled every 5 minutes · 29 components tracked

Amazee is operational right now. Last checked 2m ago; the most recent incident resolved 9d ago.

Real-time Amazee status, recent outages, and incident history — pulled directly from Amazee's official status page at https://status.amazee.io every 5 minutes. Pingoru tracks 29 Amazee services and has captured 65 incidents in the last 90 days (97.81% uptime). Get email, Slack, Discord, or webhook alerts the moment Amazee reports a new incident — free for 5 monitors, no credit card.

Users who monitor Amazee also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Amazee uptime 97.81% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 16h 10m
    Started Jun 01, 2026, 02:44 PM UTC · Resolved Jun 02, 2026, 06:54 AM UTC
    EMEA
    Timeline · 2 updates
    • 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.

    Latest: This incident has been resolved.

  2. Resolved 3h 25m
    Started Jun 01, 2026, 02:07 PM UTC · Resolved Jun 01, 2026, 05:33 PM UTC
    Lagoon Logs (Kibana)
    Timeline · 2 updates
    • monitoring · Jun 01, 2026, 02:07 PM UTC

      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 access through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

    • resolved · Jun 01, 2026, 05:33 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 12d 11h
    Started May 20, 2026, 07:26 PM UTC · Resolved Jun 02, 2026, 06:54 AM UTC
    Timeline · 3 updates
    • 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.

    Latest: This incident has been resolved.

  4. Resolved 3h 6m
    Started May 07, 2026, 06:08 PM UTC · Resolved May 07, 2026, 09:14 PM UTC
    jp1.lagoonca1.lagoonie1.lagoonDeployment Infrastructurede3.lagoonfi2.lagoonau2.lagoonus2.lagoonuk3.lagoonus3.lagoon
    Timeline · 3 updates
    • 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.

    Latest: This incident has been resolved.

  5. Resolved 13d 4h
    Started Apr 30, 2026, 01:33 AM UTC · Resolved May 13, 2026, 06:01 AM UTC
    jp1.lagoonca1.lagoonie1.lagoonde3.lagoonfi2.lagoonau2.lagoonus2.lagoonuk3.lagoonus3.lagoonAMER
    Timeline · 2 updates
    • 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.

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

See the full Amazee outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Amazee outage history →

Or sign up free to get alerts when Amazee breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 11 incidents View full outage history →