dbt Cloud Outage History

dbt Cloud is up right now

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

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

Source: https://status.getdbt.com

Minor June 10, 2026

[APAC AWS] Increased Error rate for dbt Cloud API

Detected by Pingoru
Jun 10, 2026, 02:18 PM UTC
Resolved
Jun 10, 2026, 02:18 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 10, 2026, 02:18 PM UTC

    Status: Resolved Between 14:11-14:18 UTC, we experienced a brief degraded performance that impacted API and dbt Cloud Platform. All impacted components have been operating as normally since and we have preventative measures in place. We apologise for the inconvenience caused. Please contact us at [email protected] with any questions or concerns. Affected components dbt Copilot (APAC AWS) (Operational) Semantic Layer (APAC AWS) (Operational) Metadata Ingestion (APAC AWS) (Operational) IDE (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational) Web Application (APAC AWS) (Operational) Admin API (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational)

Read the full incident report →

Minor June 6, 2026

[US AWS] Discovery API returning stale data

Detected by Pingoru
Jun 06, 2026, 12:03 AM UTC
Resolved
Jun 06, 2026, 12:03 AM UTC
Duration
—
Timeline · 2 updates
  1. investigating Jun 05, 2026, 10:42 PM UTC

    Status: Investigating We're investigating an issue with the Discovery API that is causing stale data. This is impacting systems using metadata, such as dbt Catalog and dbt Mesh, in US MT anytime after 10:30 PM UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. All other systems are not impacted and should be running as expected. Affected components Metadata API (US AWS) (Degraded performance)

  2. resolved Jun 06, 2026, 12:03 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 12:00 AM 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 Metadata API (US AWS) (Operational)

Read the full incident report →

Minor June 4, 2026

[EMEA AWS] Brief API unavailability and potential job run impacts

Detected by Pingoru
Jun 04, 2026, 12:11 AM UTC
Resolved
Jun 04, 2026, 12:11 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 04, 2026, 12:11 AM UTC

    Status: Resolved Between 00:11–00:12 UTC, we experienced a brief degraded performance that impacted API availability and had a potential impact on some job runs. All impacted components have been operating as normally since and we have preventative measures in place. We apologise for the inconvenience caused. Please contact us at [email protected] with any questions or concerns. Affected components IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Metadata Ingestion (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) dbt Copilot (EMEA AWS) (Operational) Metadata API (EMEA AWS) (Operational) Semantic Layer (EMEA AWS) (Operational) Admin API (EMEA AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[APAC AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (APAC AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (APAC AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (APAC AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (APAC AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[EMEA AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (EMEA AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (EMEA AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (EMEA AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[EMEA Cell 1 AZURE] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 31, 2026

[EU Cell 1 GCP] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (EU Cell 1 GCP) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU Cell 1 GCP) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (EU Cell 1 GCP) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 31, 2026

[EU4 Cell 1 GCP] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 31, 2026

[JP Cell 1 AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (JP Cell 1 AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (JP Cell 1 AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (JP Cell 1 AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[US AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[US Cell 1 AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US Cell 1 AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US Cell 1 AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[US Cell 1 AZURE] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US Cell 1 AZURE) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AZURE) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US Cell 1 AZURE) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 31, 2026

[US Cell 1 GCP] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US Cell 1 GCP) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 GCP) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US Cell 1 GCP) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 31, 2026

[US Cell 2 AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US Cell 2 AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 2 AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US Cell 2 AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[US Cell 3 AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US Cell 3 AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 3 AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US Cell 3 AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor May 31, 2026

[US Cell 4 AWS] Compile button error in Studio IDE

Detected by Pingoru
May 31, 2026, 08:37 PM UTC
Resolved
May 31, 2026, 08:37 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 07:22 PM UTC

    Status: Investigating We're investigating an issue with compiling on Fusion versions that is causing dbt9002: Failed to find compiled SQL. This is impacting the Studio IDE anytime after 2 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. Affected components IDE (US Cell 4 AWS) (Degraded performance)

  2. identified May 29, 2026, 08:07 PM UTC

    Status: Identified We have identified an issue with the Studio IDE that resulted in the compile button erroring on Fusion-Latest. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 4 AWS) (Degraded performance)

  3. monitoring May 29, 2026, 09:29 PM UTC

    Status: Monitoring We are deploying a fix for the compile button that is causing the failed to find compiled SQL error. We will continue to monitor and provide updates as the fix rolls out. Affected components IDE (US Cell 4 AWS) (Degraded performance)

  4. resolved May 31, 2026, 08:37 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7am 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 IDE (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor May 28, 2026

[APAC AWS] dbt1410 warnings

Detected by Pingoru
May 28, 2026, 09:22 PM UTC
Resolved
May 28, 2026, 09:22 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 28, 2026, 05:36 PM UTC

    Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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. Affected components IDE (APAC AWS) (Degraded performance) Scheduled Jobs (APAC AWS) (Degraded performance)

  2. identified May 28, 2026, 06:01 PM UTC

    Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)

  3. monitoring May 28, 2026, 06:09 PM UTC

    Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)

  4. resolved May 28, 2026, 09:22 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence and Scheduled Jobs have 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 28, 2026

[EMEA AWS] dbt1410 warnings

Detected by Pingoru
May 28, 2026, 09:22 PM UTC
Resolved
May 28, 2026, 09:22 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 28, 2026, 05:36 PM UTC

    Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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. Affected components IDE (EMEA AWS) (Degraded performance) Scheduled Jobs (EMEA AWS) (Degraded performance)

  2. identified May 28, 2026, 06:01 PM UTC

    Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  3. monitoring May 28, 2026, 06:09 PM UTC

    Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  4. resolved May 28, 2026, 09:22 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence and Scheduled Jobs have 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 28, 2026

[EMEA Cell 1 AZURE] dbt1410 warnings

Detected by Pingoru
May 28, 2026, 09:22 PM UTC
Resolved
May 28, 2026, 09:22 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 28, 2026, 05:36 PM UTC

    Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance) IDE (EMEA Cell 1 AZURE) (Degraded performance)

  2. identified May 28, 2026, 06:01 PM UTC

    Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)

  3. monitoring May 28, 2026, 06:09 PM UTC

    Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)

  4. resolved May 28, 2026, 09:22 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence and Scheduled Jobs have 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 28, 2026

[EU Cell 1 GCP] dbt1410 warnings

Detected by Pingoru
May 28, 2026, 09:22 PM UTC
Resolved
May 28, 2026, 09:22 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 28, 2026, 05:36 PM UTC

    Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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. Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance) IDE (EU Cell 1 GCP) (Degraded performance)

  2. identified May 28, 2026, 06:01 PM UTC

    Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)

  3. monitoring May 28, 2026, 06:09 PM UTC

    Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)

  4. resolved May 28, 2026, 09:22 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence and Scheduled Jobs have 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 28, 2026

[EU4 Cell 1 GCP] dbt1410 warnings

Detected by Pingoru
May 28, 2026, 09:22 PM UTC
Resolved
May 28, 2026, 09:22 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 28, 2026, 05:36 PM UTC

    Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance) Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)

  2. identified May 28, 2026, 06:01 PM UTC

    Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)

  3. monitoring May 28, 2026, 06:09 PM UTC

    Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)

  4. resolved May 28, 2026, 09:22 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence and Scheduled Jobs have 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 →