Jobs list and Environment pages failing to load
The Jobs page, Project and Environment pages, and run logs do not load for some dbt Cloud accounts on US and EMEA instances. dbt Cloud reports that a fix is deployed and the pages returned to normal at 2026-11-04 20:57 UTC. dbt Cloud continues to monitor. Some scheduled and API-triggered runs did not start and may need a manual re-trigger.
State
Monitoring
Started
Ongoing for
1 h 46 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
18 min 17%
Identified
1 h 9 min 65%
Monitoring
19 min 18%
Updates
Times in UTCAs posted by dbt Cloud
We have deployed a fix for the issue affecting the Jobs page, Project and Environment pages, and run logs, and these pages returned to normal as of 2026-11-04 20:57 UTC. We are continuing to monitor. Some scheduled and API-triggered runs during the incident did not start and may need to be re-triggered manually.
We have identified an issue with the Jobs page, Project and Environment pages, and run logs that was caused by a recent deployment. Some accounts may see an empty jobs list or errors when loading these pages. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. A fix is being implemented and we will provide an update shortly.
We began investigating at 2026-11-04 19:06 UTC an issue affecting the Jobs page, Project and Environment pages, and run logs for some accounts. Affected users may see an empty jobs list or an error when loading these pages, and may be unable to view, edit, create, or manually trigger jobs. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. The team is working on a resolution and we will provide updates as soon as new information becomes available.
We have identified an issue with the Jobs page, Project and Environment pages, and run logs that was caused by a recent deployment. Some accounts on US and EMEA instances may see an empty jobs list or errors when loading these pages. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. A fix is being implemented and we will provide an update shortly.
We began investigating at 2026-11-04 19:06 UTC an issue affecting the Jobs page, Project and Environment pages, and run logs for some accounts. Affected users may see an empty jobs list or an error when loading these pages, and may be unable to view, edit, create, or manually trigger jobs. Scheduled jobs continue to run as expected and there is no impact to pipelines or data. The team is working on a resolution and we will provide updates as soon as new information becomes available.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
26
Median duration
2 h 17 min
This incident
23% shorter than the median
Other dbt Cloud incidents
All incidentsdbt Cloud·Git errors for projects connected to GitHub over SSH
Git operations failed for dbt Cloud projects that use a dbt-managed repository or connect to GitHub with a deploy key. The errors were "Permission denied (publickey)" in job runs and dbt Studio git actions. dbt Cloud reports that this incident is resolved. It lasted 1 minute and 43 seconds.
dbt Cloud·dbt Studio error loop with restarting dbt Studio
dbt Cloud reported an error loop in dbt Studio that asked users to restart dbt Studio. The issue affected dbt Project Environments on versions 1.6 and 1.7. dbt Cloud resolved the issue after 86 minutes.
dbt Cloud·Expired GitLab project access tokens not refreshing causing failures in posting commit statuses
dbt Cloud did not post GitLab CI job commit statuses for existing projects with expired GitLab project access tokens. This affected a small number of customers in the EU2 (Azure) region. dbt Cloud reports that the issue is resolved and that it lasted about 111 minutes.
dbt 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
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.live/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.live/feed.xml?providers=dbt/feed subscribe https://outages.live/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane