Cluvio Outage History

Cluvio is up right now

Pingoru has recorded 34 incidents for Cluvio: 3 in the last 12 months and 1 in the last 90 days.

Source: status.cluvio.com

34incidents recorded
3last 12 months
1last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Cluvio in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202612 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Minor July 27, 2026 Query processing slowdown in US location 43m Cluvio Web Application (US), Query Execution (US)

Started Jul 27, 2026, 01:54 PM UTC· resolved Jul 27, 2026, 02:38 PM UTC

  1. investigating Jul 27, 2026, 01:54 PM UTC

    We are currently investigating an issue where processing SQL queries for reports is slowed down and executions are piling up. We are rolling back the last deployment while we are investigating the issue, the existing reports and dashboards should recover within the next ~10 minutes.

  2. investigating Jul 27, 2026, 01:55 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 27, 2026, 02:12 PM UTC

    The issue has been addressed and query processing is not flowing normally, we continue to monitor the situation.

  4. monitoring Jul 27, 2026, 02:16 PM UTC

    Correcting a typo in the last update: query processing is *now* flowing normally.

  5. resolved Jul 27, 2026, 02:38 PM UTC

    The incident has been resolved.

Read the full incident report →

Major April 9, 2026 Sql Alerts and Dashboard Schedules not running 1h 52m Emails for Sql Alerts and Dashboard Schedules (EU)

Started Apr 09, 2026, 08:32 AM UTC· resolved Apr 09, 2026, 10:24 AM UTC

  1. monitoring Apr 09, 2026, 08:32 AM UTC

    We have identified and mitigated an issue in the EU region where SQL alerts and dashboard schedule emails were not triggered in the time window between Apr/8 2026 15:47 CEST and approximately Apr/9 2026 9:30 CEST. The problem has been resolved and schedules are now running correctly again. We are investigating the root cause of this service interruption and will post an update once we know more.

  2. resolved Apr 09, 2026, 10:24 AM UTC

    We have identified the root cause of the temporary outage of scheduled actions in the EU region: during a deployment, an EC2 instance failed to boot correctly, but was incorrectly reported as healthy by our infrastructure monitoring. We are applying changes to the monitoring of the affected service to ensure incidents of this kind are detected and remediated automatically in the future.

Read the full incident report →

Minor February 10, 2026 Intermittent DNS Resolution issues 11h 12m Cluvio Web Application (EU), Cluvio Web Application (US)

Started Feb 10, 2026, 09:51 PM UTC· resolved Feb 11, 2026, 09:03 AM UTC

  1. identified Feb 10, 2026, 09:51 PM UTC

    We are tracking intermittent issues accessing Cluvio web app and embeds, showing DNS resolution errors. The root cause seems to be ongoing AWS Route53 issue: https://health.aws.amazon.com/health/status We continue to monitor the situation, the impact so far seems to be limited and intermittent.

  2. monitoring Feb 10, 2026, 10:02 PM UTC

    From out server logs we observe only a small fraction of users being impacted. AWS just provided an update on the issue recovery: Feb 10 1:58 PM PST We can confirm significant recovery for the DNS resolution errors for Cloudfront distributions. Customers are still experiencing delays propagating changes to Cloudfront distributions. We continue to work toward full recovery and will provide additional information in the next 30-60 minutes.

  3. monitoring Feb 11, 2026, 09:01 AM UTC

    The issue has been resolved by AWS.

  4. resolved Feb 11, 2026, 09:03 AM UTC

    This incident has been resolved.

Read the full incident report →