dbt Cloud Outage History

There were 292 dbt Cloud outages since February 4, 2026 totaling 4h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor March 5, 2026

[EU4 Cell 1 GCP] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[JP Cell 1 AWS] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US AWS] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US Cell 1 AWS] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US Cell 1 AZURE] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US Cell 1 GCP] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US Cell 2 AWS] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US Cell 3 AWS] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 5, 2026

[US Cell 4 AWS] Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 05, 2026, 03:49 AM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

Linting Error from Request Dependency Warning

Detected by Pingoru: Mar 04, 2026, 11:04 PM UTC
Resolved: Mar 05, 2026, 03:49 AM UTC
Duration: 4h 44m

Read the full incident report →

Minor March 4, 2026

[APAC AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[EMEA AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[EMEA Cell 1 AZURE] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[EU Cell 1 GCP] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[EU4 Cell 1 GCP] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[JP Cell 1 AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[US AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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)

Read the full incident report →

Minor March 4, 2026

[US Cell 1 AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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 (US Cell 1 AWS) (Degraded performance) Scheduled Jobs (US 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 (US Cell 1 AWS) (Operational) IDE (US 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 Scheduled Jobs (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 4, 2026

[US Cell 1 AZURE] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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 (US Cell 1 AZURE) (Degraded performance) Scheduled Jobs (US 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 (US Cell 1 AZURE) (Operational) Scheduled Jobs (US 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 Scheduled Jobs (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 4, 2026

[US Cell 1 GCP] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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 Cell 1 GCP) (Degraded performance) IDE (US 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 (US Cell 1 GCP) (Operational) Scheduled Jobs (US 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 Scheduled Jobs (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 4, 2026

[US Cell 2 AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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 (US Cell 2 AWS) (Degraded performance) Scheduled Jobs (US Cell 2 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 Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 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 (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor March 4, 2026

[US Cell 3 AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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 Cell 3 AWS) (Degraded performance) IDE (US Cell 3 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 Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 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 Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor March 4, 2026

[US Cell 4 AWS] "Table Not Found in Schema" error in Latest Fusion Release v2.0.0-preview.143

Detected by Pingoru: Mar 04, 2026, 06:23 PM UTC
Resolved: Mar 04, 2026, 06:23 PM UTC
Duration: —

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 (US Cell 4 AWS) (Degraded performance) Scheduled Jobs (US Cell 4 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 (US Cell 4 AWS) (Operational) IDE (US Cell 4 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 Cell 4 AWS) (Operational) IDE (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor March 3, 2026

Degraded performance with Codegen AI

Detected by Pingoru: Mar 03, 2026, 11:19 PM UTC
Resolved: Mar 03, 2026, 11:11 PM UTC
Duration: —

Read the full incident report →

Minor March 3, 2026

[APAC AWS] Degraded performance with Codegen AI

Detected by Pingoru: Mar 03, 2026, 11:11 PM UTC
Resolved: Mar 03, 2026, 11:11 PM UTC
Duration: —

Timeline · 2 updates

identified Mar 03, 2026, 10:00 PM UTC

Status: Identified Between the hours of 9:30pm UTC and 10:15pm UTC, we experienced n issue with our legacy text-to-sql. This issue also appears to have impacted users of the text_to_sql dbt MCP tool. Affected components Metadata Ingestion (APAC AWS) (Operational) Web Application (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational) Semantic Layer (APAC AWS) (Operational) dbt Copilot (APAC AWS) (Degraded performance) IDE (APAC AWS) (Operational) Admin API (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational)
resolved Mar 03, 2026, 11:11 PM 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 Copilot (APAC AWS) (Operational) Semantic Layer (APAC AWS) (Operational) Web Application (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational) IDE (APAC AWS) (Operational) Admin API (APAC AWS) (Operational) Metadata Ingestion (APAC AWS) (Operational)

Read the full incident report →

Looking to track dbt Cloud downtime and outages?

Pingoru polls dbt Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when dbt Cloud reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track dbt Cloud alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring dbt Cloud for free

5 free monitors · No credit card required