dbt Cloud Outage History

dbt Cloud is up right now

dbt Cloud had 438 outages in the last 2 years — averaging 18 incidents per month.

There were 438 dbt Cloud outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor February 25, 2026

[US Cell 4 AWS] Compare changes job step failing for Databricks users

Detected by Pingoru
Feb 25, 2026, 06:46 PM UTC
Resolved
Feb 25, 2026, 06:46 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 24, 2026, 10:27 PM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

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

    Status: Identified 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. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components Scheduled Jobs (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor February 24, 2026

[US AWS] Platform instability affecting runs, Studio, and CLI

Detected by Pingoru
Feb 24, 2026, 09:53 PM UTC
Resolved
Feb 24, 2026, 09:53 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Feb 24, 2026, 09:52 PM UTC

    Status: Identified 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. Affected components Semantic Layer API (US AWS) (Operational) Metadata Ingestion (US AWS) (Operational) dbt platform CLI (US AWS) (Full outage) Web Application (US AWS) (Operational) IDE (US AWS) (Full outage) dbt Copilot (US AWS) (Operational) Admin API (US AWS) (Operational) Scheduled Jobs (US AWS) (Full outage) Metadata API (US AWS) (Operational)

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

    Status: Resolved 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. Affected components Metadata Ingestion (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Metadata API (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) IDE (US AWS) (Operational) dbt Copilot (US AWS) (Operational) Admin API (US AWS) (Operational) Semantic Layer API (US AWS) (Operational) Web Application (US AWS) (Operational)

Read the full incident report →

Minor February 24, 2026

[US Cell 1 AWS] Cloud CLI server impacted by transient DNS resolution error

Detected by Pingoru
Feb 24, 2026, 04:05 PM UTC
Resolved
Feb 24, 2026, 04:05 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Feb 24, 2026, 04:02 PM UTC

    Status: Monitoring 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. Affected components dbt platform CLI (US Cell 1 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components dbt platform CLI (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 24, 2026

[US Cell 2 AWS] Cloud CLI server impacted by transient DNS resolution error

Detected by Pingoru
Feb 24, 2026, 04:05 PM UTC
Resolved
Feb 24, 2026, 04:05 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Feb 24, 2026, 04:02 PM UTC

    Status: Monitoring 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. Affected components dbt platform CLI (US Cell 2 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components dbt platform CLI (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 24, 2026

[US Cell 3 AWS] Cloud CLI server impacted by transient DNS resolution error

Detected by Pingoru
Feb 24, 2026, 04:05 PM UTC
Resolved
Feb 24, 2026, 04:05 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Feb 24, 2026, 04:02 PM UTC

    Status: Monitoring 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. Affected components dbt platform CLI (US Cell 3 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components dbt platform CLI (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor February 23, 2026

[US Cell 2 AWS] Studio and CLI Invocation Failures

Detected by Pingoru
Feb 23, 2026, 08:32 PM UTC
Resolved
Feb 23, 2026, 08:32 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 23, 2026, 08:32 PM UTC

    Status: Resolved 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. Affected components IDE (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 22, 2026

[US Cell 2 AWS] Scheduled Job Run Cancellations

Detected by Pingoru
Feb 22, 2026, 02:07 AM UTC
Resolved
Feb 22, 2026, 02:07 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Feb 22, 2026, 12:09 AM UTC

    Status: Identified 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. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

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

    Status: Resolved 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. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 21, 2026

[US Cell 1 AWS] Runs are failing to complete

Detected by Pingoru
Feb 21, 2026, 02:13 PM UTC
Resolved
Feb 21, 2026, 02:13 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 21, 2026, 01:28 PM UTC

    Status: Investigating 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. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

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

    Status: Monitoring Our engineers has taken steps to restore normal service Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

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

    Status: Resolved 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. Affected components Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[APAC AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (APAC AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (APAC AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (APAC AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[EMEA AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (EMEA AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EMEA AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[EMEA Cell 1 AZURE] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 18, 2026

[EU Cell 1 GCP] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (EU Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EU Cell 1 GCP) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 18, 2026

[EU4 Cell 1 GCP] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (EU4 Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EU4 Cell 1 GCP) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 18, 2026

[JP Cell 1 AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (JP Cell 1 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (JP Cell 1 AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[US AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[US Cell 1 AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US Cell 1 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US Cell 1 AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[US Cell 1 AZURE] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US Cell 1 AZURE) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US Cell 1 AZURE) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 18, 2026

[US Cell 1 GCP] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US Cell 1 GCP) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor February 18, 2026

[US Cell 2 AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US Cell 2 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US Cell 2 AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[US Cell 3 AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US Cell 3 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US Cell 3 AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor February 18, 2026

[US Cell 4 AWS] Failure Creating Managed Git Repos

Detected by Pingoru
Feb 18, 2026, 10:56 PM UTC
Resolved
Feb 18, 2026, 10:56 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 18, 2026, 06:10 PM UTC

    Status: Investigating 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

    Status: Investigating 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

    Status: Identified 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. Affected components Web Application (US Cell 4 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (US Cell 4 AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor February 17, 2026

[US Cell 2 AWS] Intermittent Job Failures

Detected by Pingoru
Feb 17, 2026, 10:14 PM UTC
Resolved
Feb 17, 2026, 10:14 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 17, 2026, 10:14 PM UTC

    Status: Resolved Starting at approximately 2:14 PM PST, some customers may have experienced job failures with the error message “Unexpected acquire failure.” Affected jobs may have failed to start or stalled during execution. The underlying issue has been identified and resolved. Systems are now operating normally, and jobs should now run successfully. Affected components Metadata Ingestion (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational) Admin API (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational) Semantic Layer API (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Operational) dbt Copilot (US Cell 2 AWS) (Operational) Web Application (US Cell 2 AWS) (Operational) Metadata API (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor February 16, 2026

[APAC AWS] Outbound Webhooks missing dispatches

Detected by Pingoru
Feb 16, 2026, 11:01 AM UTC
Resolved
Feb 16, 2026, 11:01 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 16, 2026, 11:01 AM UTC

    Status: Resolved Between Feb 16 12:01 UTC and Feb 17 9:56 UTC we experienced an issue with outbound webhooks not being dispatched for some accounts due to an unexpected issue with one of the underlying mechanisms. This issue has since been identified and resolved. We apologise for any inconveniences this may have caused. Please contacts us at [email protected] with any questions or concerns. Affected components Web Application (APAC AWS) (Operational) dbt Copilot (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational) Semantic Layer (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational) Admin API (APAC AWS) (Operational) IDE (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational) Metadata Ingestion (APAC AWS) (Operational)

Read the full incident report →

Minor February 14, 2026

[US AWS] Small number of scheduled run are cancelled

Detected by Pingoru
Feb 14, 2026, 05:43 PM UTC
Resolved
Feb 14, 2026, 05:43 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 14, 2026, 05:19 PM UTC

    Status: Investigating We're identified an issue with Scheduler pickup that is causing very small number of runs to be cancelled. This is impacting scheduled runs in US Multi tenant region between 16:30 to 16:35 UTC. The impact is minimal and only effected a few runs and the issue seems to be resolved and we are monitoring. The Impacted cancelled run need to be retried as a workaround. Please reach out to [email protected] "[email protected]": mailto:[email protected] for any further queries or clarifications. Affected components Scheduled Jobs (US AWS) (Degraded performance)

  2. monitoring Feb 14, 2026, 05:23 PM UTC

    Status: Monitoring The issue impacting scheduled runs in the US multi-tenant region between 16:30 and 16:35 UTC is now resolved. The runs have returned to normal, and we are continuing to monitor. The Impacted cancelled run Affected components Scheduled Jobs (US AWS) (Degraded performance)

  3. resolved Feb 14, 2026, 05:43 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 16:35 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →