DataRobot

Affected: Website, Website, Website, API, API, API, Predictions, Predictions, Prediction, AutoML, AutoML, AutoML, AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Apps, AI Apps, AI Apps, MLOps, MLOps, MLOps, Pipeline, Generative AI LLM Playground, Notebooks, Generative AI VDB Builder, Generative AI LLM Playground, Notebooks, Generative AI VDB Builder, Generative AI LLM Playground, Generative AI VDB Builder

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-18 12:20 UTC

   Codespace session in the Generative AI Playground fails due to a validation error. Engineering is working on creating a fix.

2. identified 2026-08-18 13:56 UTC

   Engineering has implemented a fix and is currently working on deploying it across the Production clusters.

3. resolved 2026-08-18 14:44 UTC

   The fix is now deployed to all the Prod environments and Generative AI Playground is now working as expected.

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

Affected: Generative AI VDB Builder, Generative AI VDB Builder, Generative AI VDB Builder

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-24 17:32 UTC

   The DataRobot Engineering team observed issues while creating a DataRobot hosted Vector Database. Currently, this is affecting all the DataRobot MTS environments and engineering is investigating the root cause.

2. monitoring 2026-07-24 17:44 UTC

   Engineering team has applied the fix and Vector Database creation is operational now. The team is monitoring the situation.

3. resolved 2026-07-24 18:42 UTC

   Engineering team observed that the Vector Database creation is operational across all DataRobot MTS environments. The incident is Resolved.

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

Affected: Website, API, Predictions, AutoML, AI Catalog and Data Ingest, AI Apps, MLOps, Generative AI LLM Playground, Generative AI VDB Builder

Failure mode: Login, tokens, certificates or credentials 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 2026-07-02 13:03 UTC

   We are investigating issues in MTSaaS within EU region impacting prediction requests against Custom Models deployments.

2. identified 2026-07-02 13:20 UTC

   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.

3. resolved 2026-07-02 13:37 UTC

   The issue is contained and the team has verified that predictions against Custom Models in all MTSaaS environments are healthy.

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

Affected: Website, API, Predictions, AutoML, AI Catalog and Data Ingest, AI Apps, MLOps, Pipeline, Notebooks, Generative AI LLM Playground, Generative AI VDB Builder

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-29 08:37 UTC

   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.

2. identified 2026-05-29 10:22 UTC

   The affected jobs have been resolved and the issue is mitigated. Engineering is actively working on a permanent fix and testing is currently underway

3. monitoring 2026-05-29 14:38 UTC

   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.

4. monitoring 2026-05-29 15:20 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-06-03 09:29 UTC

   A fix has been deployed to production and the issue is now resolved. All systems are operating normally.

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

Affected: MLOps

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-28 08:30 UTC

   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.

2. resolved 2026-05-28 09:47 UTC

   Feature drift statistics processing has been restored to normal. All metrics are now up to date. No data was lost.

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

Affected: API, AutoML, AI Catalog and Data Ingest

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 05:09 UTC

   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...

2. monitoring 2026-05-26 06:01 UTC

   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.

3. monitoring 2026-05-26 06:04 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-05-26 06:18 UTC

   Custom Models, Custom Applications & Data upload services are back to Operational state in US SAAS Environment. Issue is Resolved.

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

Affected: AI Apps, MLOps, Notebooks

Failure mode: A zone, region or data center became unavailable. 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: AWS.

1. monitoring 2026-05-08 00:15 UTC

   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...

2. identified 2026-05-08 05:30 UTC

   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.

3. identified 2026-05-08 05:45 UTC

   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.

4. monitoring 2026-05-08 13:40 UTC

   Engineering resolved the underlying issue with workload scheduling and is monitoring the cluster.

5. resolved 2026-05-08 20:21 UTC

   Engineering confirmed the issue is resolved and all services are restored.

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

Affected: MLOps

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-10 10:24 UTC

   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

2. resolved 2026-04-10 11:01 UTC

   Engineering has applied the required infrastructure configuration changes. The service is operating normally and no further user impact is observed. Engineering will continue monitoring cluster health to ensure stability. The incident is now marked as Contained.

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

Affected: AI Apps, Notebooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 21:56 UTC

   We're experiencing an elevated level of errors and are currently looking into the issue.

2. monitoring 2026-04-09 22:56 UTC

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

3. monitoring 2026-04-10 11:31 UTC

   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.

4. resolved 2026-04-10 13:04 UTC

   Engineering has implemented the required fixes to resolve the elevated error rates. Services are now operating normally, and no further user impact has been observed. The team will continue to monitor the system to ensure stability. The incident is now considered contained.

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

Affected: Website, Website, Website, API, API, API, Predictions, Predictions, Prediction, AutoML, AutoML, AutoML, AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Apps, AI Apps, AI Apps, MLOps, MLOps, MLOps, Pipeline, Generative AI LLM Playground, Notebooks, Generative AI VDB Builder, Generative AI LLM Playground, Notebooks, Generative AI VDB Builder, Generative AI LLM Playground, Generative AI VDB Builder

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. identified 2026-03-30 20:43 UTC

   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.

2. identified 2026-03-30 20:44 UTC

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

3. resolved 2026-03-31 08:53 UTC

   Quay.io functionality has been restored and DataRobot environments are fully stabilized.

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

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-13 17:49 UTC

   We are experiencing performance degradation on Managed AI Cloud.

2. monitoring 2026-03-13 18:31 UTC

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

3. resolved 2026-03-13 18:43 UTC

   This incident has been resolved.

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

Affected: Website, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-11 20:05 UTC

   We are currently investigating this issue.

2. monitoring 2026-03-11 20:22 UTC

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

3. monitoring 2026-03-17 18:31 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-03-17 18:32 UTC

   This incident has been resolved.

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

Affected: Predictions, MLOps, Pipeline

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-11 14:36 UTC

   DataRobot is experiencing network issue related to Kubernetes in US Cluster. This will have impact on model deployment and predictions. Engineering is investigating the root cause.

2. identified 2026-03-11 15:06 UTC

   Engineering has identified the root cause of the problem and a mitigation is put in place.

3. monitoring 2026-03-11 15:19 UTC

   The mitigation implemented by Engineering has improved the network issue. The team is continuing to monitor the environment to ensure full recovery.

4. resolved 2026-03-11 16:41 UTC

   The mitigation implemented by Engineering has resolved the Kubernetes network issue, and the incident is now contained.

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

Affected: Website, Website, Website, API, API, API, Predictions, Predictions, Prediction, AutoML, AutoML, AutoML, AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Apps, AI Apps, AI Apps, MLOps, MLOps, MLOps, Pipeline, Generative AI LLM Playground, Notebooks, Generative AI VDB Builder, Generative AI LLM Playground, Notebooks, Generative AI VDB Builder, Generative AI LLM Playground, Generative AI VDB Builder

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-02-18 21:04 UTC

   Our engineering team has found the the Quay outage currently happening is causing degraded performance across the DataRobot platform.

2. resolved 2026-02-18 21:19 UTC

   This incident is now resolved.

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

Affected: Generative AI LLM Playground

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-17 15:48 UTC

   LLM blueprints deployments can not be created in JP MTS environment. Engineering is rolling back JP cluster to previous version to mitigate the issue.

2. resolved 2026-02-17 15:55 UTC

   Rollback of the JP cluster to the previous version is complete and the problem has been mitigated.

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

Affected: AI Apps, AI Apps, AI Apps

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-16 11:35 UTC

   Agent application template is affected with the recent moderations library upgrade, fix is identified and mitigation is in progress.

2. resolved 2026-02-16 12:49 UTC

   New version of Agentic application template is released, the issue is resolved

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

Affected: API, AI Catalog and Data Ingest

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-13 20:39 UTC

   We are observing issues on DataRobot US MTS environment. Users may experience degraded performance using APIs and data ingest services. The engineering team is currently investigating the root cause.

2. resolved 2026-02-13 21:31 UTC

   The incident has now been resolved. All services are now operational.

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

Affected: Website, Website, Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-01-08 18:15 UTC

   Some customers have reported issue connecting to DataRobot. Please do a hard refresh of your browser by clearing the cache and this should fix the problem. As always let us know if it continue to have issue connecting to DataRobot after clearing the cache.

2. monitoring 2026-01-08 18:16 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-01-22 14:19 UTC

   This incident has been resolved.

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

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. resolved 2025-12-17 17:00 UTC

   Between 16:50 UTC and 17:09 UTC, one of external providers(DockerHub) had an outage that might have caused temporary delays in starting platform workloads. The issue has been resolved and normal operations have resumed. Engineering is continuing to monitor the system.

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

Affected: Predictions, Predictions, Prediction, Predictions, MLOps, MLOps, MLOps, MLOps

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. monitoring 2025-12-05 11:09 UTC

   Between 09:04 UTC and 09:17 UTC, one of external providers(DockerHub) had an outage that might have caused temporary delays in starting platform workloads. The issue has been resolved and normal operations have resumed. Engineering is continuing to monitor the system.

2. resolved 2025-12-05 11:35 UTC

   The engineering team has confirmed recovery across all MTS and STS environments. No further updates are expected.

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

Affected: Notebooks, Notebooks

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-26 07:17 UTC

   Some Users with GenAI licensing are facing issues in accessing Notebooks/Codespaces. Engineering team is checking into it.

2. identified 2025-11-26 10:30 UTC

   Engineering team has identified the issue and hotfix is being applied to all MTS envs

3. identified 2025-11-26 13:28 UTC

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

4. identified 2025-11-26 13:30 UTC

   Engineering team has verified that the fix has been applied to JP MTS production environment and Non GenAI users are now able to access notebooks in JP cluster. We are now applying the hotfix to US and EU clusters.

5. identified 2025-11-26 14:04 UTC

   Engineering team has verified that the fix has been applied to JP MTS production environment and Non GenAI users are now able to access notebooks in JP cluster. We are now applying the hotfix to US and EU clusters. The mitigation for Self Managed and STS deployments is in...

6. identified 2025-11-26 19:26 UTC

   Our team has deployed a fix for the issue. All the MTS environments are currently operational.

7. resolved 2025-11-27 08:26 UTC

   This incident has been resolved.

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

Affected: Website, Website, Website

Failure mode: Login, tokens, certificates or credentials 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-11-20 06:52 UTC

   Engineering is investigating reports of some users not being able to login in US,EU & JP MTS clusters. Please contact support@datarobot.com if you have any questions.

2. resolved 2025-11-20 07:23 UTC

   The issue is fixed. Access to the US, EU, and JP clusters is restored.

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

Affected: Website, Website, Website, AutoML, AutoML, AutoML

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-07 07:14 UTC

   The AutoML experiment creation workflow and the visibility of certain tabs in both the Classic and NextGen UIs are currently impacted for the customers with GenAI license. Engineering is actively investigating the issue.

2. resolved 2025-11-07 11:50 UTC

   The issue has been resolved.

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

Affected: Notebooks

Failure mode: The text does not say enough to tell. 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-11-06 12:38 UTC

   Notebooks are timing out occasionally on US Production, engineering team is investigating the issue.

2. monitoring 2025-11-06 13:02 UTC

   The issue of Notebooks timing out is not reproducible on US Prod. Engineering is monitoring the service and investigating the root cause.

3. resolved 2025-11-07 12:37 UTC

   The Engineering team hasn't observed any new occurrences during monitoring. All services remain fully operational.

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

Affected: AI Catalog and Data Ingest, AI Catalog and Data Ingest, AI Catalog and Data Ingest

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-04 13:57 UTC

   Users in MTS Production are not able to create new Data Connections, the process times out and Data Connection cannot be saved. The issue was reported for Snowflake connection, however other connections may be affected too. The Engineering team is actively investigating the...

2. resolved 2025-11-04 14:32 UTC

   The Engineering team has successfully resolved the connection and processing timeouts affecting data operations in MTS Production. Services are now running stable.

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

Affected: AI Apps, AI Apps, AI Apps

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-22 13:16 UTC

   After the recent permission update, Org Admins temporarily lost access to Custom Applications. A fix is being deployed and should be completed within 6 hours.

2. identified 2025-10-22 14:40 UTC

   The hotfix has been applied and access for Org Admins to Custom Applications has been restored.

3. resolved 2025-10-22 14:40 UTC

   This incident has been resolved.

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

Affected: Website, Website, API, API, Predictions, AI Catalog and Data Ingest, AutoML, Generative AI LLM Playground, AI Catalog and Data Ingest, Generative AI VDB Builder, AI Apps, MLOps, Pipeline, Notebooks, Generative AI LLM Playground, Generative AI VDB Builder

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: AWS.

1. investigating 2025-10-20 09:49 UTC

   Due to on-going AWS outage in us-east-1 region overall functionality of MTS and STS is affected. Users will experience degraded performance and intermittent connectivity issues. Engineering team is in contact with AWS team to find a resolution.

2. investigating 2025-10-20 10:01 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-20 10:02 UTC

   We are continuing to investigate this issue.

4. investigating 2025-10-20 10:03 UTC

   We are continuing to investigate this issue.

5. monitoring 2025-10-20 10:03 UTC

   Overall functionality of DataRobot is recovering. Engineering team is actively monitoring the services to ensure continued stability.

6. monitoring 2025-10-20 13:57 UTC

   We are continuing to monitor for any further issues.

7. resolved 2025-10-20 22:11 UTC

   This incident has been resolved. AWS is reporting systems as operational. Engineering will continue to monitor the situation.

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

Affected: AutoML, AutoML, AutoML

Failure mode: Login, tokens, certificates or credentials 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-10-01 09:40 UTC

   We’ve identified an issue causing limited access to Projects in Classic UI for customers with GenAI Builder seat license assigned. The Engineering team is working on a fix.

2. identified 2025-10-01 13:14 UTC

   The Engineering team has released and validated the fix on JP AI Cloud. Deployment to EU and US AI Clouds is in progress.

3. identified 2025-10-01 14:58 UTC

   The Engineering team has released and validated the fix on EU AI Cloud. Deployment to US AI Cloud is in progress.

4. resolved 2025-10-01 18:04 UTC

   Engineering team has applied the fix to address UI issue affecting Model Visibility and Project Management. This problem has now been resolved.

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

Affected: API, API, API, API, Predictions, Predictions, Prediction, AI Apps, AI Apps, AI Apps, Notebooks, Notebooks

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. identified 2025-09-25 01:19 UTC

   At 23:09 UTC / 4:09 PM PST, an unexpected outage from DockerHub triggered internal alerts. The engineering team is currently assessing potential impact across environments. We will share further details and mitigation steps as soon as our investigation progresses.

2. monitoring 2025-09-25 01:35 UTC

   As of 01:09 UTC (Sept 25)/ 06:09 PM PST, systems have started recovering from the DockerHub outage. DataRobot internal services are back to normal. The engineering team will continue to monitor closely.

3. resolved 2025-09-25 01:56 UTC

   Issue is resolved and DataRobot MTS & STS services are back to normal.

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

Affected: Website

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-09 05:39 UTC

   We've identified that some users in Japan are experiencing an intermittent login issue when trying to access the US MTS. The engineering team is currently investigating.

2. investigating 2025-09-09 11:26 UTC

   Users in APAC are experiencing network issues when accessing application endpoints in US MTS. Engineering is investigating potential ISP-related networking issues in APAC region. Affected customers are encouraged to try using a different network and/or browsers to mitigate the...

3. monitoring 2025-09-09 14:02 UTC

   Users can now access US MTS cluster from APAC region and issue recovered. The engineering team will continue monitoring this issue.

4. monitoring 2025-09-09 18:14 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-09-10 18:03 UTC

   This incident has been resolved.

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

Affected: Prediction, MLOps

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-02 15:37 UTC

   We've identified an issue impacting serverless deployments when a new deployment is created or an existing deployment is modified, in Japan cluster. Prediction against existing deployments deployed to serveless prediction server that are not modified are not impacted....

2. resolved 2025-09-02 18:07 UTC

   Engineering has applied the fix to mitigate the issue impacting serverless deployments when a new deployment is created or an existing deployment is modified. The problem has now been contained.

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

Affected: MLOps, MLOps, MLOps

Failure mode: A code release introduced the failure. 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-29 11:51 UTC

   Some of the customers are not receiving scheduled deployment reports. The data can still be observed in the application UI. The engineering is actively working on restoring the functionality. Please check the below-mentioned link for docs for generating report:...

2. identified 2025-07-29 14:32 UTC

   Engineering has identified the root cause and prepared a fix. The team has now started deploying the fix to MTS production.

3. resolved 2025-07-29 22:09 UTC

   This incident has been resolved.

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

Affected: Website, API, Predictions, AutoML, AI Catalog and Data Ingest, AI Apps, MLOps, Pipeline, Notebooks, Generative AI LLM Playground, Generative AI VDB Builder

Failure mode: The text does not say enough to tell. 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-07-07 15:42 UTC

   Starting 11:05 EST today, Interface is down for all customers in the US Prod due to internal error. Engineering has identified the problem and is in the process of applying the fix.

2. monitoring 2025-07-07 16:12 UTC

   The fix has been applied successfully and the interface has been restored. Engineering is currently monitoring the system.

3. resolved 2025-07-07 16:20 UTC

   The fix has resolved the interface failure issue. DataRobot App in US Prod is fully functioning as normal.

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

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. identified 2025-06-12 20:27 UTC

   External cloud providers are experiencing outages which is impacting the DataRobot platform and services.

2. monitoring 2025-06-12 20:35 UTC

   Our engineering team will continue to monitor the outages reported by external cloud providers.

3. resolved 2025-06-13 01:30 UTC

   Our engineering team confirmed that the outage with our external cloud provider has been resolved. We have been monitoring our functionalities and no specific functionality was affected.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-06-12 08:00 UTC

   Managed EU AI Cloud had a degraded performance during 7:00 - 7:30 AM UTC. Some users could experience intermittent connection interruptions. Please reach out to support@datarobot.com if you have any questions.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-03 09:43 UTC

   Root cause is identified and team is working on the fix

2. identified 2025-06-03 13:16 UTC

   Team is working on implementing the fix

3. resolved 2025-06-04 13:13 UTC

   Issue is now resolved and the drift charts are working as expected

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

Affected: Website, API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-05-28 11:30 UTC

   Codespaces are not starting on EU MTS because of internal connection issues. The Engineering team is working on the fix.

2. resolved 2025-05-28 11:41 UTC

   The Engineering team has applied the fix and the issue has been resolved.

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

Affected: Notebooks, Notebooks

Failure mode: The text does not say enough to tell. 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-05-12 20:25 UTC

   Subset of running notebooks sessions getting terminated in all environments (US/EU/JP). Multiple customers are impacted. Engineering team investigating the root cause.

2. monitoring 2025-05-12 22:24 UTC

   Engineering has found the potential root cause and applied a fix. Engineering is now monitoring impacted services.

3. resolved 2025-05-13 11:24 UTC

   Engineering has successfully applied the fix, and all notebooks are now running as expected across all MTS environments.

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

Affected: Website, Website, Website

Failure mode: The text does not say enough to tell. 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-04-28 11:35 UTC

   The Engineering team has identified the root cause and is woking on a fix.

2. identified 2025-04-28 12:14 UTC

   The Engineering team has applied the fix to Japan MTS and the Trial user creation has been restored in that cluster. The team is now proceeding to apply the fix to US and EU MTS.

3. resolved 2025-04-28 12:35 UTC

   The Engineering team has applied the fix to US and EU MTS and the Trial user creation has been restored across all MTS environments.

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

Affected: AI Apps, AI Apps, AI Apps

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-25 08:44 UTC

   Users with language settings other than English in profile unable to launch or access AI apps on MTS as the translation files are not loading correctly. As a workaround users can switch to English. We are actively investigating the issue and working on a fix.

2. identified 2025-04-25 09:59 UTC

   Engineering has identified the root cause of the issue and is currently preparing a fix.

3. identified 2025-04-25 12:01 UTC

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

4. identified 2025-04-25 12:19 UTC

   ETA for the deployment of the hotfix to the Japan (JP) environment is approximately 4 hours.

5. resolved 2025-04-26 08:51 UTC

   A fix has been applied to all production environments, no-code applications are operational in all languages.

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

Affected: Website, API, AI Catalog and Data Ingest, Generative AI LLM Playground, Generative AI VDB Builder

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

1. investigating 2025-04-16 09:34 UTC

   STS customers might observe degraded performance caused by Regular Maintenance performed by DataRobot Engineering. Engineering team is working on the mitigation.

2. resolved 2025-04-16 10:37 UTC

   The Engineering team has identified the issue and is currently applying mitigation steps. If you continue to experience any issues, please contact DataRobot Support.

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

Failure mode: A zone, region or data center became unavailable. 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: AWS.

1. resolved 2025-04-15 08:00 UTC

   AWS had an outage in ap-northeast-1 region that has since been resolved. Outage times: 7.47am GMT to 9:30am GMT Engineering is working to restore any affected customers on STS.

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

Affected: Notebooks

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: Azure.

1. identified 2025-04-09 12:29 UTC

   Code Assistant API requests are currently taking longer than usual for US Production customers. This is a result of a partial outage on Azure. The Engineering team is monitoring the situation and will provide updates when functionality is restored.

2. resolved 2025-04-09 18:42 UTC

   This incident has been resolved.

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

Affected: Generative AI VDB Builder, Generative AI VDB Builder, Generative AI VDB Builder

Failure mode: A code release introduced the failure. 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-04-01 11:09 UTC

   Engineering has observed that VDB creation began failing across all MTS environments following today's production deployment. The team is currently investigating the root cause and actively working on a fix.

2. resolved 2025-04-01 11:54 UTC

   The issue has been successfully mitigated in the MTS production environments. The incident is now contained, and VDB creation functionality has been fully restored.

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

Affected: Website, Website, Website

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-03-04 14:10 UTC

   SSO login has been broken, which may affect users in an attempt to log in. The Engineering team has prepared the fix. The approximate ETA for the hotfix release is 8 hours across all MTS Environments.

2. identified 2025-03-04 14:55 UTC

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

3. resolved 2025-03-05 15:06 UTC

   This incident has been resolved.

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

Affected: AI Apps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-05 16:10 UTC

   Some users on US SaaS are unable to access their Custom Applications. Engineering team is currently investigating, we will keep you updated.

2. resolved 2025-02-05 16:33 UTC

   The affected users can access the Custom Applications now. The incident has been mitigated.

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

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-03 18:16 UTC

   The Trial user provisioning is not working on the DataRobot US production environment. The engineering team is currently investigating.

2. resolved 2025-02-03 18:39 UTC

   The Trial user provisioning is back on and working as expected in the DataRobot US production environment. The issue is resolved.

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

Affected: Generative AI LLM Playground

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-28 14:51 UTC

   Japan MTS cluster is experiencing issues with creating custom models from LLM Playground. The engineering team is investigating.

2. monitoring 2025-01-28 15:08 UTC

   The issue is mitigated and users are able to create custom models again. The engineering team will continue to monitor the environment and prepare a permanent fix until the incident is contained. The estimate is ~ 2 hrs at the moment.

3. resolved 2025-01-28 18:13 UTC

   This incident has been resolved.

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

Affected: MLOps

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-01-15 16:56 UTC

   Our team has identified an issue with our Deployment Monitoring Information. This is a process delay and no data loss is expected. Our team is currently investigating the root cause and is working on a fix. The following services are currently impacted Service Health, Data...

2. monitoring 2025-01-15 19:36 UTC

   Our team has identified the root cause and implemented the fix. Service Health and Accuracy no longer have a delay and are operating normally. The delay in Data Drift monitoring is improving, however the Engineering team expects it will take several hours to fully recover as the...

3. monitoring 2025-01-16 09:30 UTC

   The unprocessed message backlog continues to catch up. The engineering team is closely monitoring the process. We will provide an update once the processing of delayed messages is caught up.

4. resolved 2025-01-16 21:54 UTC

   This incident has been contained.

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

Affected: AI Apps, MLOps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-08 15:34 UTC

   The Custom Workload is failing to start in the US MTSaaS environment. Existing running Custom Apps aren't affected. The Engineering team is investigating the root cause.

2. resolved 2025-01-08 17:58 UTC

   Engineering has identified the root cause and fixed the issue. The Custom Workloads are starting normally on the US MTSaaS environment, and the incident is resolved.

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