ScyllaDB Outage History

ScyllaDB is up right now

Pingoru has recorded 9 incidents for ScyllaDB: 5 in the last 12 months and 0 in the last 90 days.

Source: status.cloud.scylladb.com

9incidents recorded
5last 12 months
0last 90 days
4 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking ScyllaDB 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 202600 of 720 (0%)
May 2026116 of 744 (2%)
June 202600 of 720 (0%)
July 202612 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 508 (0%)

Incidents, newest first

Minor July 16, 2026 ScyllaDB Cloud Portal Unavailable Due to Third-Party SSO Provider Incident 1h 54m Cloud API, SSO & SAML authentication

Started Jul 16, 2026, 08:15 AM UTC· resolved Jul 16, 2026, 10:09 AM UTC

  1. investigating Jul 16, 2026, 08:15 AM UTC

    We are investigating an issue preventing users from accessing the ScyllaDB Cloud web portal. The impact is caused by an ongoing incident at our third-party identity and SSO provider, Frontegg. ScyllaDB Cloud databases and data-plane operations remain unaffected; however, portal login and management functions are currently unavailable. We are monitoring Frontegg’s recovery efforts and will provide an update as soon as more information is available. For details from the provider, please see the Frontegg incident status.

  2. identified Jul 16, 2026, 08:16 AM UTC

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

  3. identified Jul 16, 2026, 08:16 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jul 16, 2026, 10:08 AM UTC

    Access to the ScyllaDB Cloud portal has been restored, and the service is operating normally. The underlying incident at our third-party SSO provider, Frontegg, remains active. We will continue to monitor their status and provide further updates if needed.

  5. resolved Jul 16, 2026, 10:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026 Operational issue - AWS Availability Zone (use1-az4). 16h 6m

Started May 08, 2026, 02:53 AM UTC· resolved May 08, 2026, 06:59 PM UTC

  1. investigating May 08, 2026, 02:53 AM UTC

    We are currently experiencing elevated provisioning times and limited impact to some clusters hosted in AWS US-EAST-1 due to an ongoing infrastructure incident affecting a single AWS Availability Zone (use1-az4). AWS has identified the issue as a thermal/power event impacting EC2 and EBS resources in that zone. Our team is actively monitoring the situation and AWS has shifted traffic away from the affected infrastructure. Other Availability Zones remain operational and unaffected. We will continue to provide updates as more information becomes available.

  2. monitoring May 08, 2026, 04:23 AM UTC

    We continue to monitor the AWS US-EAST-1 Availability Zone incident. As a proactive measure, we are replacing a small number of affected nodes in several clusters. At this time, we are not observing any data loss, performance degradation, or customer impact. Cluster operations remain stable, and our team is actively overseeing recovery activities.

  3. monitoring May 08, 2026, 09:56 AM UTC

    The AWS US-EAST-1 Availability Zone incident remains ongoing on the AWS side, however at this time we do not observe any new issues affecting Scylla Cloud operations. All affected clusters have been handled and Scylla Cloud services are operating normally. Customers whose clusters were impacted will receive additional details and follow-up communication through Zendesk. While the incident is considered resolved from the Scylla Cloud perspective, we continue to monitor the AWS situation closely and will provide further updates if needed.

  4. resolved May 08, 2026, 06:59 PM UTC

    The incident related to the AWS US-EAST-1 Availability Zone disruption has been resolved from the Scylla Cloud side, and all services are operating normally. If your cluster was impacted in any way, you will receive additional details through a Zendesk notification. Please note that AWS continues to work on resolving related infrastructure issues within the affected Availability Zone, and additional AWS service updates may still occur while their incident remains ongoing. Have a great weekend, ScyllaDB Cloud Team

Read the full incident report →

Major December 15, 2025 Scylla Cloud Partial Outage 1h 20m Cloud API, Cloud App

Started Dec 15, 2025, 01:20 PM UTC· resolved Dec 15, 2025, 02:41 PM UTC

  1. identified Dec 15, 2025, 01:20 PM UTC

    Customers cannot perform actions on the clusters that involve async operations. e.g: bootstrap, resizes etc. The issue has been identified and a fix is implemented.

  2. resolved Dec 15, 2025, 02:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025 ScyllaDB Cloud Portal Availability issues 1h 49m Cloud API, Cloud App, SSO & SAML authentication

Started Nov 18, 2025, 11:38 AM UTC· resolved Nov 18, 2025, 01:28 PM UTC

  1. investigating Nov 18, 2025, 11:38 AM UTC

    We are currently investigating this issue.

  2. identified Nov 18, 2025, 11:45 AM UTC

    We are currently investigating reports of elevated errors originated by our WAF provider Cloudflare.

  3. identified Nov 18, 2025, 11:46 AM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Nov 18, 2025, 12:14 PM UTC

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

  5. resolved Nov 18, 2025, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 29, 2025 Login issues 19m Cloud API, Cloud App, SSO & SAML authentication

Started Oct 29, 2025, 04:27 PM UTC· resolved Oct 29, 2025, 04:47 PM UTC

  1. identified Oct 29, 2025, 04:27 PM UTC

    The issue has been identified and a fix is being implemented on our CDN provider.

  2. identified Oct 29, 2025, 04:39 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 29, 2025, 04:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 7, 2025 Partial Service Disruption — Self-Service Scale-Out/In Unavailable 1h 31m Cloud API

Started Jul 07, 2025, 02:56 PM UTC· resolved Jul 07, 2025, 04:28 PM UTC

  1. investigating Jul 07, 2025, 02:56 PM UTC

    Impact: We are currently experiencing an issue with the self-service scale-out/in feature in our ScyllaDB DBaaS platform. Customers attempting to scale out/in their clusters via the dashboard or API may see failures or no effect. Workaround: Our team can assist with scaling out / in your cluster manually during this time. Please contact support if you need to scale your cluster urgently. Status: We are actively investigating and working on a fix. We will provide updates as progress is made.

  2. resolved Jul 07, 2025, 04:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025 Issues Affecting Monitoring 2h Cloud API, Cloud App, SSO & SAML authentication

Started Jun 12, 2025, 06:45 PM UTC· resolved Jun 12, 2025, 08:45 PM UTC

  1. identified Jun 12, 2025, 06:57 PM UTC

    We are currently investigating issues affecting access to ScyllaDB Monitoring and the ScyllaDB Cloud Portal. Please note that there is no impact to clusters running on ScyllaDB Cloud. We will provide updates as they become available. The issue appears to be related to broader internet connectivity problems, potentially involving Cloudflare. We are beginning to receive reports that access is starting to improve or has been restored.

  2. identified Jun 12, 2025, 06:58 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Jun 12, 2025, 09:02 PM UTC

    This incident has been resolved.

Read the full incident report →