dbt Cloud Outage History

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 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 17, 2026, 03:02 PM UTC· resolved Aug 17, 2026, 09:21 PM UTC

1. investigating Aug 17, 2026, 03:02 PM UTC

   We're investigating an issue with GitHub that is causing failures across multiple components including dbt deps and repository connections. This is impacting the Studio IDE and Scheduled Jobs anytime after 9:30 AM Eastern. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 03:51 PM UTC

   An ongoing GitHub outage is causing intermittent failures across parts of the dbt platform including Scheduled Jobs and the Studio IDE. Some users may also run into errors when trying to authenticate to GitHub or connect repositories. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/zkxwbgr0cnmx We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Aug 17, 2026, 05:31 PM UTC

   The degradation affecting git services has been mitigated. Error rates are continuing to decrease and we are continuing to monitor for full resolution on the impacted systems.

4. resolved Aug 17, 2026, 09:21 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 9:30 AM Eastern and 5 PM Eastern a widespread GitHub outage resulted in multiple failures across git services within dbt Platform. https://www.githubstatus.com/incidents/zkxwbgr0cnmx Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 Aug 13, 2026, 08:18 PM UTC· resolved Aug 13, 2026, 11:33 PM UTC

1. investigating Aug 13, 2026, 08:18 PM UTC

   We're investigating an issue affecting AI agent runs in dbt Copilot and dbt Studio. Users may see errors or failed responses when running agent requests, and conversations that have already hit the error may continue to fail. Other areas of the dbt platform, including the IDE, job orchestration, and MCP connections, 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 13, 2026, 08:26 PM UTC

   We have identified an issue affecting AI agent runs in dbt Copilot and dbt Studio caused by a change in an upstream service. A fix is being implemented and we will provide an update shortly.

3. identified Aug 13, 2026, 10:06 PM UTC

   Our initial change reduced the underlying error rate but did not resolve the issue. AI agent functionality in dbt Copilot and dbt Studio remains unavailable. We are continuing to work on a fix and will provide another update as soon as more information becomes available.

4. monitoring Aug 13, 2026, 11:03 PM UTC

   A fix has been deployed and AI agent functionality in dbt Copilot and dbt Studio has recovered and we are continuing to monitor.

5. resolved Aug 13, 2026, 11:33 PM UTC

   This issue has been resolved. AI agent functionality in dbt Copilot and dbt Studio is fully restored. 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 →