dbt Cloud Outage History
dbt Cloud is up right nowdbt Cloud had 438 outages in the last 2 years totaling 7h 46m of downtime — averaging 18 incidents per month.
There were 438 dbt Cloud outages since January 27, 2026 totaling 7h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.
[EU Cell 1 GCP] Connectivity Errors When Starting dbt Studio and Deployment Runs
Timeline · 3 updates
- investigating Mar 05, 2026, 03:57 PM UTC
Status: Investigating We are investigating an intermittent issue with an internal service that is causing connectivity failures. As a result, some users in the GCP US and EMEA regions may experience: 1. Failures when starting dbt Studio sessions 2. Delays when executing or cancelling deployment runs This behavior has been observed starting around 10:18 AM Eastern. Our engineering team is actively working on a resolution. We will post the next update in approximately 15 minutes, or sooner if new information becomes available. Affected components IDE (EU Cell 1 GCP) (Full outage) Scheduled Jobs (EU Cell 1 GCP) (Full outage)
- monitoring Mar 05, 2026, 05:11 PM UTC
Status: Monitoring We have deployed a fix for connectivity issues in an internal service that was causing failures in starting dbt Studio and delays in executing/canceling deployment runs. Both dbt Studio and scheduled jobs have returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)
- resolved Mar 05, 2026, 06:55 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-03-05 8:06 PM EST. Between 10:18 AM EST and 8:06 PM EST an issue with an internal service resulted in failures in starting dbt Studio and scheduled jobs . We have put measures in place to prevent a recurrence and the dbt Studio and scheduled jobs have 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. Affected components IDE (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational)
[US Cell 1 GCP] Connectivity Errors When Starting dbt Studio and Deployment Runs
Timeline · 3 updates
- investigating Mar 05, 2026, 03:57 PM UTC
Status: Investigating We are investigating an intermittent issue with an internal service that is causing connectivity failures. As a result, some users in the GCP US and EMEA regions may experience: 1. Failures when starting dbt Studio sessions 2. Delays when executing or cancelling deployment runs This behavior has been observed starting around 10:18 AM Eastern. Our engineering team is actively working on a resolution. We will post the next update in approximately 15 minutes, or sooner if new information becomes available. Affected components IDE (US Cell 1 GCP) (Full outage) Scheduled Jobs (US Cell 1 GCP) (Full outage)
- monitoring Mar 05, 2026, 05:11 PM UTC
Status: Monitoring We have deployed a fix for connectivity issues in an internal service that was causing failures in starting dbt Studio and delays in executing/canceling deployment runs. Both dbt Studio and scheduled jobs have returned to its normal state and we are continuing to monitor. Affected components IDE (US Cell 1 GCP) (Operational) Scheduled Jobs (US Cell 1 GCP) (Operational)
- resolved Mar 05, 2026, 06:55 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-03-05 8:06 PM EST. Between 10:18 AM EST and 8:06 PM EST an issue with an internal service resulted in failures in starting dbt Studio and scheduled jobs . We have put measures in place to prevent a recurrence and the dbt Studio and scheduled jobs have 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. Affected components IDE (US Cell 1 GCP) (Operational) Scheduled Jobs (US Cell 1 GCP) (Operational)
Connectivity Errors When Starting dbt Studio and Deployment Runs
[APAC AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (APAC AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (APAC AWS) (Operational) IDE (APAC AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational)
[EMEA AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)
[EMEA Cell 1 AZURE] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational)
[EU Cell 1 GCP] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU Cell 1 GCP) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components dbt platform CLI (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)
[EU4 Cell 1 GCP] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Operational)
[JP Cell 1 AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (JP Cell 1 AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components dbt platform CLI (JP Cell 1 AWS) (Operational) IDE (JP Cell 1 AWS) (Operational)
[US AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (US AWS) (Operational) IDE (US AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (US AWS) (Operational) dbt platform CLI (US AWS) (Operational)
[US Cell 1 AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)
[US Cell 1 AZURE] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AZURE) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational)
[US Cell 1 GCP] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 GCP) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (US Cell 1 GCP) (Operational) dbt platform CLI (US Cell 1 GCP) (Operational)
[US Cell 2 AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 2 AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational)
[US Cell 3 AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 3 AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (US Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components dbt platform CLI (US Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational)
[US Cell 4 AWS] Linting Error from Request Dependency Warning
Timeline · 3 updates
- identified Mar 04, 2026, 11:04 PM UTC
Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 4 AWS) (Degraded performance)
- monitoring Mar 05, 2026, 12:49 AM UTC
Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (US Cell 4 AWS) (Operational) dbt platform CLI (US Cell 4 AWS) (Operational)
- resolved Mar 05, 2026, 03:49 AM UTC
Status: Resolved 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. Affected components IDE (US Cell 4 AWS) (Operational) dbt platform CLI (US Cell 4 AWS) (Operational)
Linting Error from Request Dependency Warning
[APAC AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components IDE (APAC AWS) (Degraded performance) Scheduled Jobs (APAC AWS) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components IDE (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components Scheduled Jobs (APAC AWS) (Operational) IDE (APAC AWS) (Operational)
[EMEA AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components IDE (EMEA AWS) (Degraded performance) Scheduled Jobs (EMEA AWS) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components IDE (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components IDE (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational)
[EMEA Cell 1 AZURE] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance) IDE (EMEA Cell 1 AZURE) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components IDE (EMEA Cell 1 AZURE) (Operational) Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components IDE (EMEA Cell 1 AZURE) (Operational) Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)
[EU Cell 1 GCP] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance) IDE (EU Cell 1 GCP) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components IDE (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational)
[EU4 Cell 1 GCP] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance) Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components IDE (EU4 Cell 1 GCP) (Operational) Scheduled Jobs (EU4 Cell 1 GCP) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components IDE (EU4 Cell 1 GCP) (Operational) Scheduled Jobs (EU4 Cell 1 GCP) (Operational)
[JP Cell 1 AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance) IDE (JP Cell 1 AWS) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (JP Cell 1 AWS) (Operational) IDE (JP Cell 1 AWS) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components IDE (JP Cell 1 AWS) (Operational) Scheduled Jobs (JP Cell 1 AWS) (Operational)
[US AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143
Timeline · 3 updates
- investigating Mar 03, 2026, 01:29 PM UTC
Status: Investigating We're investigating an issue with the latest fusion release v2.0.0-preview.143 that is causing "Table Not Found" error message. This is impacting studio running in dbt-fusion after 02 March 2026 at 1PM EST. While we work on a resolution, our engineers have rolled back dbt-fusion to a previous state. We will provide more updates as they become available. Affected components Scheduled Jobs (US AWS) (Degraded performance) IDE (US AWS) (Degraded performance)
- monitoring Mar 03, 2026, 04:37 PM UTC
Status: Monitoring We have deployed a fix for latest dbt-fusion release that was causing "Table Not Found in Schema" errors. dbt Studio has returned to its normal state and we are continuing to monitor. Affected components IDE (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational)
- resolved Mar 04, 2026, 06:23 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:13 PM Eastern. Between March 02, 2026 1:00 PM Eastern and March 04, 2026 1:13PM Eastern an issue with Latest Fusion release v2.0.0-preview.143 resulted in "Table Not Found in Schema" errors in dbt Studio . We have put measures in place to prevent a recurrence and the dbt Studio 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. Affected components Scheduled Jobs (US AWS) (Operational) IDE (US AWS) (Operational)