dbt Cloud Outage History

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 10:00 PM UTC· resolved Mar 03, 2026, 11:11 PM UTC

1. identified Mar 03, 2026, 10:00 PM UTC

   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.

2. resolved Mar 03, 2026, 11:11 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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 01:29 PM UTC· resolved Mar 04, 2026, 06:23 PM UTC

1. investigating Mar 03, 2026, 01:29 PM UTC

   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.

2. monitoring Mar 03, 2026, 04:37 PM UTC

   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.

3. resolved Mar 04, 2026, 06:23 PM UTC

   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.

Read the full incident report →

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

1. investigating Feb 26, 2026, 03:17 PM UTC

   We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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.

2. monitoring Feb 26, 2026, 04:00 PM UTC

   We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

3. resolved Feb 26, 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.

Read the full incident report →

Started Feb 26, 2026, 03:17 PM UTC· resolved Feb 26, 2026, 04:20 PM UTC

1. investigating Feb 26, 2026, 03:17 PM UTC

   We're investigating an issue that may cause background errors in some features like Insights. At this time, core functionality of Insights remains unaffected. 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.

2. monitoring Feb 26, 2026, 04:00 PM UTC

   We have deployed a fix for that was causing background errors when accessing Insights. It has returned to its normal state and we are continuing to monitor.

3. resolved Feb 26, 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.

Read the full incident report →