Vendor Status Watch

← all vendors

Datarobot status history

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

1incidents, last 30 days
3incidents, last 90 days
31incidents on record
Incidents per week, last 12 weeks:

How long do Datarobot incidents last?

84 minmedian incident duration31 measured
36.4 h90th percentile1 in 10 ran longer
8.8 hmedian, major/critical only8 incidents

From 31 incidents with a vendor-posted start and resolve time. Longest on record: Problem connecting to DataRobot due to client browser caching — 13.8 days (2026-01-08 18:15 UTC). Excluded, never estimated: nothing. 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 (31)

StartedIncidentStatusImpactDuration
2026-08-18 12:20 UTCCodespace Session Validation Failure in Generative AI Playgroundresolvedminor2 h 24 min
2026-07-24 17:32 UTCIssues with Vector Database Creationresolvedminor1 h 10 min
2026-07-02 13:03 UTCIssues with prediction requests against custom model deploymentsresolvedminor34 min
2026-05-29 08:37 UTCBatch Jobs queued up in US MTSresolvedminor5 d 0 h
2026-05-28 08:30 UTCDelay in Feature Drift Statistics Processingresolvedminor1 h 17 min
2026-05-26 05:09 UTCCustomers Experiencing Errors with New Custom Model Creation.resolvedminor1 h 09 min
2026-05-08 00:15 UTCWidespread intermittent service issues for new workloads in US Productionresolvedminor20 h 05 min
2026-04-10 10:24 UTCDelay in processing actual messagesresolvedminor36 min
2026-04-09 21:56 UTCElevated Errors on Managed AI Cloudresolvedmajor15 h 07 min
2026-03-30 20:43 UTCDegraded Performance on DataRobot MTS due to Quay outageresolvedminor12 h 10 min
2026-03-13 17:49 UTCPerformance Degradation on Managed AI Cloudresolvedminor54 min
2026-03-11 20:05 UTCIntermittent UI disruptions on Managed AI Cloudresolvedminor5 d 22 h
2026-03-11 14:36 UTCNetwork issue related to Kubernetes in US clusterresolvedmajor2 h 05 min
2026-02-18 21:04 UTCDegraded Performance on the DataRobot MTS due to Quay outageresolvedminor15 min
2026-02-17 15:48 UTCLLM blueprints deployments cannot be createdresolvedmajor7 min
2026-02-16 11:35 UTCAgent Application Template Impacted After Moderations Library Upgrade.resolvedminor1 h 13 min
2026-02-13 20:39 UTCDegraded Performance on the DataRobot US MTSresolvedminor52 min
2026-01-08 18:15 UTCProblem connecting to DataRobot due to client browser cachingresolvedcritical13 d 20 h
2025-12-17 17:00 UTCDegraded Platform Performance Due to Docker Hub Outageresolvedminor0 min
2025-12-05 11:09 UTCDegraded Platform Performance Due to Docker Hub Outageresolvedminor25 min
2025-11-26 07:17 UTCSome Users Facing Issues In Accessing Notebooks/Codespaces in US/EU/JP MTS.resolvedmajor25 h 08 min
2025-11-20 06:52 UTCSome Users Are Unable To Login Into US,EU & JP MTS clusters.resolvedmajor30 min
2025-11-07 07:14 UTCThe AutoML experiment creation workflow and visibility of certain tabs impacted in MTS environmentsresolvedminor4 h 35 min
2025-11-06 12:38 UTCNotebooks are timing out occasionally on US Production.resolvedminor23 h 59 min
2025-11-04 13:57 UTCData Connectors Hanging on Creationresolvedminor35 min
2025-10-22 13:16 UTCTemporary Access Issue for Org Admins to Custom Applicationsresolvedminor1 h 24 min
2025-10-20 09:49 UTCAWS services outage affects STS and MTS DataRobot environmentsresolvedminor12 h 22 min
2025-10-01 09:40 UTCUI Issue Affecting Model Visibility and Project Managementresolvedminor8 h 24 min
2025-09-25 01:19 UTCIssue With DockerHub Services Impacting MTS & STS DataRobot Clusters.resolvedminor37 min
2025-09-09 05:39 UTCUsers in APAC region are experiencing network issues when accessing application endpoints in US MTSresolvedmajor36 h 24 min
2025-09-02 15:37 UTCServerless Prediction Servers are impacted when an a new deployment is created or an existing deployment is modified.resolvedmajor2 h 30 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 Datarobot with the template

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

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