Dremio Outage History

Started Oct 05, 2026, 07:26 PM UTC· resolved Oct 05, 2026, 08:02 PM UTC

1. resolved Oct 05, 2026, 09:54 PM UTC

   Between 12:26 and 1:02 PM PDT today, a configuration issue caused query failures for users on Dremio Cloud (US & EU). The issue was identified and resolved within 36 minutes. All query services are operating normally. We apologize for the disruption and are taking steps to prevent similar issues in the future.

Read the full incident report →

Started Aug 26, 2026, 09:25 PM UTC· resolved Aug 26, 2026, 09:55 PM UTC

1. identified Aug 26, 2026, 09:25 PM UTC

   We are investigating an issue preventing some engines from starting on Dremio Cloud (US). Users with classic engines may be unable to scale up or start new engines. Our team has identified a potential cause and is actively working on a fix. We will provide an update as more information becomes available.

2. monitoring Aug 26, 2026, 09:42 PM UTC

   A fix has been applied for the engine scaling issue on Dremio Cloud (US). Engines should now be able to start and scale normally. Our team is monitoring to confirm full recovery across all affected environments.

3. resolved Aug 26, 2026, 09:55 PM UTC

   This incident has been resolved. Earlier today, an infrastructure issue on Dremio Cloud (US) prevented some engines from starting or scaling up. Our team identified the cause, deployed a fix, and confirmed that engine operations have returned to normal. We appreciate your patience.

4. postmortem Sep 01, 2026, 04:58 PM UTC

   On August 26, 2026, between approximately 12:30 PM and 2:45 PM PDT, some users on Dremio Cloud \(US\) were unable to start or scale up engines. The issue was caused by an infrastructure artifact required for engine provisioning being inadvertently removed during a compliance-related infrastructure change. Engines that were already running were not affected. Our team identified the root cause, restored the affected component across all US regions, and confirmed that engine operations returned to normal. Beyond this fix, we are conducting a broader review of our infrastructure maintenance workflows to strengthen production dependency checks, and implementing monitoring for critical provisioning components to catch similar issues sooner. We recognize the impact this had on your operations and apologize for the disruption. Thank you for your patience as we worked to resolve it.

Read the full incident report →

Started Aug 05, 2026, 01:58 PM UTC· resolved Aug 05, 2026, 06:49 PM UTC

1. identified Aug 05, 2026, 01:58 PM UTC

   We are investigating an incident affecting Dremio Cloud US. Users may be unable to load the application or complete login. Dremio Cloud Europe is operating normally.

2. identified Aug 05, 2026, 02:46 PM UTC

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

3. monitoring Aug 05, 2026, 02:47 PM UTC

   Service has recovered. We are continuing to monitor Dremio Cloud login and application access following an issue that caused intermittent unavailability. All services are healthy.

4. resolved Aug 05, 2026, 06:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 20, 2026, 08:24 AM UTC· resolved Jun 21, 2026, 06:15 AM UTC

1. resolved Jun 20, 2026, 08:24 AM UTC

   Starting around 23:13 UTC on June 19, 2026, Dremio Cloud US region experienced intermittent query failures due to connectivity issues within the engine management service. The issue was detected by our monitoring systems and mitigation was applied soon after at 04:00 UTC on June 20, 2026. The system fully recovered by 06:15 UTC. We apologize for any inconvenience.

Read the full incident report →

Started Jun 18, 2026, 12:54 AM UTC· resolved Jun 18, 2026, 02:55 AM UTC

1. resolved Jun 18, 2026, 03:49 AM UTC

   During pre-steps for a scheduled system update, an infrastructure change was inadvertently published ahead of schedule, resulting in minor network connectivity issues and a brief period of degraded performance, with some failing queries. The issue was identified at 00:54 UTC and fully resolved by 02:55 UTC. All systems are now fully operational. We apologize for any inconvenience.

Read the full incident report →

Started Jun 12, 2026, 06:54 PM UTC· resolved Jun 16, 2026, 04:04 PM UTC

1. identified Jun 12, 2026, 06:54 PM UTC

   We've identified an issue affecting email delivery on Dremio Cloud (EU). Email notifications, including account and system notifications, are currently not being delivered. Our team is actively working to restore delivery and will provide an update as soon as we have more information.

2. identified Jun 12, 2026, 08:25 PM UTC

   Email delivery on Dremio Cloud (EU) is currently affected by an issue with a third-party email service provider. Email notifications, including account and system notifications, are not being delivered. We are working directly with the provider to restore services and will share another update as soon as there is a meaningful change in status.

3. resolved Jun 16, 2026, 04:04 PM UTC

   We have successfully resolved the issue affecting email delivery on Dremio Cloud (EU). All email notifications are now being delivered as expected. We appreciate your patience while we worked with the third-party provider to resolve this

Read the full incident report →

Started Mar 08, 2026, 05:03 AM UTC· resolved Mar 08, 2026, 05:30 AM UTC

1. identified Mar 08, 2026, 05:03 AM UTC

   We are currently investigating intermittent login issues for some Dremio Cloud users in the US and EU. We will provide an update in 30 minutes.

2. monitoring Mar 08, 2026, 05:14 AM UTC

   We have applied a mitigation for the login issues for users in both Dremio Cloud US and EU. We will continue monitoring for any residual login issues. We apologize for the inconvenience.

3. resolved Mar 08, 2026, 05:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 25, 2026, 04:57 AM UTC· resolved Feb 25, 2026, 05:28 AM UTC

1. identified Feb 25, 2026, 04:57 AM UTC

   We've identified an issue that is intermittently affecting Dremio Cloud's AI integrations for a select number of projects. We are working to mitigate this and will provide another status update in 20 minutes.

2. monitoring Feb 25, 2026, 05:18 AM UTC

   We have mitigated this issue for all projects at this time and will continue to monitor for any additional errors. We apologize for any inconvenience caused.

3. resolved Feb 25, 2026, 05:28 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 24, 2026, 11:15 PM UTC· resolved Feb 24, 2026, 11:51 PM UTC

1. monitoring Feb 24, 2026, 11:15 PM UTC

   System upgrade in progress Regions: EMEA System is currently undergoing a planned upgrade. We expect the system to be available and functional, but some running queries may be interrupted during the upgrade. Expected completion: 5:30 pm PST

2. resolved Feb 24, 2026, 11:51 PM UTC

   System upgrade was successfully finished.

Read the full incident report →

Started Feb 18, 2026, 05:44 PM UTC· resolved Feb 18, 2026, 05:55 PM UTC

1. identified Feb 18, 2026, 05:44 PM UTC

   Dremio is going through a maintenance update for one of the service in our US cluster. This may impact some queries. The system should be fully functional within 10 minutes

2. resolved Feb 18, 2026, 05:55 PM UTC

   Service update was delivered.

Read the full incident report →

Started Jan 28, 2026, 04:41 AM UTC· resolved Jan 28, 2026, 04:41 AM UTC

1. resolved Jan 28, 2026, 04:48 PM UTC

   At 8:41 PM PT, a change to a feature flag was inadvertently applied to the production systems which impacted queries for select projects. The issue was resolved on 1/28/2026 at 12:04 AM PT by reverting the change to the feature flag. We apologize for the inconvenience and our delayed status update. We are taking the necessary steps to prevent such errors in the future.

Read the full incident report →

Started Oct 20, 2025, 04:08 PM UTC· resolved Oct 20, 2025, 11:19 PM UTC

1. identified Oct 20, 2025, 04:08 PM UTC

   We have observed issues with engine scaling in the AWS us-east-1 region due to AWS service throttling as part of AWS' ongoing incident. We are actively monitoring the situation.

2. resolved Oct 20, 2025, 11:19 PM UTC

   We have observed recovery of AWS services in the us-east-1 region and engine scale ups are succeeding at this time.

Read the full incident report →

Started Oct 20, 2025, 09:30 AM UTC· resolved Oct 20, 2025, 09:30 AM UTC

1. resolved Oct 20, 2025, 03:11 PM UTC

   On 10/20/2025, at approximately 2:30 AM PDT, an outage in the AWS us-east-1 region resulted in Query execution failures within Dremio projects in that region. The issue has been resolved by AWS and Dremio Query Execution services within that region are fully operational.

Read the full incident report →

Started Jun 12, 2025, 07:47 PM UTC· resolved Jun 12, 2025, 11:33 PM UTC

1. investigating Jun 12, 2025, 07:47 PM UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

2. identified Jun 12, 2025, 07:51 PM UTC

   We are experiencing intermittent failures in Dremio Cloud (EU) due to disruptions in upstream providers. We are currently working with our partners to resolve this as soon as possible. We will provide a subsequent update in the next 60 minutes.

3. identified Jun 12, 2025, 08:38 PM UTC

   We are continuing to experience intermittent failures in Dremio Cloud (EU) due to disruptions in upstream providers. We are working with our partners to resolve this as soon as possible. We will provide a subsequent update in the next 60 minutes.

4. identified Jun 12, 2025, 10:02 PM UTC

   We are continuing to experience delays in Dremio Cloud (EU) due to disruptions in upstream providers. We are working with our partners to resolve this as soon as possible. We will provide a subsequent update in the next 60 minutes.

5. monitoring Jun 12, 2025, 10:28 PM UTC

   We have seen recovery of Dremio Cloud (EU). We are continuing to monitor for any residual issues with our upstream providers.

6. resolved Jun 12, 2025, 11:33 PM UTC

   We have seen recovery of GCP which affected our upstream providers. This issue is now resolved and Dremio Cloud (EU) is fully operational.

Read the full incident report →

Started Apr 11, 2025, 10:26 AM UTC· resolved Apr 11, 2025, 11:27 AM UTC

1. identified Apr 11, 2025, 10:26 AM UTC

   We have identified an issue impacting customers with Azure engines using PrivateLink connectivity back to Dremio Cloud (EU). We are currently working on mitigating the issue. We will provide another update within 30 minutes.

2. monitoring Apr 11, 2025, 10:53 AM UTC

   We have mitigated an issue preventing customers with Azure engines using PrivateLink connectivity back to Dremio Cloud (EU) from scaling up successfully. We are actively monitoring the recovery of engines in customer environments and are seeing successful scale ups. We apologize for any inconvenience caused.

3. resolved Apr 11, 2025, 11:27 AM UTC

   We have mitigated an issue preventing customers with Azure engines using PrivateLink connectivity back to Dremio Cloud (EU) from scaling up successfully. We have now seen successful scale up of engines in customer environments. We apologize for any inconvenience caused.

Read the full incident report →

Started Apr 02, 2025, 06:24 PM UTC· resolved Apr 02, 2025, 06:24 PM UTC

1. resolved Apr 02, 2025, 07:56 PM UTC

   A configuration change prevented queries from completing. We have reverted this configuration change and have seen that queries are now operational again. We apologize for any inconvenience caused.

Read the full incident report →

Started Mar 20, 2025, 07:33 AM UTC· resolved Mar 20, 2025, 08:35 AM UTC

1. investigating Mar 20, 2025, 07:33 AM UTC

   We are currently working on mitigating an issue impacting some customers within Dremio Cloud (EU) that causes queries to not progress past the metadata retrieval stage. We will provide another update within 60 minutes.

2. resolved Mar 20, 2025, 08:35 AM UTC

   Our engineers were able to rollback some changes and restore service for impacted customers. This incident is now resolved.

Read the full incident report →

Started Mar 19, 2025, 04:00 PM UTC· resolved Mar 19, 2025, 04:00 PM UTC

1. resolved Mar 19, 2025, 04:05 PM UTC

   An internal test of our incidence response tooling sent a bulletin to the public status page. Dremio Cloud continues to be operational at this time. We apologize for any inconvenience or confusion caused.

Read the full incident report →

Started Feb 28, 2025, 12:39 AM UTC· resolved Feb 28, 2025, 08:49 AM UTC

1. investigating Feb 28, 2025, 12:39 AM UTC

   We have detected an outage impacting our Dremio Cloud (US) service. We are investigating the cause and will provide another update within 30 minutes.

2. identified Feb 28, 2025, 01:06 AM UTC

   We have identified an infrastructure issue that is impacting accessibility to Dremio Cloud (US). We are working urgently to restore the affected infrastructure.

3. identified Feb 28, 2025, 02:07 AM UTC

   We have identified an infrastructure issue that is impacting accessibility to Dremio Cloud (US). We are continuing to work urgently to restore the affected infrastructure.

4. identified Feb 28, 2025, 05:27 AM UTC

   We have identified an infrastructure issue that is impacting accessibility to Dremio Cloud (US). We are still working on bringing full restoration to the affected infrastructure.

5. identified Feb 28, 2025, 06:54 AM UTC

   We identified an infrastructure issue that affected core services for Dremio Cloud (US). We are continuing to work urgently to restore full access to customers.

6. identified Feb 28, 2025, 06:57 AM UTC

   We identified an infrastructure issue that affected core services for Dremio Cloud (US). We are continuing to work urgently to restore full access to customers.

7. monitoring Feb 28, 2025, 07:34 AM UTC

   We have restored core services for Dremio Cloud (US) and are seeing recovery of users' projects. We are continuing to monitor the environment. We apologize for any inconvenience caused.

8. resolved Feb 28, 2025, 08:49 AM UTC

   We have restored all services for Dremio Cloud (US) and are seeing successful recovery of users' projects. We apologize for any inconvenience caused and will publish a post-mortem for this incident in the coming days.

Read the full incident report →

Started Jan 08, 2025, 11:07 PM UTC· resolved Jan 08, 2025, 11:35 PM UTC

1. resolved Jan 08, 2025, 11:47 PM UTC

   Dremio Cloud (EU) users experienced engine scaling issues which prevented queries from successfully being executed. We have mitigated this issue and are seeing recovery of engines within customer accounts. We apologize for any inconvenience caused.

Read the full incident report →

Started Dec 17, 2024, 04:56 PM UTC· resolved Dec 17, 2024, 07:01 PM UTC

1. investigating Dec 17, 2024, 04:56 PM UTC

   We are currently investigating an issue impacting engines within Dremio Cloud (US) that are causing them to shutdown while queries are in progress. We will provide another update within 30 minutes.

2. identified Dec 17, 2024, 05:27 PM UTC

   We have identified the issue impacting engine stability within Dremio Cloud (US). We are working to mitigate this issue. We will provide another update within the next 30 minutes.

3. identified Dec 17, 2024, 06:01 PM UTC

   We have identified the issue impacting engine stability within Dremio Cloud (US). We are continuing to work to mitigate this issue. We will provide another update within the next 30 minutes.

4. identified Dec 17, 2024, 06:42 PM UTC

   We are in the process of mitigating the issue. More updates will be provided in 30 minutes.

5. identified Dec 17, 2024, 06:52 PM UTC

   We have identified the issue impacting engine stability within Dremio Cloud (US). We have applied changes to our infrastructure and are working on recovering services. We will provide another update within the next 30 minutes.

6. identified Dec 17, 2024, 06:54 PM UTC

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

7. monitoring Dec 17, 2024, 06:58 PM UTC

   We have mitigated the issue impacting engine stability within Dremio Cloud (US) and are continuing to monitor the recovery of customer engines. We apologize for any inconvenience caused.

8. resolved Dec 17, 2024, 07:01 PM UTC

   We have mitigated the issue impacting engine stability within Dremio Cloud (US) and have seen successful recovery of customer engines. We apologize for any inconvenience caused and will publish a post-mortem for this incident in the coming days.

Read the full incident report →