Dremio: Unable to run queries in Dremio Cloud (US)
AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents
Dremio’s incident blames AWS as the cause. (hop 1, posted +8 h 1 min vs AWS’s own post)
“…ueries in Dremio Cloud (US) 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…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
root --> before
h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
root --> h1
h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
root --> h4
later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
root --> later
p0["Twilio<br/>posted +15 min"]:::blames
root --> p0
k0["BigCommerce<br/>+2 h 46 min"]:::hop2
p0 -->|"blamed Twilio"| k0
p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
root -.-> p1
k1["Rootly<br/>+10 h 23 min"]:::hop2
p1 -->|"blamed Webflow"| k1
p2["Baseten<br/>posted +4 min"]:::blames
root --> p2
k2["Zed<br/>+26 h 20 min"]:::hop2
p2 -->|"blamed Baseten"| k2
me["Dremio (this incident)<br/>posted +8 h 1 min"]:::me
later --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
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.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).