Amazee Outage History

Amazee is up right now

There were 8 Amazee outages since February 9, 2026 totaling 1265h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.amazee.io

Minor April 29, 2026

High error rate on Fastly Management API

Detected by Pingoru
Apr 29, 2026, 09:19 AM UTC
Resolved
Apr 29, 2026, 12:51 PM UTC
Duration
3h 31m
Affected: CDN
Timeline · 4 updates
  1. 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.

  2. 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.

  3. monitoring Apr 29, 2026, 11:15 AM UTC

    Fastly resolved the issue with their management API and we'll keep monitoring the situation.

  4. resolved Apr 29, 2026, 12:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 21, 2026

Degraded Performance

Detected by Pingoru
Apr 21, 2026, 12:09 PM UTC
Resolved
Apr 21, 2026, 01:03 PM UTC
Duration
53m
Affected: de3.lagoonuk3.lagoon
Timeline · 2 updates
  1. investigating Apr 21, 2026, 12:09 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 21, 2026, 01:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2026

Post-maintenance Rollout

Detected by Pingoru
Apr 15, 2026, 04:19 AM UTC
Resolved
Apr 15, 2026, 07:24 AM UTC
Duration
3h 5m
Affected: de3.lagoon
Timeline · 3 updates
  1. identified Apr 15, 2026, 04:19 AM UTC

    There was an issue with an EKS rollout during maintenance, we are actively addressing this issue.

  2. monitoring Apr 15, 2026, 06:16 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 15, 2026, 07:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 7, 2026

Increased Build Failures

Detected by Pingoru
Apr 07, 2026, 04:18 PM UTC
Resolved
Apr 08, 2026, 09:54 PM UTC
Duration
1d 5h
Affected: Deployment Infrastructure
Timeline · 3 updates
  1. identified Apr 07, 2026, 04:18 PM UTC

    We have identified an issue causing Lagoon builds to fail and are actively working to resolve.

  2. monitoring Apr 07, 2026, 05:27 PM UTC

    We have applied a fix for this issue and are monitoring deployments.

  3. resolved Apr 08, 2026, 09:54 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Increased Lagoon API error rate

Detected by Pingoru
Mar 18, 2026, 01:41 PM UTC
Resolved
Mar 19, 2026, 02:52 PM UTC
Duration
1d 1h
Affected: Lagoon APILagoon Dashboard
Timeline · 3 updates
  1. investigating Mar 18, 2026, 01:41 PM UTC

    We are investigating increased error rates on the Lagoon API.

  2. identified Mar 19, 2026, 03:27 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Mar 19, 2026, 02:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 17, 2026

Lagoon API slow or degraded

Detected by Pingoru
Mar 17, 2026, 06:42 AM UTC
Resolved
Mar 17, 2026, 08:48 PM UTC
Duration
14h 5m
Affected: Lagoon API
Timeline · 4 updates
  1. investigating Mar 17, 2026, 06:42 AM UTC

    We are currently investigating this issue.

  2. identified Mar 17, 2026, 07:45 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 17, 2026, 07:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 17, 2026, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 18, 2026

Changed processing of HTTP 425 responses in Google Chrome

Detected by Pingoru
Feb 18, 2026, 07:01 AM UTC
Resolved
Apr 08, 2026, 08:10 AM UTC
Duration
49d 1h
Affected: CDN
Timeline · 2 updates
  1. 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#

  2. resolved Apr 08, 2026, 08:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026

Elevated Errors on Fastly level

Detected by Pingoru
Feb 09, 2026, 07:38 PM UTC
Resolved
Feb 10, 2026, 07:52 AM UTC
Duration
12h 13m
Affected: CDN
Timeline · 2 updates
  1. 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/

  2. resolved Feb 10, 2026, 07:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Amazee downtime and outages?

Pingoru polls Amazee's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Amazee reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Amazee alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Amazee for free

5 free monitors · No credit card required