dbt Cloud Outage History

There were 292 dbt Cloud outages since February 4, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

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

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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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.
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.
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)
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)
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

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

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

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)
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)
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 →

Minor February 12, 2026

[APAC AWS] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (APAC AWS) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (APAC AWS) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

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

Read the full incident report →

Minor February 12, 2026

[EMEA AWS] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (EMEA AWS) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (EMEA AWS) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

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

Read the full incident report →

Minor February 12, 2026

[EMEA Cell 1 AZURE] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (EMEA Cell 1 AZURE) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (EMEA Cell 1 AZURE) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components dbt Copilot (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 12, 2026

[US AWS] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (US AWS) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (US AWS) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

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

Read the full incident report →

Minor February 12, 2026

[US Cell 1 AWS] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (US Cell 1 AWS) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (US Cell 1 AWS) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

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

Read the full incident report →

Minor February 12, 2026

[US Cell 1 AZURE] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (US Cell 1 AZURE) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (US Cell 1 AZURE) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components dbt Copilot (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor February 12, 2026

[US Cell 2 AWS] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (US Cell 2 AWS) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (US Cell 2 AWS) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

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

Read the full incident report →

Minor February 12, 2026

[US Cell 3 AWS] dbt Copilot SQL generation failures across all regions

Detected by Pingoru: Feb 12, 2026, 06:15 PM UTC
Resolved: Feb 12, 2026, 06:15 PM UTC
Duration: —

Timeline · 3 updates

identified Feb 12, 2026, 03:00 PM UTC

Status: Identified We have identified an issue with dbt Copilot that is causing failures when generating SQL due to an ongoing OpenAI incident. Other Copilot functionality is not impacted. The team is working on a resolution and we will provide updates as soon as new information becomes available. OpenAI status page: https://status.openai.com/ Affected components dbt Copilot (US Cell 3 AWS) (Partial outage)
monitoring Feb 12, 2026, 05:52 PM UTC

Status: Monitoring We have confirmed that OpenAI has recovered and Copilot SQL generation is functioning again. We are continuing to monitor error rates and performance to ensure the service remains stable. Affected components dbt Copilot (US Cell 3 AWS) (Operational)
resolved Feb 12, 2026, 06:15 PM UTC

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

Read the full incident report →

Looking to track dbt Cloud downtime and outages?

Pingoru polls dbt Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when dbt Cloud reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track dbt Cloud alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring dbt Cloud for free

5 free monitors · No credit card required