<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Dbt Cloud incidents — Vendor Status Watch</title><link>https://approjects-vendor-status-watch.static.hf.space/v/dbt-cloud.html</link><description>Incidents from Dbt Cloud's public status page, polled daily.</description><lastBuildDate>Wed, 16 Sep 2026 12:28:20 +0000</lastBuildDate><item><title>Intermittent errors on the Discovery API [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-10T14:28:20Z</guid><pubDate>Thu, 10 Sep 2026 14:28:20 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>Increased error rates associated with dbt MCP and dbt Wizard [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-10T13:46:47Z</guid><pubDate>Thu, 10 Sep 2026 13:46:47 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 1:57 PM UTC</description></item><item><title>State usage metrics not being ingested [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-10T08:02:13Z</guid><pubDate>Thu, 10 Sep 2026 08:02:13 +0000</pubDate><description>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</description></item><item><title>User Login Sessions Terminated [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-08T18:44:59Z</guid><pubDate>Tue, 08 Sep 2026 18:44:59 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally.

 

Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience login issues and are unsure of the root cause.</description></item><item><title>dbt Platform not responding [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-04T14:20:09Z</guid><pubDate>Fri, 04 Sep 2026 14:20:09 +0000</pubDate><description>The issue has been resolved, and all affected systems are functioning normally as of 11:30 AM Eastern. Between 9:50 AM Eastern and 10:30 AM Eastern an issue with the dbt Platform resulted in users being unable to access dbt and all services were down during this time. We have put measures in place to prevent a recurrence and the dbt Platform has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>New user onboarding issue for trial sign-ups [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-03T13:24:41Z</guid><pubDate>Thu, 03 Sep 2026 13:24:41 +0000</pubDate><description>A configuration change affecting new account onboarding caused some customers signing up for a dbt State or dbt Wizard trial to be unable to create a project or proceed past the billing setup step. This impacted new trial sign-ups between 2026-09-03 11:48 UTC and 2026-09-03 12:53 UTC. The issue was resolved and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience issues or have any follow-up questions.</description></item><item><title>Delayed metadata ingestion and Discovery API latency [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-09-02T15:00:59Z</guid><pubDate>Wed, 02 Sep 2026 15:00:59 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 1:45 PM Eastern. Between 7:05 AM Eastern and 1:45 PM Eastern an issue with delayed metadata impacted the Discovery (Metadata) API in our EU2 region. We have put measures in place to prevent a recurrence and metadata ingestion has returned to normal. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>support@getdbt.com address not found [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-26T15:58:36Z</guid><pubDate>Wed, 26 Aug 2026 15:58:36 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [support@getdbt.com](mailto:support@getdbt.com &quot;support@getdbt.com&quot;) email resulted in customers receiving &quot;address not found&quot; errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [support@getdbt.com](mailto:support@getdbt.com &quot;support@getdbt.com&quot;) email has returned to normal.</description></item><item><title>Intermittent Databricks connection Errors [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-25T04:23:49Z</guid><pubDate>Tue, 25 Aug 2026 04:23:49 +0000</pubDate><description>This incident is resolved. Connections to Databricks warehouses in our AU region returned to normal operation at approximately August 25, 04:07 UTC, and we have seen no further errors since.

 

Development sessions in the IDE and job runs that rely on Databricks credentials are operating normally.

Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.</description></item><item><title>Degraded Discovery API performance [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-24T15:44:38Z</guid><pubDate>Mon, 24 Aug 2026 15:44:38 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 3:00PM UTC.</description></item><item><title>Studio AI assistant (Wizard) tool errors [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-18T09:15:44Z</guid><pubDate>Tue, 18 Aug 2026 09:15:44 +0000</pubDate><description>A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.</description></item><item><title>Git Failures in dbt Platform [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-17T15:02:37Z</guid><pubDate>Mon, 17 Aug 2026 15:02:37 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx &quot;https://www.githubstatus.com/incidents/zkxwbgr0cnmx&quot;)

Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience issues and are unsure of the root cause.</description></item><item><title>ai-codegen-api-increased-error-rate [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-13T20:18:44Z</guid><pubDate>Thu, 13 Aug 2026 20:18:44 +0000</pubDate><description>This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored.

Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>Potential intermittent admin APIs requests failing [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-10T23:26:19Z</guid><pubDate>Mon, 10 Aug 2026 23:26:19 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. 

Between 10 Aug 22:16 - 23:33 UTC an issue with our platform&#x27;s memory resulted in intermittent 500 or 502 errors with admin APIs requests.


We have put measures in place to prevent a recurrence and the admin API requests have returned to normal.

Please contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>Fusion Stable: BigQuery incremental model builds affected [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-08-09T16:25:44Z</guid><pubDate>Sun, 09 Aug 2026 16:25:44 +0000</pubDate><description>A regression in a recent Fusion build affecting the BigQuery adapter led to incremental models being rebuilt from empty instead of updating incrementally. This impacted some customers using BigQuery as their connected data warehouse with cross-project execution/target configurations between August 4, 2026 at 20:00 UTC and August 9, 2026 at 17:15 UTC. The affected Fusion build was rolled back to the last known-good version, and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience issues or have any follow-up questions</description></item><item><title>AI Codegen (Wizard) unavailable in EMEA [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-29T09:12:59Z</guid><pubDate>Wed, 29 Jul 2026 09:12:59 +0000</pubDate><description>Since our last update, we&#x27;ve continued to monitor AI Codegen (Wizard) in EMEA and error rates have remained normal. As of 09:16 UTC, 29 July 2026, this incident is resolved. </description></item><item><title>Certificate errors affecting the dbt platform [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-27T18:25:19Z</guid><pubDate>Mon, 27 Jul 2026 18:25:19 +0000</pubDate><description>A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or &quot;insecure connection&quot; warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.</description></item><item><title>Scheduled jobs are intermittently affected by job failures caused by 403 error [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-24T07:58:08Z</guid><pubDate>Fri, 24 Jul 2026 07:58:08 +0000</pubDate><description>Intermittent job run failures during the git repository clone step affected our EMEA infrastructure. This impacted job runs between 2026-07-24 00:00 UTC and 2026-07-24 11:08 UTC. The issue has not recurred for over 3.5 hours and all affected systems are functioning normally. Please contact Support at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience issues or have any follow-up questions.</description></item><item><title>Unable to create or edit environment variables in dbt platform user interface [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-22T01:52:14Z</guid><pubDate>Wed, 22 Jul 2026 01:52:14 +0000</pubDate><description>The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. 

Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. 

Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience issues and are unsure of the root cause.</description></item><item><title>Job runs failing at the git clone step [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-21T10:23:29Z</guid><pubDate>Tue, 21 Jul 2026 10:23:29 +0000</pubDate><description>This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the &quot;Clone git repository&quot; step due to an upstream GitHub incident affecting SSH deploy key authentication.

GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried.

We apologize for the disruption and thank you for your patience.</description></item><item><title>Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-19T07:33:02Z</guid><pubDate>Sun, 19 Jul 2026 07:33:02 +0000</pubDate><description>**Update — 13:52 UTC**

Git clone errors on prod-emea have not recurred and success rates have remained normal. We have not identified a definitive root cause on our side and are continuing to investigate internally. We are resolving this incident, but will follow up if new information becomes available.</description></item><item><title>Studio IDE experiencing issues [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-16T23:48:09Z</guid><pubDate>Thu, 16 Jul 2026 23:48:09 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. We have confirmed that the impact was as a result of a GitHub outage: &lt;https://www.githubstatus.com/incidents/gxycch3076xk&gt;
Please contact Support via email [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>Intermittent slowness on login.dbt.com and loading account information [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-10T12:19:55Z</guid><pubDate>Fri, 10 Jul 2026 12:19:55 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 10:50 UTC. Between 09:40 UTC and 10:50 UTC, an issue affecting [login.dbt.com](http://login.dbt.com) and account discovery resulted in intermittent slowness when signing in and loading account information. We have put measures in place to prevent a recurrence and the affected services have 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.</description></item><item><title>Minor delay in job runs starting [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-07-07T00:55:07Z</guid><pubDate>Tue, 07 Jul 2026 00:55:07 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>us1.dbt.com is unreachable and showing &#x27;something went wrong&#x27; [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-06-30T21:57:06Z</guid><pubDate>Tue, 30 Jun 2026 21:57:06 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 5:12PM Eastern. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>Brief API unavailability [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-06-29T04:47:31Z</guid><pubDate>Mon, 29 Jun 2026 04:47:31 +0000</pubDate><description>From 24 June 2:00 PM UTC to 25 June 2:00 PM UTC, users may have experienced latency or brief unavailability in API requests. These may have resulted in failed API requests, or job runs statuses not updating correctly. The issue has since been resolved and there should be no further impact. Please contact us at support@getdbt.com with any questions or concerns. We thank you for your patience and understanding.</description></item><item><title>Snowflake Authentication failure in Development environments if the Account name has an &#x27;_&#x27; [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-06-24T16:14:34Z</guid><pubDate>Wed, 24 Jun 2026 16:14:34 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. 
 Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>LSP connection errors in Studio [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-06-19T17:19:42Z</guid><pubDate>Fri, 19 Jun 2026 17:19:42 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item><item><title>Login Distruption [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-06-19T08:52:14Z</guid><pubDate>Fri, 19 Jun 2026 08:52:14 +0000</pubDate><description>The issue has been resolved, and all affected systems are functioning normally . Between 04:00 EST and 04:53 EST an issue with  the Global Login Service resulted in  customers unable to login. Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience any issues regarding this.</description></item><item><title>Customer login access disruption [resolved]</title><link>https://status.getdbt.com</link><guid isPermaLink="false">dbt-cloud:2026-06-19T06:16:14Z</guid><pubDate>Fri, 19 Jun 2026 06:16:14 +0000</pubDate><description>The issue has been resolved, and all affected systems are now functioning normally. Between 19 Jun 00:00 - 06:50 UTC, an issue with login resulted in users receiving &quot;Access denied&quot; error at authentication. 

We have put measures in place to prevent a recurrence and all system has returned to normal. 

Please contact Support via email [support@getdbt.com](http://support@getdbt.com &quot;support@getdbt.com&quot;) if you continue to experience delays and are unsure of the root cause.</description></item></channel></rss>