dbt Cloud Outage History

dbt Cloud is up right now

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

Source: https://status.getdbt.com

Minor May 1, 2026

[US AWS] jobs failing on dbt deps due to private packages

Detected by Pingoru
May 01, 2026, 01:00 AM UTC
Resolved
May 01, 2026, 01:00 AM UTC
Duration
—
Timeline · 2 updates
  1. identified Apr 30, 2026, 08:18 PM UTC

    Status: Identified We have identified an issue with private packages that resulted in jobs failing on the dbt deps step. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Full outage)

  2. resolved May 01, 2026, 01:00 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 01:00 UTC. Between 20:18 UTC and 01:00 UTC an issue with private packages resulted in dbt deps failures in job runs. We have put measures in place to prevent a recurrence and scheduled jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor April 24, 2026

[US Cell 1 AWS] FlightSQL authentication error on Semantic Layer failing with working service token

Detected by Pingoru
Apr 24, 2026, 12:04 AM UTC
Resolved
Apr 24, 2026, 12:04 AM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Apr 23, 2026, 11:59 PM UTC

    Status: Monitoring We have deployed a fix for the Semantic Layer that was causing service token authentication failures. The Semantic Layer has returned to its normal state and we are continuing to monitor. Affected components Semantic Layer API (US Cell 1 AWS) (Degraded performance)

  2. resolved Apr 24, 2026, 12:04 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 12:31 PM Eastern. Between 10:42 AM Eastern and 12:24 PM Eastern an issue with the Semantic Layer resulted in service token authentication failures . We have put measures in place to prevent a recurrence and the Semantic Layer 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 Semantic Layer API (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor April 22, 2026

[APAC AWS] Login Authentication code exchange failures

Detected by Pingoru
Apr 22, 2026, 08:53 PM UTC
Resolved
Apr 22, 2026, 08:53 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Apr 22, 2026, 07:19 PM UTC

    Status: Investigating We're investigating an issue with Authentication that is causing Logins to fail. This is impacting dbt Platform in EMEA and AU region between 18:35pm and 18:55pm UTC. The team is investigating. Affected components Web Application (APAC AWS) (Degraded performance)

  2. monitoring Apr 22, 2026, 07:25 PM UTC

    Status: Monitoring The suspected cause for the underlying issue is an outage with an upstream dependent system. A sharp decline in error rates and increasing login successes, indicating recovery is underway. Operational status has been confirmed with manual checks and successful logs, users are now able to log in again on the affected tenants. We are continuing to monitor this issue. Affected components Web Application (APAC AWS) (Operational)

  3. resolved Apr 22, 2026, 08:53 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Affected components Web Application (APAC AWS) (Operational)

Read the full incident report →

Minor April 22, 2026

[EMEA AWS] Login Authentication code exchange failures

Detected by Pingoru
Apr 22, 2026, 08:53 PM UTC
Resolved
Apr 22, 2026, 08:53 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Apr 22, 2026, 07:19 PM UTC

    Status: Investigating We're investigating an issue with Authentication that is causing Logins to fail. This is impacting dbt Platform in EMEA and AU region between 18:35pm and 18:55pm UTC. The team is investigating. Affected components Web Application (EMEA AWS) (Degraded performance)

  2. monitoring Apr 22, 2026, 07:25 PM UTC

    Status: Monitoring The suspected cause for the underlying issue is an outage with an upstream dependent system. A sharp decline in error rates and increasing login successes, indicating recovery is underway. Operational status has been confirmed with manual checks and successful logs, users are now able to log in again on the affected tenants. We are continuing to monitor this issue. Affected components Web Application (EMEA AWS) (Operational)

  3. resolved Apr 22, 2026, 08:53 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Affected components Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor April 21, 2026

[EMEA AWS] deps failures due to private packages in dbt Platform

Detected by Pingoru
Apr 21, 2026, 12:52 AM UTC
Resolved
Apr 21, 2026, 12:52 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Apr 20, 2026, 10:24 PM UTC

    Status: Investigating We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 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 Scheduled Jobs (EMEA AWS) (Partial outage) IDE (EMEA AWS) (Partial outage)

  2. identified Apr 20, 2026, 10:37 PM UTC

    Status: Identified We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA AWS) (Partial outage) IDE (EMEA AWS) (Partial outage)

  3. identified Apr 20, 2026, 11:52 PM UTC

    Status: Identified We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available. Affected components IDE (EMEA AWS) (Partial outage) Scheduled Jobs (EMEA AWS) (Partial outage)

  4. monitoring Apr 21, 2026, 12:23 AM UTC

    Status: Monitoring We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor. Affected components IDE (EMEA AWS) (Partial outage) Scheduled Jobs (EMEA AWS) (Partial outage)

  5. resolved Apr 21, 2026, 12:52 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational)

Read the full incident report →

Minor April 21, 2026

[EU4 Cell 1 GCP] deps failures due to private packages in dbt Platform

Detected by Pingoru
Apr 21, 2026, 12:52 AM UTC
Resolved
Apr 21, 2026, 12:52 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Apr 20, 2026, 10:24 PM UTC

    Status: Investigating We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 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) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  2. identified Apr 20, 2026, 10:37 PM UTC

    Status: Identified We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  3. identified Apr 20, 2026, 11:52 PM UTC

    Status: Identified We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available. Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  4. monitoring Apr 21, 2026, 12:23 AM UTC

    Status: Monitoring We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor. Affected components IDE (EU4 Cell 1 GCP) (Partial outage) Scheduled Jobs (EU4 Cell 1 GCP) (Partial outage)

  5. resolved Apr 21, 2026, 12:52 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (EU4 Cell 1 GCP) (Operational) Scheduled Jobs (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 21, 2026

[US AWS] deps failures due to private packages in dbt Platform

Detected by Pingoru
Apr 21, 2026, 12:52 AM UTC
Resolved
Apr 21, 2026, 12:52 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Apr 20, 2026, 10:24 PM UTC

    Status: Investigating We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 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) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  2. identified Apr 20, 2026, 10:37 PM UTC

    Status: Identified We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US AWS) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  3. identified Apr 20, 2026, 11:52 PM UTC

    Status: Identified We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available. Affected components IDE (US AWS) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  4. monitoring Apr 21, 2026, 12:23 AM UTC

    Status: Monitoring We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor. Affected components IDE (US AWS) (Partial outage) Scheduled Jobs (US AWS) (Partial outage)

  5. resolved Apr 21, 2026, 12:52 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor April 21, 2026

[US Cell 1 AZURE] deps failures due to private packages in dbt Platform

Detected by Pingoru
Apr 21, 2026, 12:52 AM UTC
Resolved
Apr 21, 2026, 12:52 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Apr 20, 2026, 10:24 PM UTC

    Status: Investigating We're investigating an issue with scheduled jobs and the studio IDE that is causing deps failures for some customers using private packages. This is impacting job runs and studio IDE sessions anytime after 3:20 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) (Partial outage) Scheduled Jobs (US Cell 1 AZURE) (Partial outage)

  2. identified Apr 20, 2026, 10:37 PM UTC

    Status: Identified We have identified an issue with private packages that resulted in deps failures in scheduled jobs and the studio ide for some customers. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AZURE) (Partial outage) Scheduled Jobs (US Cell 1 AZURE) (Partial outage)

  3. identified Apr 20, 2026, 11:52 PM UTC

    Status: Identified We have identified an issue impacting a subset of customers using private packages with Azure DevOps, resulting in deps failures in scheduled jobs and the Studio IDE. We are continuing to deploy a fix and will provide further updates as they become available. Affected components Scheduled Jobs (US Cell 1 AZURE) (Partial outage) IDE (US Cell 1 AZURE) (Partial outage)

  4. monitoring Apr 21, 2026, 12:23 AM UTC

    Status: Monitoring We have deployed a fix for the private packages dependency resolution in dbt Cloud that was causing deps failures in scheduled jobs and the Studio IDE for a subset of customers using Azure DevOps. The affected systems have returned to their normal state and we are continuing to monitor. Affected components IDE (US Cell 1 AZURE) (Partial outage) Scheduled Jobs (US Cell 1 AZURE) (Partial outage)

  5. resolved Apr 21, 2026, 12:52 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. An issue with private package dependency resolution in dbt Cloud resulted in dbt deps failures in scheduled jobs and the Studio IDE for customers using Azure DevOps. We have put measures in place to prevent a recurrence and the affected systems have returned to normal. Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components IDE (US Cell 1 AZURE) (Operational) Scheduled Jobs (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor April 18, 2026

[APAC 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 (APAC 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 (APAC 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 (APAC 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 (APAC AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[EMEA 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 (EMEA 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 (EMEA 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 (EMEA 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 (EMEA AWS) (Operational)

Read the full incident report →

Minor April 18, 2026

[EMEA 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 (EMEA 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 (EMEA 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 (EMEA 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 (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor April 18, 2026

[EU 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 (EU 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 (EU 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 (EU 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 (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor April 18, 2026

[EU4 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 (EU4 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 (EU4 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 (EU4 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 (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

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 →

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