dbt Cloud Outage History

Started May 22, 2026, 06:53 PM UTC· resolved May 22, 2026, 08:03 PM UTC

1. investigating May 22, 2026, 06:53 PM UTC

   We're investigating an issue with the dbt platform CLI Server that is causing elevated 5xx errors for Studio IDE sessions. This is impacting the dbt platform IDE in US Multi-Cell Azure. The team is working on a resolution as soon as new information becomes available. Job runs are not impacted and should be running as expected.

2. identified May 22, 2026, 07:18 PM UTC

   We have identified an issue with the dbt platform CLI Server that resulted in errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 22, 2026, 07:21 PM UTC

   We have deployed a fix for the dbt platform CLI Server that was causing errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. The Studio IDE has returned to its normal state and we are continuing to monitor.

4. resolved May 22, 2026, 08:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 3:22 PM Eastern. Between 2:53 PM Eastern and 3:22 PM Eastern an issue with the dbt platform CLI Server resulted in errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. The Studio IDE has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 06:15 PM UTC· resolved May 22, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:22 PM UTC

   We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

2. monitoring May 22, 2026, 04:44 PM UTC

   The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

3. identified May 22, 2026, 07:23 PM UTC

   We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly.

4. monitoring May 22, 2026, 08:57 PM UTC

   Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected.

5. resolved May 22, 2026, 09:04 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 04:59 PM UTC· resolved May 25, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:59 PM UTC

   We're investigating an issue with the Snowflake adapter on the Latest release track that is causing some dbt jobs to fail when fetching large query result sets. The Snowflake connector is hitting a 7-second connection timeout while retrieving result data from Snowflake's internal storage, surfacing in run logs as: "Failed to fetch the large result set batch data_1 ... ConnectTimeoutError ... timed out (connect timeout=7)" This is impacting jobs running on the Latest release track in deployments using Snowflake. The team is investigating the underlying cause and will provide updates at approximately 15-minute intervals as new information becomes available. Workaround Switching affected jobs to the Compatible or Extended release track resolves the failures immediately. For production workloads, we recommend Extended going forward as the most stable option.

2. identified May 22, 2026, 06:09 PM UTC

   We have identified an issue with a recent Snowflake adapter release that resulted in some dbt jobs failing when fetching large query result sets. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 25, 2026, 06:43 PM UTC

   We have deployed a fix for the Snowflake adapter that resulted in some dbt jobs failing when fetching large query result sets. We are continuing to monitor.

4. resolved May 25, 2026, 09:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence and the Snowflake adapter has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 22, 2026, 04:59 PM UTC· resolved May 25, 2026, 09:03 PM UTC

1. investigating May 22, 2026, 04:59 PM UTC

   We're investigating an issue with the Snowflake adapter on the Latest release track that is causing some dbt jobs to fail when fetching large query result sets. The Snowflake connector is hitting a 7-second connection timeout while retrieving result data from Snowflake's internal storage, surfacing in run logs as: "Failed to fetch the large result set batch data_1 ... ConnectTimeoutError ... timed out (connect timeout=7)" This is impacting jobs running on the Latest release track in deployments using Snowflake. The team is investigating the underlying cause and will provide updates at approximately 15-minute intervals as new information becomes available. Workaround Switching affected jobs to the Compatible or Extended release track resolves the failures immediately. For production workloads, we recommend Extended going forward as the most stable option.

2. identified May 22, 2026, 06:09 PM UTC

   We have identified an issue with a recent Snowflake adapter release that resulted in some dbt jobs failing when fetching large query result sets. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 25, 2026, 06:43 PM UTC

   We have deployed a fix for the Snowflake adapter that resulted in some dbt jobs failing when fetching large query result sets. We are continuing to monitor.

4. resolved May 25, 2026, 09:03 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence and the Snowflake adapter has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC

1. investigating May 15, 2026, 06:23 PM UTC

   We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected.

2. identified May 15, 2026, 06:38 PM UTC

   We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly.

3. monitoring May 15, 2026, 07:34 PM UTC

   We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor.

4. resolved May 15, 2026, 09:09 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →