dbt Cloud Outage History

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 26, 2026, 03:58 PM UTC· resolved Aug 26, 2026, 09:49 PM UTC

1. investigating Aug 26, 2026, 03:58 PM UTC

   We're investigating an issue with the [email protected] "[email protected]": mailto:[email protected] email that is causing "address not found" errors when trying to contact support. We are investigating further impacts with notifications downstream using this email address. 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. If you need to contact support, please use the [email protected] "[email protected]": mailto:[email protected] email instead.

2. investigating Aug 26, 2026, 04:14 PM UTC

   We have deployed a fix for the [email protected] "[email protected]": mailto:[email protected] email that was causing "address not found" errors when contacting support. Support emails to this address are being received now, and we are continuing to investigate additional impact that occurred.

3. monitoring Aug 26, 2026, 05:20 PM UTC

   Support emails from and to [email protected] "[email protected]": mailto:[email protected] have returned to its normal state and we are continuing to monitor.

4. resolved Aug 26, 2026, 09:49 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Between 11 AM Eastern, August 25th, and 12 PM Eastern, August 26th, an issue with the [email protected] "[email protected]": mailto:[email protected] email resulted in customers receiving "address not found" errors or unable to reach this email for support. We have put measures in place to prevent a recurrence and the [email protected] "[email protected]": mailto:[email protected] email has returned to normal.

Read the full incident report →

Started Aug 25, 2026, 04:23 AM UTC· resolved Aug 25, 2026, 04:59 AM UTC

1. investigating Aug 25, 2026, 04:23 AM UTC

   We are investigating an issue affecting some customers in the AU multi-tenant environment using Databricks connections. Impacted customers may see failed runs or IDE connection errors due to intermittent errors refreshing Databricks credential tokens. Our team is investigating and will provide another update as we learn more.

2. monitoring Aug 25, 2026, 04:46 AM UTC

   We have observed recovery for the issue affecting a some customers in our AU multi-tenant environment using Databricks connections. Errors have not recurred since 9:07 PM PDT / 12:07 PM AEST. We are continuing to monitor and will provide another update once the issue is fully resolved.

3. resolved Aug 25, 2026, 04:59 AM UTC

   This incident is resolved. Connections to Databricks warehouses in our AU region returned to normal operation at approximately August 25, 2:07 PM AEST (August 24, 9:07 PM PDT), and we have seen no further errors since. Development sessions in the IDE and job runs that rely on Databricks credentials are operating normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 24, 2026, 02:25 PM UTC· resolved Aug 24, 2026, 03:00 PM UTC

1. identified Aug 24, 2026, 02:25 PM UTC

   We have identified an issue with the Discovery API that may have resulted is failed API requests.. A fix has been implemented, and we will provide an update shortly.

2. resolved Aug 24, 2026, 03:00 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 3:00PM UTC.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Started Aug 18, 2026, 09:15 AM UTC· resolved Aug 18, 2026, 11:19 AM UTC

1. investigating Aug 18, 2026, 09:15 AM UTC

   We're investigating an issue with the Studio AI assistant (Wizard). Users may see errors or unexpected behavior when the assistant tries to read or edit project files, run git commands, or run dbt commands on their behalf. Studio itself, manual file editing, and running dbt commands directly are not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Aug 18, 2026, 10:04 AM UTC

   We have identified an issue with the Studio AI assistant (Wizard) that a recent deployment introduced, causing it to lose required parameters when using its tools. A fix has been identified and is currently being tested. We plan to deploy it as soon as testing is complete and will provide a further update shortly.

3. resolved Aug 18, 2026, 11:19 AM UTC

   A recent deployment to the Studio AI assistant (Wizard) caused it to lose required parameters when using its tools, resulting in failures for file reads and edits, git actions, and dbt commands run through the assistant. This impacted the Studio AI assistant across multiple multi-tenant instances between 2026-08-18 08:47 UTC and 2026-08-18 10:18 UTC. A fix has been released and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →