dbt Cloud Outage History

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 May 22, 2026

[EMEA AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EMEA AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EMEA AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (EMEA AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EMEA AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[EMEA Cell 1 AZURE] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 22, 2026

[EU Cell 1 GCP] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EU Cell 1 GCP) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EU Cell 1 GCP) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (EU Cell 1 GCP) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EU Cell 1 GCP) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 22, 2026

[EU4 Cell 1 GCP] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EU4 Cell 1 GCP) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EU4 Cell 1 GCP) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (EU4 Cell 1 GCP) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (EU4 Cell 1 GCP) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 22, 2026

[JP Cell 1 AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (JP Cell 1 AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (JP Cell 1 AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (JP Cell 1 AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (JP Cell 1 AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[US AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 1 AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US Cell 1 AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 1 AZURE] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 AZURE) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 AZURE) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US Cell 1 AZURE) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 AZURE) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 1 GCP] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 GCP) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 GCP) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US Cell 1 GCP) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 1 GCP) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 2 AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 2 AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 2 AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US Cell 2 AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 2 AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 3 AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 3 AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 3 AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US Cell 3 AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 3 AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 4 AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 4 AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 4 AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (US Cell 4 AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (US Cell 4 AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[US Cell 1 AZURE] Elevated errors affecting Studio IDE sessions – US Azure region

Detected by Pingoru: May 22, 2026, 08:03 PM UTC
Resolved: May 22, 2026, 08:03 PM UTC
Duration: —

Timeline · 4 updates

investigating May 22, 2026, 06:53 PM UTC

Status: Investigating We're investigating an issue with the dbt platform CLI Server that is causing elevated 5xx errors for Studio IDE sessions. This is impacting the dbt platform IDE in US Multi-Cell Azure. The team is working on a resolution as soon as new information becomes available. Job runs are not impacted and should be running as expected. Affected components IDE (US Cell 1 AZURE) (Degraded performance) dbt platform CLI (US Cell 1 AZURE) (Degraded performance)
identified May 22, 2026, 07:18 PM UTC

Status: Identified We have identified an issue with the dbt platform CLI Server that resulted in errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 1 AZURE) (Degraded performance) IDE (US Cell 1 AZURE) (Degraded performance)
monitoring May 22, 2026, 07:21 PM UTC

Status: Monitoring We have deployed a fix for the dbt platform CLI Server that was causing errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. The Studio IDE has returned to its normal state and we are continuing to monitor. Affected components IDE (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational)
resolved May 22, 2026, 08:03 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 3:22 PM Eastern. Between 2:53 PM Eastern and 3:22 PM Eastern an issue with the dbt platform CLI Server resulted in errors when loading Studio IDE sessions for customers in the US Multi-Cell Azure region. The Studio IDE has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 15, 2026

[APAC AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (APAC AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (APAC AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (APAC AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 (APAC AWS) (Operational)

Read the full incident report →

Minor May 15, 2026

[EMEA AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (EMEA AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EMEA AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 (EMEA AWS) (Operational)

Read the full incident report →

Minor May 15, 2026

[EMEA Cell 1 AZURE] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 15, 2026

[EU Cell 1 GCP] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (EU Cell 1 GCP) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EU Cell 1 GCP) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 15, 2026

[EU4 Cell 1 GCP] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 15, 2026

[JP Cell 1 AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (JP Cell 1 AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (JP Cell 1 AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (JP Cell 1 AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 15, 2026

[US AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 AWS) (Operational)

Read the full incident report →

Minor May 15, 2026

[US Cell 1 AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 1 AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 May 15, 2026

[US Cell 1 AZURE] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 1 AZURE) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AZURE) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 AZURE) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 AZURE) (Operational)

Read the full incident report →

Minor May 15, 2026

[US Cell 1 GCP] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 1 GCP) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 GCP) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 GCP) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 GCP) (Operational)

Read the full incident report →

Minor May 15, 2026

[US Cell 2 AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 2 AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 2 AWS) (Operational)

Read the full incident report →

Minor May 15, 2026

[US Cell 3 AWS] dbt Platform CI Outage for AzureDevOps Integrations

Detected by Pingoru: May 15, 2026, 09:09 PM UTC
Resolved: May 15, 2026, 09:09 PM UTC
Duration: —

Timeline · 4 updates

investigating May 15, 2026, 06:23 PM UTC

Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM 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. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 3 AWS) (Partial outage)
identified May 15, 2026, 06:38 PM UTC

Status: Identified We have identified an issue with a recent change to the ADO integration that resulted in CI issues in the dbt Platform UI. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 3 AWS) (Partial outage)
monitoring May 15, 2026, 07:34 PM UTC

Status: Monitoring We have deployed a fix for integration that was causing issues with CI in the dbt Platform for ADO users. CI triggers and the UI has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 3 AWS) (Operational)
resolved May 15, 2026, 09:09 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs 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 3 AWS) (Operational)

Read the full incident report →