State usage metrics not being ingested
This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience
The latest update from dbt Cloud.
State
Resolved
Started
53 d ago
2026-09-10 08:02 UTC
Lasted
1 h 13 min
until 2026-09-10 09:14 UTC
Worst impact
Partial outage
Timeline
4 updatesInvestigating
12 min 17%
Identified
38 min 52%
Monitoring
22 min 31%
Updates
Times in UTCAs posted by dbt Cloud
This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience
A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this.
We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience.
We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
22
Days with an incident
24
Median duration
2 h 58 min
This incident
59% shorter than the median
Other dbt Cloud incidents
All incidentsdbt Cloud·dbt Wizard SQL execution failing
The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Degraded performance across dbt platform
The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform 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
dbt Cloud·dbt deps failures in dbt job runs and Studio
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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.
dbt Cloud·Delayed and stuck job runs in EMEA
**Update posted at 15:05 UTC:** This incident has been resolved. Between about 06:00 and 12:10 UTC, an incident with our cloud provider (GCP) affected services in EMEA. Some customers saw stuck or delayed job runs, failed run cancellations, delayed notifications, out-of-date information in dbt Explorer and intermittent Semantic Layer errors. All services have recovered and are working as expected. If you still see any issues, please contact support.
dbt Cloud·Intermittent dbt package download failures
The issue has been resolved, and all affected systems are now functioning normally as of 16:10 UTC. We have put measures in place to prevent a recurrence and dbt package installations have 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.
Follow dbt Cloud
Your coding agent knows when dbt Cloud is down, and tells you when a failure is theirs, not yours. You can also get dbt Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dbt" and tell me if dbt Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=dbt/feed subscribe https://outages.cc/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane