DataRobot Outage History
Uptime record, past incidents, and downtime history for DataRobot.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| July 2026 | 88.9% | 9 | 1 |
| June 2026 | 80% | 30 | 6 |
| May 2026 | 77.4% | 31 | 7 |
| April 2026 | 95.2% | 21 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Apr 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
July 2026
Issues with prediction requests against custom model deployments
Started: Jul 2, 1:03 PM
identified
The team root caused the issue causing HTTP 403 responses for Custom Model deployments in EU region. Mitigations were applied and the team is verifying the fix stabilized the service.
Jul 2, 1:20 PM
investigating
We are investigating issues in MTSaaS within EU region impacting prediction requests against Custom Models deployments.
Jul 2, 1:03 PM
May 2026
Batch Jobs queued up in US MTS
Started: May 29, 8:37 AM
monitoring
We are continuing to monitor for any further issues.
May 29, 3:20 PM
monitoring
The remediation script has been deployed and Engineering is actively monitoring the situation. Batch jobs may take longer than usual to show as completed until a permanent fix is rolled out in the next production deployment.
May 29, 2:38 PM
identified
The affected jobs have been resolved and the issue is mitigated. Engineering is actively working on a permanent fix and testing is currently underway
May 29, 10:22 AM
identified
Batch jobs that are currently in the queue are completed successfully; however, their completion status is not being updated correctly. As a temporary workaround, we are manually marking these jobs as completed while we work on implementing a solution.
May 29, 8:37 AM
Delay in Feature Drift Statistics Processing
Started: May 28, 8:30 AM
identified
Feature drift statistics are currently experiencing a processing delay of approximately 1 hour. No data has been lost, and all metrics will reflect accurate values once processing catches up. Our team is actively working to resolve this.
May 28, 9:09 AM
Customers Experiencing Errors with New Custom Model Creation.
Started: May 26, 5:09 AM
monitoring
We are continuing to monitor for any further issues.
May 26, 6:04 AM
monitoring
Engineering has applied a fix in the US SAAS environment which resolved the issue. At the time of issue, some users might have experienced issues with Custom Apps, Data upload and custom model creation. The issue is contained.
May 26, 6:01 AM
investigating
We are experiencing a service interruption with Custom Models functionality in US SAAS environment. Predictions to existing deployments are working fine, but users cannot create new custom models. Engineering is investigating the issue and will provide updates as we make further progress.
May 26, 5:09 AM
Widespread intermittent service issues for new workloads in US Production
Started: May 8, 12:15 AM
monitoring
Engineering resolved the underlying issue with workload scheduling and is monitoring the cluster.
May 8, 1:40 PM
identified
We are continuing to experience issues launching new workloads for Custom Models and Custom Applications in US Production.
This is connected to an ongoing AWS outage. Our team is exploring multiple mitigation options.
May 8, 6:13 AM
identified
We are continuing to experience issues launching new workloads for Custom Models and Custom Applications in US Production.
This is connected to an ongoing AWS outage. Our team is exploring multiple mitigation options.
May 8, 5:47 AM
monitoring
We are currently experiencing intermittent service issues in US Production, which are primarily affecting the launch of new workloads for Notebooks, Custom models, and Custom Applications. This issue does not impact existing workloads. This disruption is strongly correlated with an ongoing AWS Availability Zone outage (https://health.aws.amazon.com/health/status), causing resource allocation failures. The team is actively monitoring the situation and tracking updates from AWS.
May 8, 3:53 AM
April 2026
Delay in processing actual messages
Started: Apr 10, 10:24 AM
monitoring
Processing actual messages on JP MTS is delayed due to autoscaling malfunction.
Engineering scaled up the deployment to alleviate the issue. Root cause mitigation in progress
Apr 10, 10:24 AM
Elevated Errors on Managed AI Cloud
Started: Apr 9, 9:56 PM
monitoring
Engineering has applied changes to mitigate the elevated error rates. Services are now operating normally. We are continuing to monitor the system while investigating the cause of the issue.
Apr 10, 11:31 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 9, 10:56 PM
investigating
We're experiencing an elevated level of errors and are currently looking into the issue.
Apr 9, 9:56 PM
March 2026
Degraded Performance on DataRobot MTS due to Quay outage
Started: Mar 30, 8:43 PM
identified
We are continuing to work on a fix for this issue.
Mar 30, 8:44 PM
identified
Our engineering team has found the the Quay outage currently happening is causing degraded performance across the DataRobot platform. Engineering is currently monitoring the situation.
Mar 30, 8:43 PM
Performance Degradation on Managed AI Cloud
Started: Mar 13, 5:49 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 13, 6:31 PM
investigating
We are experiencing performance degradation on Managed AI Cloud.
Mar 13, 5:49 PM
Intermittent UI disruptions on Managed AI Cloud
Started: Mar 11, 8:05 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 11, 8:22 PM
investigating
We are currently investigating this issue.
Mar 11, 8:05 PM