Is dbt Cloud Down?

DatabaseLive status, outages, and incident history

No. dbt Cloud is up right now.

Every monitored dbt Cloud system is operational as of October 13, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment dbt Cloud breaks

dbt Cloud is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official dbt Cloud status page

How we know: the official dbt Cloud status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

dbt Cloud Component Status

The main dbt Cloud systems on this page. All 135 are operational right now.

135operational

Admin API · APAC AWS

Operational

Admin API · AU2 Cell 1 Azure

Operational

Admin API · EMEA AWS

Operational

132 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking dbt platform CLI, and 131 more.

See all of them free

Component statuses may change independently during partial outages.

Recent dbt Cloud Outages & Incidents

Incident history from the official dbt Cloud status page, including resolution updates.

Run logs and artifacts missing for some runs (US Cell 3, GCP)Resolved Oct 8, 2026 · 30h 36mResolved

The issue has been resolved, and all affected systems are now functioning normally as of 1:20 PM Eastern on October 8. Between 11:30 AM and 1:20 PM Eastern, an issue with run artifact and log storage in US Cell 3 (GCP) resulted in some job runs completing without their logs and artifacts (such as manifest.json and run_results.json) being available, and some runs that use deferral failing. We have put measures in place to prevent a recurrence and run artifact and log storage has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause. --- [2026-10-08T20:26:45Z] (monitoring) GCP has completed mitigations on their end that were causing some job runs to complete without their logs and artifacts (such as [manifest.json](https://manifest.json) and [run_results.json](https://run_results.json)) being available. Scheduled jobs and metadata ingestion have returned to their normal state and we are continuing to monitor. --- [2026-10-08T16:19:29Z] (investigating) We're investigating an issue with run artifact and log storage that is causing some job runs to complete without their logs and artifacts (such as manifest.json and run_results.json) being available. This is impacting some runs in the US Cell 3 (GCP) region anytime after 11:30 AM Eastern. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Other dbt Cloud components are not impacted and should be running as expected. Job runs that use deferral and depend on artifacts from affected runs may fail.

Increased errors for Wizard CLI requests using Anthropic modelsResolved Oct 2, 2026 · 1h 28mResolved

The issue has been resolved, and all affected systems are now functioning normally as of 12:30 UTC. We have put measures in place to prevent a recurrence and the system has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause. --- [2026-10-02T11:50:30Z] (identified) We've identified the cause of the increased errors affecting Wizard CLI requests to Anthropic models — introduced during a recent inference endpoint upgrade. A fix has been prepared and is being deployed. We have not yet confirmed full recovery and will provide another update once that's verified. All other dbt Cloud functionality is not impacted and should be running as expected. --- [2026-10-02T11:47:20Z] (identified) We've identified the cause of the increased errors affecting Wizard CLI requests to Anthropic models — introduced during a recent inference endpoint upgrade. A fix has been prepared and is being deployed. We have not yet confirmed full recovery and will provide another update once that's verified. All other dbt Cloud functionality is not impacted and should be running as expected. --- [2026-10-02T11:05:59Z] (identified) We're investigating an issue with Wizard CLI requests to Anthropic models that is causing increased errors for affected customers. This is impacting AI-assisted CLI functionality in our multi-tenant US production environment this morning. The team is working on a resolution and we will provide updates as soon as new information becomes available. All other dbt Cloud functionality is not impacted and should be running as expected.

dbt deps failures impacting private packagesResolved Sep 30, 2026 · 56 minResolved

The issue has been resolved, and all affected systems are now functioning normally as of 9:55 PM UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause. --- [2026-09-30T22:23:13Z] (monitoring) We have deployed a fix and are beginning to see recovery in scheduled jobs. We will continue to monitor. --- [2026-09-30T22:14:51Z] (investigating) We're investigating an issue with private packages due to the error "No matching Git URLs for private definition" that is causing the dbt deps run step to fail. The team is working on a resolution and we will provide updates as soon as new information becomes available.

dbt Cloud Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a dbt Cloud incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

Jul 1599.99% average · 5 days with incidentsOct 13

Going further back: dbt Cloud uptime by month and every recorded dbt Cloud outage.

Live dbt Cloud Outage Reports

Problems reported by engineers using dbt Cloud. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No dbt Cloud problems reported yet.

Something wrong with dbt Cloud on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About dbt Cloud

dbt Cloud publishes overall service health on its public status page at status.getdbt.com. PulsAPI tracks dbt Cloud outages, degraded performance and incident history in real time, alongside the rest of your database stack.

Over the past 30 days, PulsAPI has measured dbt Cloud uptime at 100.00%. Response times, incident history, and SLA tracking for dbt Cloud are available on the PulsAPI dashboard.

dbt Cloud Status FAQ

Is dbt Cloud down right now?

The verdict at the top of this page comes from the latest poll of the official dbt Cloud status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if dbt Cloud is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until dbt Cloud recovers.

How do I check dbt Cloud uptime history?

PulsAPI tracks dbt Cloud uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever dbt Cloud changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect dbt Cloud outages?

PulsAPI reads the official dbt Cloud status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual dbt Cloud components?

Yes. PulsAPI monitors 135 individual dbt Cloud components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when dbt Cloud goes down?

Yes. Create a free account and subscribe to dbt Cloud: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with dbt Cloud to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot dbt Cloud problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor dbt Cloud?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so dbt Cloud plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track dbt Cloud with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services