История сбоев Datarobot

1. 18 августа 2026 г. в 12:20 UTCidentified

   Сессия Codespace в Generative AI Playground не работает из-за ошибки проверки. Инженеры работают над созданием исправления.

2. 18 августа 2026 г. в 13:56 UTCidentified

   Инженерия внедрила исправление и в настоящее время работает над его развертыванием в производственных кластерах.

3. 18 августа 2026 г. в 14:44 UTCresolved

   В настоящее время исправление развернуто во всех средах Prod, и игровая площадка Generative AI теперь работает, как и ожидалось.

Автоматический перевод официального обновления инцидента.

1. 24 июля 2026 г. в 17:32 UTCinvestigating

   Команда DataRobot Engineering наблюдала за проблемами при создании базы данных векторов DataRobot. В настоящее время это влияет на все среды DataRobot MTS, и инженерия изучает первопричину.

2. 24 июля 2026 г. в 17:44 UTCmonitoring

   Инженерная команда применила исправление, и создание базы данных Vector уже работает. Команда следит за ситуацией.

3. 24 июля 2026 г. в 18:42 UTCresolved

   Инженеры отметили, что создание базы данных Vector работает во всех средах DataRobot MTS. Инцидент решен.

Автоматический перевод официального обновления инцидента.

1. 2 июля 2026 г. в 13:03 UTCinvestigating

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

2. 2 июля 2026 г. в 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 июля 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 15:20 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 3 июня 2026 г. в 09:29 UTCresolved

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

1. 28 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 06:04 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 26 мая 2026 г. в 06:18 UTCresolved

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

1. 8 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 13:40 UTCmonitoring

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

4. 8 мая 2026 г. в 20:21 UTCresolved

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

1. 10 апреля 2026 г. в 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 апреля 2026 г. в 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 апреля 2026 г. в 21:56 UTCinvestigating

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

2. 9 апреля 2026 г. в 22:56 UTCmonitoring

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

3. 10 апреля 2026 г. в 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 апреля 2026 г. в 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 марта 2026 г. в 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 марта 2026 г. в 20:44 UTCidentified

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

3. 31 марта 2026 г. в 08:53 UTCresolved

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

1. 13 марта 2026 г. в 17:49 UTCinvestigating

   We are experiencing performance degradation on Managed AI Cloud.

2. 13 марта 2026 г. в 18:31 UTCmonitoring

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

3. 13 марта 2026 г. в 18:43 UTCresolved

   This incident has been resolved.

1. 11 марта 2026 г. в 20:05 UTCinvestigating

   We are currently investigating this issue.

2. 11 марта 2026 г. в 20:22 UTCmonitoring

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

3. 17 марта 2026 г. в 18:31 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 17 марта 2026 г. в 18:32 UTCresolved

   This incident has been resolved.

1. 11 марта 2026 г. в 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 марта 2026 г. в 15:06 UTCidentified

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

3. 11 марта 2026 г. в 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 марта 2026 г. в 16:41 UTCresolved

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

1. 18 февраля 2026 г. в 21:04 UTCinvestigating

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

2. 18 февраля 2026 г. в 21:19 UTCresolved

   This incident is now resolved.

1. 17 февраля 2026 г. в 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 февраля 2026 г. в 15:55 UTCresolved

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

1. 16 февраля 2026 г. в 11:35 UTCidentified

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

2. 16 февраля 2026 г. в 12:49 UTCresolved

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

1. 13 февраля 2026 г. в 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 февраля 2026 г. в 21:31 UTCresolved

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

1. 8 января 2026 г. в 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 января 2026 г. в 18:16 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 22 января 2026 г. в 14:19 UTCresolved

   This incident has been resolved.

1. 17 декабря 2025 г. в 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 декабря 2025 г. в 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 декабря 2025 г. в 11:35 UTCresolved

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