Störungsverlauf von Datarobot

1. 18. August 2026 um 12:20 UTCidentified

   Die Codespace-Sitzung im Generative AI Playground schlägt aufgrund eines Validierungsfehlers fehl. Engineering arbeitet daran, einen Fix zu erstellen.

2. 18. August 2026 um 13:56 UTCidentified

   Engineering hat einen Fix implementiert und arbeitet derzeit daran, ihn in den Produktionsclustern einzusetzen.

3. 18. August 2026 um 14:44 UTCresolved

   Der Fix wird nun in allen Prod-Umgebungen bereitgestellt und Generative AI Playground funktioniert nun wie erwartet.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 17:32 UTCinvestigating

   Das DataRobot Engineering-Team beobachtete Probleme beim Erstellen einer DataRobot gehosteten Vektordatenbank. Derzeit betrifft dies alle DataRobot MTS-Umgebungen und das Engineering untersucht die Ursache.

2. 24. Juli 2026 um 17:44 UTCmonitoring

   Das Engineering-Team hat den Fix angewendet und die Erstellung der Vector-Datenbank ist jetzt in Betrieb. Das Team beobachtet die Situation.

3. 24. Juli 2026 um 18:42 UTCresolved

   Das Ingenieurteam beobachtete, dass die Erstellung der Vector-Datenbank in allen MTS-Umgebungen von DataRobot einsatzbereit ist. Der Vorfall ist gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 13:03 UTCinvestigating

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

2. 2. Juli 2026 um 13:20 UTCidentified

   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. 2. Juli 2026 um 13:37 UTCresolved

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

1. 29. Mai 2026 um 08:37 UTCidentified

   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. 29. Mai 2026 um 10:22 UTCidentified

   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. 29. Mai 2026 um 14:38 UTCmonitoring

   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. 29. Mai 2026 um 15:20 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 3. Juni 2026 um 09:29 UTCresolved

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

1. 28. Mai 2026 um 09:09 UTCidentified

   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. 28. Mai 2026 um 09:47 UTCresolved

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

1. 26. Mai 2026 um 05:09 UTCinvestigating

   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.

2. 26. Mai 2026 um 06:01 UTCmonitoring

   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. 26. Mai 2026 um 06:04 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 26. Mai 2026 um 06:18 UTCresolved

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

1. 8. Mai 2026 um 03:53 UTCmonitoring

   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.

2. 8. Mai 2026 um 06:13 UTCidentified

   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. 8. Mai 2026 um 13:40 UTCmonitoring

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

4. 8. Mai 2026 um 20:21 UTCresolved

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

1. 10. April 2026 um 10:24 UTCmonitoring

   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. 10. April 2026 um 11:01 UTCresolved

   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.

1. 9. April 2026 um 21:56 UTCinvestigating

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

2. 9. April 2026 um 22:56 UTCmonitoring

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

3. 10. April 2026 um 11:31 UTCmonitoring

   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. 10. April 2026 um 13:04 UTCresolved

   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.

1. 30. März 2026 um 20:43 UTCidentified

   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. 30. März 2026 um 20:44 UTCidentified

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

3. 31. März 2026 um 08:53 UTCresolved

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

1. 13. März 2026 um 17:49 UTCinvestigating

   We are experiencing performance degradation on Managed AI Cloud.

2. 13. März 2026 um 18:31 UTCmonitoring

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

3. 13. März 2026 um 18:43 UTCresolved

   This incident has been resolved.

1. 11. März 2026 um 20:05 UTCinvestigating

   We are currently investigating this issue.

2. 11. März 2026 um 20:22 UTCmonitoring

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

3. 17. März 2026 um 18:31 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 17. März 2026 um 18:32 UTCresolved

   This incident has been resolved.

1. 11. März 2026 um 14:36 UTCinvestigating

   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. 11. März 2026 um 15:06 UTCidentified

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

3. 11. März 2026 um 15:19 UTCmonitoring

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

4. 11. März 2026 um 16:41 UTCresolved

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

1. 18. Februar 2026 um 21:04 UTCinvestigating

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

2. 18. Februar 2026 um 21:19 UTCresolved

   This incident is now resolved.

1. 17. Februar 2026 um 15:48 UTCidentified

   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. 17. Februar 2026 um 15:55 UTCresolved

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

1. 16. Februar 2026 um 11:35 UTCidentified

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

2. 16. Februar 2026 um 12:49 UTCresolved

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

1. 13. Februar 2026 um 20:39 UTCinvestigating

   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. 13. Februar 2026 um 21:31 UTCresolved

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

1. 8. Januar 2026 um 18:15 UTCmonitoring

   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. 8. Januar 2026 um 18:16 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 22. Januar 2026 um 14:19 UTCresolved

   This incident has been resolved.

1. 17. Dezember 2025 um 17:41 UTCresolved

   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.

1. 5. Dezember 2025 um 11:09 UTCmonitoring

   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. 5. Dezember 2025 um 11:35 UTCresolved

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