dbt Cloud Outage History

dbt Cloud is up right now

There were 292 dbt Cloud outages since February 4, 2026 totaling 6h 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor April 16, 2026

[APAC AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (APAC AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (APAC AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (APAC AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (APAC AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[EMEA AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (EMEA AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (EMEA AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (EMEA AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[EMEA Cell 1 AZURE] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (EMEA Cell 1 AZURE) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor April 16, 2026

[EU Cell 1 GCP] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (EU Cell 1 GCP) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU Cell 1 GCP) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (EU Cell 1 GCP) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 16, 2026

[EU4 Cell 1 GCP] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU4 Cell 1 GCP) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (EU4 Cell 1 GCP) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 16, 2026

[JP Cell 1 AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (JP Cell 1 AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (JP Cell 1 AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (JP Cell 1 AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[US AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[US Cell 1 AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US Cell 1 AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US Cell 1 AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[US Cell 1 AZURE] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US Cell 1 AZURE) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AZURE) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US Cell 1 AZURE) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor April 16, 2026

[US Cell 1 GCP] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US Cell 1 GCP) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 GCP) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US Cell 1 GCP) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 16, 2026

[US Cell 2 AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US Cell 2 AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 2 AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US Cell 2 AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[US Cell 3 AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US Cell 3 AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 3 AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US Cell 3 AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor April 16, 2026

[US Cell 4 AWS] Latest versions of files not showing recent commits in Studio

Detected by Pingoru
Apr 16, 2026, 07:24 PM UTC
Resolved
Apr 16, 2026, 07:24 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 16, 2026, 05:04 PM UTC

    Status: Investigating We're investigating an issue with dbt Studio that is causing stale versions of files to display in Studio despite new changes being recently committed. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components IDE (US Cell 4 AWS) (Degraded performance)

  2. identified Apr 16, 2026, 06:26 PM UTC

    Status: Identified We have identified an issue with browser caching behaviors that resulted in stale versions of files displaying in Studio despite new changes being recently committed. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 4 AWS) (Degraded performance)

  3. monitoring Apr 16, 2026, 06:58 PM UTC

    Status: Monitoring We have deployed a fix for Studio that was causing stale versions of files to display in Studio despite new changes being recently committed. Studio has returned to its normal state and we are continuing to monitor. Please note that you will need to refresh your Studio session for the fix to be applied. Affected components IDE (US Cell 4 AWS) (Operational)

  4. resolved Apr 16, 2026, 07:24 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 19:24 UTC. An issue with browser caching in dbt Studio resulted in stale versions of files to display in Studio despite new changes being recently committed . We have put measures in place to prevent a recurrence and dbt Studio 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 IDE (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor April 13, 2026

[EMEA AWS] Failed or broken AI responses in Copilot

Detected by Pingoru
Apr 13, 2026, 06:50 PM UTC
Resolved
Apr 13, 2026, 06:50 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Apr 13, 2026, 03:50 PM UTC

    Status: Identified Beginning 3:50pm UTC some users saw errors when using AI features in dbt Platform (dbt Copilot in Studio), and affected interactions did not complete as expected. The issue was caused by an issue with how our AI service handled cancelled requests, which could leave conversations in an invalid state. Affected components Admin API (EMEA AWS) (Operational) dbt Copilot (EMEA AWS) (Degraded performance) Semantic Layer (EMEA AWS) (Operational) Metadata Ingestion (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational) IDE (EMEA AWS) (Operational) Metadata API (EMEA AWS) (Operational)

  2. resolved Apr 13, 2026, 06:50 PM UTC

    Status: Resolved On April 13, 2026 we deployed a fix to correct this behavior and improved our validation to prevent similar errors going forward. Affected components Metadata API (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) dbt Copilot (EMEA AWS) (Operational) Metadata Ingestion (EMEA AWS) (Operational) IDE (EMEA AWS) (Operational) Semantic Layer (EMEA AWS) (Operational) Admin API (EMEA AWS) (Operational)

Read the full incident report →

Minor April 13, 2026

[EU Cell 1 GCP] Failed or broken AI responses in Copilot

Detected by Pingoru
Apr 13, 2026, 06:50 PM UTC
Resolved
Apr 13, 2026, 06:50 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Apr 13, 2026, 03:50 PM UTC

    Status: Identified Beginning 3:50pm UTC some users saw errors when using AI features in dbt Platform (dbt Copilot in Studio), and affected interactions did not complete as expected. The issue was caused by an issue with how our AI service handled cancelled requests, which could leave conversations in an invalid state. Affected components IDE (EU Cell 1 GCP) (Operational) Semantic Layer API (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational) Metadata Ingestion (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational) Metadata API (EU Cell 1 GCP) (Operational) Admin API (EU Cell 1 GCP) (Operational) dbt platform CLI (EU Cell 1 GCP) (Operational) dbt Copilot (EU Cell 1 GCP) (Degraded performance)

  2. resolved Apr 13, 2026, 06:50 PM UTC

    Status: Resolved On April 13, 2026 we deployed a fix to correct this behavior and improved our validation to prevent similar errors going forward. Affected components dbt platform CLI (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational) Metadata API (EU Cell 1 GCP) (Operational) Metadata Ingestion (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational) dbt Copilot (EU Cell 1 GCP) (Operational) Semantic Layer API (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational) Admin API (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 13, 2026

[US Cell 1 AWS] Failed or broken AI responses in Copilot

Detected by Pingoru
Apr 13, 2026, 06:50 PM UTC
Resolved
Apr 13, 2026, 06:50 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Apr 13, 2026, 03:50 PM UTC

    Status: Identified Beginning 3:50pm UTC some users saw errors when using AI features in dbt Platform (dbt Copilot in Studio), and affected interactions did not complete as expected. The issue was caused by an issue with how our AI service handled cancelled requests, which could leave conversations in an invalid state. Affected components Admin API (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational) dbt Copilot (US Cell 1 AWS) (Degraded performance) Scheduled Jobs (US Cell 1 AWS) (Operational) Metadata API (US Cell 1 AWS) (Operational) Metadata Ingestion (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational) Semantic Layer API (US Cell 1 AWS) (Operational)

  2. resolved Apr 13, 2026, 06:50 PM UTC

    Status: Resolved On April 13, 2026 we deployed a fix to correct this behavior and improved our validation to prevent similar errors going forward. Affected components dbt platform CLI (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) Admin API (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational) Metadata Ingestion (US Cell 1 AWS) (Operational) Semantic Layer API (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational) Metadata API (US Cell 1 AWS) (Operational) dbt Copilot (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor April 13, 2026

[US Cell 3 AWS] Failed or broken AI responses in Copilot

Detected by Pingoru
Apr 13, 2026, 06:50 PM UTC
Resolved
Apr 13, 2026, 06:50 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Apr 13, 2026, 03:50 PM UTC

    Status: Identified Beginning 3:50pm UTC some users saw errors when using AI features in dbt Platform (dbt Copilot in Studio), and affected interactions did not complete as expected. The issue was caused by an issue with how our AI service handled cancelled requests, which could leave conversations in an invalid state. Affected components IDE (US Cell 3 AWS) (Operational) Web Application (US Cell 3 AWS) (Operational) Metadata API (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational) Admin API (US Cell 3 AWS) (Operational) Semantic Layer API (US Cell 3 AWS) (Operational) Metadata Ingestion (US Cell 3 AWS) (Operational) dbt Copilot (US Cell 3 AWS) (Degraded performance)

  2. resolved Apr 13, 2026, 06:50 PM UTC

    Status: Resolved On April 13, 2026 we deployed a fix to correct this behavior and improved our validation to prevent similar errors going forward. Affected components Admin API (US Cell 3 AWS) (Operational) Metadata Ingestion (US Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Operational) Web Application (US Cell 3 AWS) (Operational) dbt Copilot (US Cell 3 AWS) (Operational) Metadata API (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational) Semantic Layer API (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor April 11, 2026

[EMEA Cell 1 AZURE] Runs not Starting

Detected by Pingoru
Apr 11, 2026, 07:20 AM UTC
Resolved
Apr 11, 2026, 07:20 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Apr 11, 2026, 06:53 AM UTC

    Status: Investigating We're investigating an issue with scheduled jobs that is causing jobs not to start. This is impacting Scheduled Jobs in EMEA Azure anytime after 02:08 time 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. All other components are not impacted and should be running as expected. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)

  2. monitoring Apr 11, 2026, 07:04 AM UTC

    Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing runs not to start. EMEA Azure has returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)

  3. resolved Apr 11, 2026, 07:20 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of [H:MM time Eastern]. Between 02:08 Eastern and 03:03 Eastern an issue with Scheduled Runs resulted in jobs not starting. We have put measures in place to prevent a recurrence and the Scheduled Runs 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 April 10, 2026

[APAC AWS] "Something went wrong" message displaying on dbt Platform job pages

Detected by Pingoru
Apr 10, 2026, 11:35 PM UTC
Resolved
Apr 10, 2026, 11:35 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 10, 2026, 10:08 PM UTC

    Status: Investigating We're investigating an issue with a recent release to the web application that is causing the message "Something went wrong" to display on job pages in dbt Platform. This is impacting the job pages in the UI anytime after 21:24 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Web Application (APAC AWS) (Partial outage) Scheduled Jobs (APAC AWS) (Partial outage)

  2. identified Apr 10, 2026, 10:29 PM UTC

    Status: Identified We have identified an issue with a recent release to the web application that resulted in job pages in the UI returning a "Something went wrong" message when accessed. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (APAC AWS) (Partial outage) Scheduled Jobs (APAC AWS) (Partial outage)

  3. monitoring Apr 10, 2026, 11:07 PM UTC

    Status: Monitoring We have deployed a fix for the web application that was causing job pages in the UI to fail to load with "Something went wrong" errors. The UI is returning to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (APAC AWS) (Partial outage) Web Application (APAC AWS) (Partial outage)

  4. resolved Apr 10, 2026, 11:35 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7:30 PM Eastern. Between 4:15 PM Eastern and 6:30 PM Eastern an issue with the web application resulted in job pages failing to load due to error "Something went wrong" . We have put measures in place to prevent a recurrence and the web application 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 Web Application (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational)

Read the full incident report →

Minor April 10, 2026

[EMEA AWS] "Something went wrong" message displaying on dbt Platform job pages

Detected by Pingoru
Apr 10, 2026, 11:35 PM UTC
Resolved
Apr 10, 2026, 11:35 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 10, 2026, 10:08 PM UTC

    Status: Investigating We're investigating an issue with a recent release to the web application that is causing the message "Something went wrong" to display on job pages in dbt Platform. This is impacting the job pages in the UI anytime after 21:24 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA AWS) (Partial outage) Web Application (EMEA AWS) (Partial outage)

  2. identified Apr 10, 2026, 10:29 PM UTC

    Status: Identified We have identified an issue with a recent release to the web application that resulted in job pages in the UI returning a "Something went wrong" message when accessed. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA AWS) (Partial outage) Web Application (EMEA AWS) (Partial outage)

  3. monitoring Apr 10, 2026, 11:07 PM UTC

    Status: Monitoring We have deployed a fix for the web application that was causing job pages in the UI to fail to load with "Something went wrong" errors. The UI is returning to its normal state and we are continuing to monitor. Affected components Web Application (EMEA AWS) (Partial outage) Scheduled Jobs (EMEA AWS) (Partial outage)

  4. resolved Apr 10, 2026, 11:35 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7:30 PM Eastern. Between 4:15 PM Eastern and 6:30 PM Eastern an issue with the web application resulted in job pages failing to load due to error "Something went wrong" . We have put measures in place to prevent a recurrence and the web application 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) Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor April 10, 2026

[EMEA Cell 1 AZURE] "Something went wrong" message displaying on dbt Platform job pages

Detected by Pingoru
Apr 10, 2026, 11:35 PM UTC
Resolved
Apr 10, 2026, 11:35 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 10, 2026, 10:08 PM UTC

    Status: Investigating We're investigating an issue with a recent release to the web application that is causing the message "Something went wrong" to display on job pages in dbt Platform. This is impacting the job pages in the UI anytime after 21:24 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Web Application (EMEA Cell 1 AZURE) (Partial outage) Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage)

  2. identified Apr 10, 2026, 10:29 PM UTC

    Status: Identified We have identified an issue with a recent release to the web application that resulted in job pages in the UI returning a "Something went wrong" message when accessed. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage) Web Application (EMEA Cell 1 AZURE) (Partial outage)

  3. monitoring Apr 10, 2026, 11:07 PM UTC

    Status: Monitoring We have deployed a fix for the web application that was causing job pages in the UI to fail to load with "Something went wrong" errors. The UI is returning to its normal state and we are continuing to monitor. Affected components Web Application (EMEA Cell 1 AZURE) (Partial outage) Scheduled Jobs (EMEA Cell 1 AZURE) (Partial outage)

  4. resolved Apr 10, 2026, 11:35 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7:30 PM Eastern. Between 4:15 PM Eastern and 6:30 PM Eastern an issue with the web application resulted in job pages failing to load due to error "Something went wrong" . We have put measures in place to prevent a recurrence and the web application 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) Web Application (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Looking to track dbt Cloud downtime and outages?

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

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

5 free monitors · No credit card required