Vendor Status Watch

← all vendors

DataStax status history

Current state: operational — “All Systems Operational” per https://status.astra.datastax.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
4incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:

How long do DataStax incidents last?

3.0 hmedian incident duration27 measured
16.6 h90th percentile1 in 10 ran longer
4.8 hmedian, major/critical only7 incidents

From 27 incidents with a vendor-posted start and resolve time. Longest on record: Classic database creation failure in GCP — 3.9 days (2026-01-24 00:47 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (28)

StartedIncidentStatusImpactDuration
2026-09-01 17:39 UTCNetwork service degredation for databases on us-central1 GCP regionresolvedminor1 h 43 min
2026-08-14 13:55 UTCAstraDB Serverless database creation failures on Azureresolvedminor2 h 22 min
2026-07-30 11:30 UTCData API Service Degradationresolvedminor7 h 49 min
2026-07-22 18:24 UTCAWS - us-east-2 - Degraded performanceresolvednone1 h 53 min
2026-06-16 10:47 UTCLogin issues affecting access to the Astra Web UIresolvedmajor2 h 12 min
2026-06-05 18:33 UTCDatabase creation requests are failing in the AWS us-east 2 regionresolvednone1 h 38 min
2026-05-29 05:55 UTCAzure us west 2: Potential Degraded Performance and Observability Impactresolvedminor17 h 23 min
2026-05-08 07:27 UTCService Performance Degradation in AWS US-EAST-1resolvedminor23 h 42 min
2026-04-16 04:30 UTCmultiple serverless database creation issueresolvedminor1 h 05 min
2026-04-16 03:44 UTCConnection Issue Affecting US East Regionpostmortemnone1 h 50 min
2026-04-07 17:29 UTCDevOps API Issues on Astra DBresolvedminor2 h 59 min
2026-03-23 17:17 UTCAstra Serverless Database Health Dashboard is Unavailableresolvednone2 h 57 min
2026-02-25 05:38 UTCPartial Connectivity Issues in Astra Serverless AWS us-west-2resolvedminor26 min
2026-02-18 12:33 UTCDATA API is Failing on Astra Serverlessresolvedminor13 h 08 min
2026-01-24 00:47 UTCClassic database creation failure in GCPresolvednone3 d 21 h
2026-01-14 17:47 UTCNew Database Creation Astra Managed Clusters Failing in AWSresolvedminor2 h 41 min
2026-01-12 23:14 UTCAstraDB: Service Degradation in aws eu-west-1 Regionresolvedmajor2 h 57 min
2025-11-14 03:30 UTCAstra serverless east1 errorresolvedmajor12 h 12 min
2025-11-13 11:23 UTCElevated API Errors in AWS eu-west-1resolvedmajor4 h 47 min
2025-11-12 05:13 UTCDatabase creation errorsresolvedmajor44 min
2025-11-12 03:36 UTCDataStax Release Notificationresolvedmaintenance26 h 34 min
2025-11-04 08:50 UTCDegraded performance on Astra Serverless databases in AWS us-west-2resolvedminor6 h 13 min
2025-10-20 09:56 UTCDegraded performance due to AWS issues in US-EAST-1 Regionresolvedmajor16 h 33 min
2025-10-14 19:51 UTCDatabase Creation/Expansion Failuresresolvedminor3 h 37 min
2025-10-08 18:21 UTCGCP us-east1: Astra Serverless Query and Connection Failuresresolvedmajor6 h 53 min
2025-09-26 09:14 UTCDatabase creation failingresolvedminor9 h 57 min
2025-09-25 13:48 UTCDatabase creation failingresolvedminor6 h 34 min
2025-09-25 13:11 UTCDatabase creation failingresolvednone2 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch DataStax with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "datastax"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}