Degraded run performance due to dbt State service disruption

What to do

• Check whether you use dbt Cloud in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-11-10 07:34 UTC and 2026-11-10 02:05 UTC may need a replay.

• Subscribe to dbt Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=dbt-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from dbt Cloud 1

1. resolvedNov 10, 2026, 2:05 AM UTC

   This incident has been resolved. Between 02:05 and 04:13 UTC on November 10, 2026, the dbt State service had intermittent availability problems and timeouts. During this window, some dbt platform runs couldn’t reach dbt State and ran without it. Those runs completed normally and produced correct results, but they didn’t get the State-based optimizations, such as reusing prior results and making clone decisions. As a result, some runs may have taken longer than usual. Apologies for the inconveniences caused. Please contact us at support@getdbt.com with any questions or concerns.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.