ScyllaDB Cloud

Affected: Cloud API, SSO & SAML authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-16 08:15 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...

2. identified 2026-07-16 08:16 UTC

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

3. identified 2026-07-16 08:16 UTC

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

4. monitoring 2026-07-16 10:08 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 2026-07-16 10:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 02:53 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...

2. monitoring 2026-05-08 04:23 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...

3. monitoring 2026-05-08 09:56 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...

4. resolved 2026-05-08 18:59 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...

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API, Cloud App

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-15 13:20 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 2025-12-15 14:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API, Cloud App, SSO & SAML authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 11:38 UTC

   We are currently investigating this issue.

2. identified 2025-11-18 11:45 UTC

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

3. identified 2025-11-18 11:46 UTC

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

4. monitoring 2025-11-18 12:14 UTC

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

5. resolved 2025-11-18 13:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API, Cloud App, SSO & SAML authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-29 16:27 UTC

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

2. identified 2025-10-29 16:39 UTC

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

3. resolved 2025-10-29 16:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-07 14:56 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...

2. resolved 2025-07-07 16:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API, Cloud App, SSO & SAML authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-06-12 18:45 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...

2. identified 2025-06-12 18:58 UTC

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

3. resolved 2025-06-12 20:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-06-20 16:06 UTC

   At the moment, we are experiencing issues with creating new clusters.

2. resolved 2024-06-20 18:17 UTC

   This incident has been resolved.

3. postmortem 2024-06-23 11:43 UTC

   The [keyserver.ubuntu.com](http://keyserver.ubuntu.com), a critical service for retrieving GPG keys required during the setup and upgrade processes, was unavailable. This caused failures in the automation scripts that rely on these keys for secure package installations and...

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.

Affected: Cloud API, Cloud App

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-11-28 14:25 UTC

   We found configuration issue facing customers which could lead to the inability to list clusters and other frontend malfunctions. The bug has been identified and a fix is on the way.

2. monitoring 2023-11-28 15:13 UTC

   The patch has been deployed. We are continuing to monitor the status.

3. resolved 2023-11-28 15:45 UTC

   Systems are fully operational. Issue is resolved.

Excerpts are shortened. Read the full incident on ScyllaDB Cloud's status page.