dbt Cloud Outage History

Started Feb 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

1. investigating Feb 24, 2026, 10:27 PM UTC

   We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Feb 24, 2026, 11:07 PM UTC

   We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

3. resolved Feb 25, 2026, 06:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

1. investigating Feb 24, 2026, 10:27 PM UTC

   We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Feb 24, 2026, 11:07 PM UTC

   We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

3. resolved Feb 25, 2026, 06:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

1. investigating Feb 24, 2026, 10:27 PM UTC

   We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Feb 24, 2026, 11:07 PM UTC

   We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

3. resolved Feb 25, 2026, 06:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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 24, 2026, 10:27 PM UTC· resolved Feb 25, 2026, 06:46 PM UTC

1. investigating Feb 24, 2026, 10:27 PM UTC

   We're investigating an issue with advanced CI that is causing the compare changes step of CI jobs to fail for users of the Databricks adapter. The team is working on a resolution and we will provide updates as soon as new information becomes available.

2. identified Feb 24, 2026, 11:07 PM UTC

   We have identified an issue with partial success handling in advanced CI that resulted the compare changes step of CI jobs to fail for users of the Databricks adapter. A fix is being implemented, and we will provide an update shortly.

3. resolved Feb 25, 2026, 06:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 17:25 UTC. We have put measures in place to prevent a recurrence and the compare changes step of advanced CI jobs for Databricks users 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 24, 2026, 09:52 PM UTC· resolved Feb 24, 2026, 09:53 PM UTC

1. identified Feb 24, 2026, 09:52 PM UTC

   We have identified an issue impacting run execution and Studio and Cloud CLI functionality. A fix is currently being implemented. We will share another update as soon as more information becomes available.

2. resolved Feb 24, 2026, 09:53 PM UTC

   Between 24 Feb 21:52-21:53 UTC, we experienced platform instability that resulted in newly triggered runs to time out and be cancelled, Studio to fail to launch and Cloud CLI commands to fail. The issue has since been resolved. We have implemented measures to help prevent a recurrence and all platform features are operating normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] with any further questions.

Read the full incident report →

Started Feb 24, 2026, 04:02 PM UTC· resolved Feb 24, 2026, 04:05 PM UTC

1. monitoring Feb 24, 2026, 04:02 PM UTC

   We're investigating an issue with cloud CLI that caused a transient DNS resolution failure for the Cloud CLI server for a small number of customer. This is impacted Cloud CLI servers were in (us-c1, us-c2, us-c3) instances anytime between 10:00 AM EST and between 11:00 AM EST.

2. resolved Feb 24, 2026, 04:05 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of11:00 AM EST. Between 10:00 AM EST and 11:00 AM ESTan issue with cloud CLI resulted in a small number of customers requests failing. We have put measures in place to prevent a recurrence and the cloud CLI 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 24, 2026, 04:02 PM UTC· resolved Feb 24, 2026, 04:05 PM UTC

1. monitoring Feb 24, 2026, 04:02 PM UTC

   We're investigating an issue with cloud CLI that caused a transient DNS resolution failure for the Cloud CLI server for a small number of customer. This is impacted Cloud CLI servers were in (us-c1, us-c2, us-c3) instances anytime between 10:00 AM EST and between 11:00 AM EST.

2. resolved Feb 24, 2026, 04:05 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of11:00 AM EST. Between 10:00 AM EST and 11:00 AM ESTan issue with cloud CLI resulted in a small number of customers requests failing. We have put measures in place to prevent a recurrence and the cloud CLI 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 24, 2026, 04:02 PM UTC· resolved Feb 24, 2026, 04:05 PM UTC

1. monitoring Feb 24, 2026, 04:02 PM UTC

   We're investigating an issue with cloud CLI that caused a transient DNS resolution failure for the Cloud CLI server for a small number of customer. This is impacted Cloud CLI servers were in (us-c1, us-c2, us-c3) instances anytime between 10:00 AM EST and between 11:00 AM EST.

2. resolved Feb 24, 2026, 04:05 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of11:00 AM EST. Between 10:00 AM EST and 11:00 AM ESTan issue with cloud CLI resulted in a small number of customers requests failing. We have put measures in place to prevent a recurrence and the cloud CLI 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 23, 2026, 08:32 PM UTC· resolved Feb 23, 2026, 08:32 PM UTC

1. resolved Feb 23, 2026, 08:32 PM UTC

   Starting at approximately 19:03 UTC, some customers may have experienced dbt invocation failures. This impacted some Studio IDE and CLI invocations, resulting in "internal error" messages. The underlying issue has been identified and resolved. Systems are now operating normally, and invocations should now run successfully.

Read the full incident report →

Started Feb 22, 2026, 12:09 AM UTC· resolved Feb 22, 2026, 02:07 AM UTC

1. identified Feb 22, 2026, 12:09 AM UTC

   We have identified an issue with Scheduled Jobs in the US Cell 2 AWS environment, resulting in run cancellations with the following error: "This run timed out after 10 minutes of inactivity." A fix is actively being implemented, and we will provide an update as soon as more information becomes available.

2. monitoring Feb 22, 2026, 12:15 AM UTC

   We have deployed a fix for Scheduled Jobs in the US Cell 2 AWS environment that was causing run cancellations. Scheduled Jobs have returned to their normal state and we are continuing to monitor.

3. resolved Feb 22, 2026, 02:07 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with Scheduled Jobs in the US Cell 2 AWS environment resulted in run cancellations. We have put measures in place to prevent a recurrence and Scheduled Jobs have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Feb 21, 2026, 04:37 PM UTC· resolved Feb 22, 2026, 03:19 AM UTC

1. investigating Feb 21, 2026, 04:37 PM UTC

   We're investigating an issue with orchestration that is causing run failures. This is impacting Scheduled Jobs anytime after 11:00 AM Eastern. 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. investigating Feb 21, 2026, 05:05 PM UTC

   We're continuing to investigate an issue with orchestration resulting in run failures for deployment jobs on the dbt Platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

3. identified Feb 21, 2026, 05:39 PM UTC

   We have identified an issue with Scheduled Jobs that is resulting in run failures. A fix is being implemented, and we will provide an update shortly.

4. identified Feb 21, 2026, 06:34 PM UTC

   The identified issue with Scheduled Jobs is also causing run delays in addition to run failures with the output of "Internal Error." We are working on implementing a fix and we will provide an update shortly.

5. identified Feb 21, 2026, 07:39 PM UTC

   We are continuing to work on implementing a fix, and we will provide additional updates as more information becomes available.

6. monitoring Feb 21, 2026, 07:51 PM UTC

   We have deployed a fix for Scheduled Jobs that was causing run start delays and run failures. Runs are starting to return to a normal state and error rates are decreasing. We are continuing to monitor.

7. identified Feb 21, 2026, 08:28 PM UTC

   We continue to see impacts on Scheduled Jobs resulting in run cancellations, run failures, and run delays due to the ongoing incident. A fix is being implemented, and we will continue to provide updates as soon as more information becomes available.

8. identified Feb 21, 2026, 09:19 PM UTC

   We have identified an issue with the Studio IDE as part of this ongoing incident that is resulting in IDE sessions not starting. A fix is being implemented, and we will provide an update shortly.

9. identified Feb 21, 2026, 11:01 PM UTC

   We are continuing to work on implementing a fix, and we will provide an update as soon as more information is available.

10. identified Feb 22, 2026, 12:20 AM UTC

    We are continuing to work on implementing a fix, and we will provide an update as soon as more information is available.

11. monitoring Feb 22, 2026, 02:11 AM UTC

    We have deployed a fix for Scheduled Jobs that was causing run failures, run delays, run cancellations, and IDE sessions not starting. Scheduled Jobs and the Studio IDE have returned to their normal state and we are continuing to monitor.

12. resolved Feb 22, 2026, 03:19 AM UTC

    The issue has been resolved, and all affected systems are now functioning normally. An issue with Scheduled Jobs resulted in run failures, run delays, run cancellations, and IDE sessions not starting. We have put measures in place to prevent a recurrence and Scheduled Jobs and the Studio IDE have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Feb 21, 2026, 01:28 PM UTC· resolved Feb 21, 2026, 02:13 PM UTC

1. investigating Feb 21, 2026, 01:28 PM UTC

   We're investigating an issue with jobs that is causing runs to fail. This is impacting some customers in US1 C1 anytime after 07:30 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available. [X component/system] is not impacted and should be running as expected.

2. monitoring Feb 21, 2026, 01:55 PM UTC

   Our engineers has taken steps to restore normal service

3. resolved Feb 21, 2026, 02:13 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 09:15 Eastern. Between 07:30 Eastern and 09:30 Eastern with runs resulted in some customer jobs failing . We have put measures in place to prevent a recurrence and the service 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 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →

Started Feb 18, 2026, 06:10 PM UTC· resolved Feb 18, 2026, 10:56 PM UTC

1. investigating Feb 18, 2026, 06:10 PM UTC

   We're investigating an issue with Git integrations that is causing an error when attempting to create managed repos. This is impacting all instances anytime after 12:45 Eastern. The team is working on a resolution and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Feb 18, 2026, 06:33 PM UTC

   The team have taken steps to mitigate the issue and are currently working to restore normal functionality.

3. identified Feb 18, 2026, 08:40 PM UTC

   We have identified an issue with dbt Managed Repo hit a threshold limit of total repos, this resulted in dbt users attempting to create new dbt Managed Repos being denied the ability to create a new Repo. A fix has been implemented and functionality has been restored.

4. monitoring Feb 18, 2026, 08:47 PM UTC

   We have deployed a fix for dbt Managed Repo creation that was causing Managed Repos to be denied from being created. dbt Managed Repos creation has returned to its normal state and we are continuing to monitor.

5. resolved Feb 18, 2026, 10:56 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. An issue with dbt Managed Repos resulted in users being unable to create new managed repositories due to a repository threshold limit being reached. dbt Managed Repo creation has returned to normal operation. Please contact Support via email at [email protected] "[email protected]": mailto:[email protected] if you continue to experience issues or are unsure about the root cause.

Read the full incident report →