Is DataStax Astra Down Right Now? Check if there is a current outage ongoing.

We are currently investigating an issue with sporadic read failures in Astra Serverless databases in GCP. This issue is isolated to GCP only.

This incident has been resolved.

A fix has been implemented, and we are observing improvements in database creation. We are actively monitoring the situation.

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

We are currently investigating an issue with database creation in AWS us-east-2 region. No impact on existing databases.

This incident has been resolved.

A fix has been implemented, and we are observing improvements in database creation. We are actively monitoring the situation.

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

We are currently investigating an issue with database creation in AWS us-east-2 region. No impact on existing databases.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

We have identified an issue that affects vector search and SAI queries, and we are working to mitigate and resolve the issue.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be performing maintenance operations.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

We have identified an issue that affects vector search and SAI queries, and we are working to mitigate and resolve the issue.

This incident has been resolved.

We have completed adding additional resources to the region and are monitoring the situation. At this time, all databases should no longer be experiencing impact.

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

We have identified a recurring issue, and a fix is being implemented.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Our investigation is still ongoing and our team continues to work diligently toward resolving the issue.

We are actively working towards a resolution. Our team remains fully engaged, and we’ll share updates as progress is made.

We have identified the issue and are taking mitigating actions

This incident has been resolved. Hibernated databases should now be able to be resumed without issue.

Databases that were hibernated due to inactivity are not resuming correctly. We have identified the issue and are working on a fix. This has no impact on any active databases.

This incident has been resolved.

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

We are currently investigating an issue preventing new Astra Classic databases from being created successfully across all cloud providers. This does not impact our Astra Serverless Vector and Non-Vector databases. There is no impact on existing Astra Classic databases.

This incident has been resolved.

We have uncovered intermittent connection issues In AWS US-East-1 in Astra Serverless DB. We have identified the root cause and are fixing the issue..

This incident has been resolved.

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

We are currently investigating an issue in GCP us-east1 for vector databases. Newly created databases and databases resumed from hibernation are failing to start.

This incident has been resolved.

A fix has been implemented. All database creation should now be working again. We are continuing to monitor at this time.

We are currently investigating an issue where database creation is failing across all clouds and regions. There is no impact on existing databases or traffic to the databases.

This incident has been resolved.

We have identified an issue with CQL Console in the Astra Portal. A fix is expected in 72 hours. In the interim, CQL Console is unavailable. Access to the database for applications is not impacted.

This incident has been resolved.

Currently investigating the issue, health checker is reporting failures.

This incident has been resolved.

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

Newly created databases are experiencing failures. We are currently investigating. This only impacts new databases and not existing databases.

This incident has been resolved.

The system has recovered, and we are actively monitoring to ensure continued stability and performance.

Between February 6, 2025, 02:35:30 UTC and 02:49:30 UTC, some databases in the AWS US East region experienced degraded performance and intermittent errors. The issue has since been mitigated, and databases are now operating normally. We are continuing to investigate the root cause and monitor system stability.

This incident has been resolved.

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

We are currently investigating the issue, authentication is currently impossible for a limited amount of vector databases in AWS us-east-2.

This incident has been resolved.

A fix has been implemented, and we are monitoring the results. If an application is still having trouble sending traffic, please restart the application to re-establish the driver connections.

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

Applications are unable to connect to Astra Serverless databases in AWS south-east-2. We are actively investigating this issue.

This incident has been resolved.

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

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating the issue, but no operations on existing databases are impacted.

This incident has been resolved.

We have identified the root cause and currently rolling out a fix

We are currently investigating an issue with partial request failures on Azure westus3 region

This incident has been resolved.

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

We are currently investigating the issue.

This incident has been resolved.

All databases should be stable. As caches are repopulated, there may still be some residual latency, but availability should not be impacted.

Recovery is in progress, and most databases should be available.

We are currently investigating an issue in AWS us-east-1 causing the Astra Data Services component to crash, resulting in increased latencies, timeouts, or unavailable exceptions.

This incident has been resolved.

We are continuing to monitor for any further issues.

There are some databases still having issues and we are working on resolving the issues

We are continuing to monitor for any further issues.

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

System is on the way to recovery most databases have recovered and we continue to recover the remaining databases

We are continuing to fix the issue and system has started to recover

The issue is identified and a fix is being implement. We will provide an update for resolution projection in next 10 minutes

We are currently investigating this issue.

This incident has been resolved.

A fix is being implemented and we're continuing to monitor. No end-user impact is expected.

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

Intermittent issues creating new non-vector serverless Databases on Azure US East 2. Root cause has been identified and being worked on

This incident has been resolved.

The rollout of a fix is continuing. Performance issues should now be mitigated, and we are actively monitoring the situation.

A solution is being implemented, however, the implementation will continue past the documented maintenance window for Azure US East. An update to this issue is expected within the next 2 hours.

The issue has been identified and we are working with the Azure support team to implement a solution.

We are currently investigating a performance issue in Azure region US East.

This incident has been resolved.

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

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

We have identified a sporadic issue affecting the creation of new databases on AWS. Our team is working on a resolution, and we will provide updates as progress is made.

The issue issue resolved; it occurred from 2024-10-17 at 19:15 to 20:51.

At this time issue should be resolved.

Degraded performance was observed in our GCP us-east1 region, affecting serverless vector database access for some database users and potentially causing timeouts.

We have not observed any further disruptions since the reported AWS issue window between 20:27 UTC and 20:52 UTC on October 7th.

AWS has identified the issue, which lasted from 20:27 UTC to 20:52 UTC on October 7th. We are monitoring our system.

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

We are currently experiencing an elevated error rate affecting Astra databases in the AWS US-East-2 region. This can impact application traffic to databases in this region. For more information, please refer to the AWS status page. If your Astra database is configured with a secondary region, we recommend switching traffic to that region to minimize disruption. https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-2::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_67084_0A6A325AD2F

We have deployed a fix for the issue affecting Private Service Connect (GCP) and Private Link (AWS/Azure) configurations when terminating databases. You can now safely terminate databases without impacting private link connectivity.

We have identified a problem related to terminating Serverless and Classic databases that are configured with Private Service Connect (GCP) or Private Link (AWS/Azure) and are sharing the connection with another database. When one of the databases sharing the Private Link/Private Serve Connect is terminated, it causes the associated Private Service Connect or Private Link configurations to be deleted even though the connection is in use by another database. Do not terminate your database if you are sharing a Private Link/Private Serve Connect across databases. We are currently working on a fix for this issue.

This incident has been resolved.

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

We currently investigating degraded performance for some of the databases in AWS region US-West-2. Application clients may be experiencing errors and / or increase in query latencies.

Degraded performance was observed in our GCP Asia-Northeast1 region, affecting serverless database access for some users with potential timeouts. The issue has been resolved, and the impact period was from 19:18 UTC to 19:33 UTC on Sep 13th.

This incident has been resolved.

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

We are starting an emergency maintenance in the Canada Central Azure region.

The emergency maintenance has been completed in the Australia East Azure region.

We are starting an emergency maintenance in the Australia East Azure region.

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

We are currently investigating an issue creating databases and keyspaces in Azure in Canada Central and Australia East regions. The traffic to existing databases remains unaffected.

We are no longer seeing any impact and confirm that all databases are fully operational. We will continue to monitor the Azure status.

Based on the recent Azure's Status Page recommendation for Central US issue (as of 23:45 UTC on 18 July 2024), DataStax recommends customers with Astra DB in Central US with multi-region setup to initiate failover to the other regions.

We are continuing to monitor for any further issues.

Azure has an outage in US Central Region as indicated in Azure Status Page - https://azure.status.microsoft/en-us/status. As a consequence Astra Serverless Databases in this region are also impacted. We are closely monitoring the status of the issue in Azure and will ensure Astra Serverless database services are restored as soon as the Azure issue is resolved.

The issue has been resolved.

We are currently investigating the issue and working towards resolution.

This incident has been resolved. If any databases failed to be created during this window, please retry the creation workflow.

We are seeing intermittent issues creating new databases. Connectivity and interactions with existing databases are not impacted.

This incident has been resolved.

We are continuing to investigate this issue.

We are seeing intermittent issues creating new database. Connectivity to existing database should not be impacted.

This incident is resolved. Note: The incident was accidentally titled incorrectly. It's been updated to reflect an accurate description of the incident. There was no issue observed with elevated API errors as the original title suggested.

Issue has been resolved. Latencies should now be normal for customers that may have experienced them. We are monitoring our services before we mark this "resolved"

We are currently investigating possible increases in latency on the us-west-2 AWS region. Some customers may experience elevated latency. We are monitoring for any change and investigating the issue further.

This incident has been resolved.

Some customers may have experienced latency on the us-east-1 cluster. Latency issues are no longer being observed, and we continue to monitor the issue.

This incident has been resolved.

We are currently investigating the issue, currently Vector databases in AWS are affected. Traffic normal, but authentication may be impacted.

This incident has been resolved.

We are continuing to investigate this issue.

At this time Vector databases are impacted.

This incident has been resolved. Accurate reporting is restored for affected databases. The operation of databases and the data stored on these databases are unaffected by this incident.

We have applied the fix and are monitoring to ensure the issue is resolved.

Issue has been identified and mitigation steps are in progress. Databases are still healthy and data is unaffected.

We are continuing to investigate this issue.

Currently investigating an issue with metrics in health dashboards for some databases in the AWS us-east-1 region. This degredation will also be visible in external metrics in this region. Databases are healthy; there is no impact to serverless resources or data stored in these databases.

This incident has been resolved.

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

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

We are investigating a new and similar performance issue with the Astra Portal. Users may notice slowness during login or occasional timeout. There is no impact to the connectivity to the databases or the performance of the databases.

This incident has been resolved.

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

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

We are investigating a performance issue with the Astra Portal. Users may notice slowness during login or occasional timeout. There is no impact to the connectivity to the databases or the performance of the databases.

The incident has been resolved. If you are encountering issues with your metrics, please reach out to our support team!

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

We have initiated the rollout of fixes. We will continue to provide details here.

The health dashboards are slow to load the graphs. We have identified the root cause and in the process of the resolving the issue. There is no impact on the database operations or performance.

This incident has been resolved.

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

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

We have identified an issue with observability metrics availability that impacts dashboards and Third Party Metrics. We are working to resolve this issue.

The issue has been resolved and we are able to access data again using the Data_API

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

We are continuing to investigate the issue with Vector Databases having issues accessing data using the Data_API. The Region affected are as follows: AWS: * eu-west-1 * us-east-1 * us-east-2 Azure: * Centralindia * westus3 GCP: * us-east1

Following regions for Vector may be affected aws eu-west-1 aws us-east-1 azure centralindia aws us-east-2 azure westus3 gcp us-east1

We are currently investigating this issue.

This incident has been resolved.

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

An issue has been identified as a possible underlying cause. Measures are underway to resolve the issue.

We are currently aware of an issue accessing the CQL console on Astra Vector Databases from the UI, and we are actively investigating a root cause. At this time, the standalone CQL shell appears to be unaffected.

This incident is resolved, accounts.datastax.com is now reachable

We are currently investigating the issue, databases are accessible only sign ups and login to admin is impacted

This incident has been resolved.

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

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

We are currently experiencing an issue affecting classic database creation across all regions and cloud providers. Our team has identified the cause and is actively working on implementing a solution. Thank you for your patience and understanding as we diligently strive to reinstate the creation of classic databases. If you have any concerns or require assistance, please reach out to our support team.

This incident has been resolved.

We have identified an issue with Astra that is affecting following operations : Create / Terminate Database Add / Remove a Region Resize Database (Astra Classic) Park / Unpark Database (Astra Classic) Enable Third party Metrics There may be a delay observed in processing these operations. Read / Write operations on the existing databases are not impacted. We have identified a fix and it is being rolled out.

We have resolved this issue. All database now show the correct status.

We have identified the issue and now working on restoring status to the correct status for all existing databases.

All active databases are operational and there is no impact to customer's applications. Astra Portal erroneously shows status as Unknown. As a result Astra Portal users are not able to see metrics and run CQL console.

This incident has been resolved.

Backup functionality has been restored and we are monitoring the situation.

Commitlog replay functionality has been fully restored. No data has been lost and consistency should be restored for all affected databases. We are working on restoring the hourly backup service now.

The workaround has been applied successfully. We are working on restoring the normal operations now. This should be completed within the next hour.

We are continuing work on the resolution.

We identified the root cause of the issues and are working on a resolution.

We are currently having issues with our snapshotting and replaying mechanisms on Vector databases in GCP. Consequently, some databases may currently face temporary data inconsistencies and may be without regular backups. We are investigating this issue.