dbt Cloud Outage History
dbt Cloud is up right nowPingoru has recorded 767 incidents for dbt Cloud: 767 in the last 12 months and 210 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 82 | 70 of 720 (10%) |
| May 2026 | 126 | 155 of 744 (21%) |
| June 2026 | 55 | 40 of 720 (6%) |
| July 2026 | 81 | 29 of 744 (4%) |
| August 2026 | 78 | 22 of 744 (3%) |
| September 2026 | 77 | 53 of 720 (7%) |
| October 2026 | 44 | 69 of 592 (12%) |
Incidents, newest first
Minor May 15, 2026 [US Cell 1 GCP] dbt Platform CI Outage for AzureDevOps Integrations 2h 45m
Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC
- 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.
- 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.
- 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.
- 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.
Minor May 15, 2026 [US Cell 2 AWS] dbt Platform CI Outage for AzureDevOps Integrations 2h 45m
Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC
- 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.
- 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.
- 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.
- 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.
Minor May 15, 2026 [US Cell 3 AWS] dbt Platform CI Outage for AzureDevOps Integrations 2h 45m
Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC
- 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.
- 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.
- 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.
- 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.
Minor May 15, 2026 [US Cell 4 AWS] dbt Platform CI Outage for AzureDevOps Integrations 2h 45m
Started May 15, 2026, 06:23 PM UTC· resolved May 15, 2026, 09:09 PM UTC
- 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.
- 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.
- 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.
- 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.
Minor May 15, 2026 [APAC AWS] dbt Platform CLI State Selector Failing 2h 2m
Started May 15, 2026, 02:18 PM UTC· resolved May 15, 2026, 04:20 PM UTC
- monitoring May 15, 2026, 04:17 PM UTC
We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 15, 2026, 04:20 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. 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.
- investigating May 15, 2026, 04:24 PM UTC
We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 15, 2026, 04:37 PM UTC
We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). A fix is being implemented, and we will provide an update shortly.
Minor May 15, 2026 [EMEA AWS] dbt Platform CLI State Selector Failing 2h 2m
Started May 15, 2026, 02:18 PM UTC· resolved May 15, 2026, 04:20 PM UTC
- monitoring May 15, 2026, 04:17 PM UTC
We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 15, 2026, 04:20 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. 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.
- investigating May 15, 2026, 04:24 PM UTC
We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 15, 2026, 04:37 PM UTC
We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). A fix is being implemented, and we will provide an update shortly.
Minor May 15, 2026 [US Cell 2 AWS] dbt Platform CLI State Selector Failing 2h 2m
Started May 15, 2026, 02:18 PM UTC· resolved May 15, 2026, 04:20 PM UTC
- monitoring May 15, 2026, 04:17 PM UTC
We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 15, 2026, 04:20 PM UTC
The issue has been resolved, and all affected systems are now functioning normally. 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.
- investigating May 15, 2026, 04:24 PM UTC
We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). The team is working on a resolution and we will provide updates as soon as new information becomes available.
- identified May 15, 2026, 04:37 PM UTC
We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). A fix is being implemented, and we will provide an update shortly.
Minor May 12, 2026 [APAC AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [EMEA AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [EMEA Cell 1 AZURE] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [EU Cell 1 GCP] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [EU4 Cell 1 GCP] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [JP Cell 1 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US Cell 1 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US Cell 1 AZURE] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US Cell 1 GCP] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US Cell 2 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US Cell 3 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 12, 2026 [US Cell 4 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." 1h 18m
Started May 12, 2026, 07:30 AM UTC· resolved May 12, 2026, 08:49 AM UTC
- investigating May 12, 2026, 07:30 AM UTC
We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."
- monitoring May 12, 2026, 08:27 AM UTC
We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns.
- resolved May 12, 2026, 08:49 AM UTC
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 [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.
Minor May 11, 2026 [APAC AWS] dbt Studio issues with previewing and compiling code –
Started May 11, 2026, 10:26 PM UTC· resolved May 11, 2026, 10:26 PM UTC
- resolved May 11, 2026, 10:26 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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.
Minor May 11, 2026 [EMEA AWS] dbt Studio issues with previewing and compiling code –
Started May 11, 2026, 10:26 PM UTC· resolved May 11, 2026, 10:26 PM UTC
- resolved May 11, 2026, 10:26 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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.
Minor May 11, 2026 [EMEA Cell 1 AZURE] dbt Studio issues with previewing and compiling code –
Started May 11, 2026, 10:26 PM UTC· resolved May 11, 2026, 10:26 PM UTC
- resolved May 11, 2026, 10:26 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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.
Minor May 11, 2026 [EU Cell 1 GCP] dbt Studio issues with previewing and compiling code –
Started May 11, 2026, 10:26 PM UTC· resolved May 11, 2026, 10:26 PM UTC
- resolved May 11, 2026, 10:26 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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.
Minor May 11, 2026 [EU4 Cell 1 GCP] dbt Studio issues with previewing and compiling code –
Started May 11, 2026, 10:26 PM UTC· resolved May 11, 2026, 10:26 PM UTC
- resolved May 11, 2026, 10:26 PM UTC
The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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.