dbt Cloud Outage History

dbt Cloud is up right now

dbt Cloud had 438 outages in the last 2 years totaling 6h 14m of downtime — averaging 18 incidents per month.

There were 438 dbt Cloud outages since January 27, 2026 totaling 6h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor April 18, 2026

[JP Cell 1 AWS] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[US AWS] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US AWS) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US AWS) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[US Cell 1 AWS] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[US Cell 1 AZURE] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor April 18, 2026

[US Cell 1 GCP] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 18, 2026

[US Cell 2 AWS] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[US Cell 3 AWS] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[US Cell 4 AWS] Job Run logs unavailable

Detected by Pingoru
Apr 18, 2026, 05:56 PM UTC
Resolved
Apr 18, 2026, 05:56 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Apr 18, 2026, 02:01 PM UTC

    Status: Investigating We're investigating an issue with Job Run logs that is resulting in "No logs found". The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

  2. identified Apr 18, 2026, 02:13 PM UTC

    Status: Identified We have identified an issue that prevented Job Runs from pulling in debug logs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

  3. identified Apr 18, 2026, 03:28 PM UTC

    Status: Identified We have released an update that will resolve the missing logs issue for new job runs. We are actively working on a fix for existing job runs that are currently missing logs. We will provide an update on this fix shortly. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

  4. resolved Apr 18, 2026, 05:56 PM UTC

    Status: Resolved The issue has been resolved, and all Job Run logs should be available as of 5:50 pm UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 4 AWS) (Operational)

Read the full incident report →

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 →