dbt Cloud Outage History

dbt Cloud is up right now

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

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

Source: https://status.getdbt.com

Minor May 15, 2026

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

Detected by Pingoru
May 15, 2026, 09:09 PM UTC
Resolved
May 15, 2026, 09:09 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 15, 2026, 06:23 PM UTC

    Status: Investigating We're investigating an issue with CI in the dbt Platform UI for ADO integrations that is causing missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. This is impacting CI jobs anytime after May 14th around approximately 3 PM Eastern. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Cron-scheduled jobs are not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 4 AWS) (Partial outage)

  2. identified May 15, 2026, 06:38 PM UTC

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

  3. monitoring May 15, 2026, 07:34 PM UTC

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

  4. resolved May 15, 2026, 09:09 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between May 14th at approximately 3 PM Eastern and 5 PM Eastern on May 15th, an issue with CI in the dbt Platform UI for ADO integrations caused missing Pull Requests tab in CI jobs in addition to error "This feature is only available for dbt repositories connected through dbt's native integration with GitHub, Gitlab, or Azure DevOps" under trigger on pull request setting in CI jobs. We have put measures in place to prevent a recurrence and CI jobs has returned to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor May 15, 2026

[APAC AWS] dbt Platform CLI State Selector Failing

Detected by Pingoru
May 15, 2026, 04:20 PM UTC
Resolved
May 15, 2026, 04:20 PM UTC
Duration
—
Timeline · 4 updates
  1. monitoring May 15, 2026, 04:17 PM UTC

    Status: Monitoring We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational)

  2. resolved May 15, 2026, 04:20 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. 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) dbt platform CLI (APAC AWS) (Operational)

  3. investigating May 15, 2026, 04:24 PM UTC

    Status: Investigating We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components dbt platform CLI (APAC AWS) (Degraded performance) Scheduled Jobs (APAC AWS) (Degraded performance)

  4. identified May 15, 2026, 04:37 PM UTC

    Status: Identified We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (APAC AWS) (Degraded performance) dbt platform CLI (APAC AWS) (Degraded performance)

Read the full incident report →

Minor May 15, 2026

[EMEA AWS] dbt Platform CLI State Selector Failing

Detected by Pingoru
May 15, 2026, 04:20 PM UTC
Resolved
May 15, 2026, 04:20 PM UTC
Duration
—
Timeline · 4 updates
  1. monitoring May 15, 2026, 04:17 PM UTC

    Status: Monitoring We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)

  2. resolved May 15, 2026, 04:20 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. 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) dbt platform CLI (EMEA AWS) (Operational)

  3. investigating May 15, 2026, 04:24 PM UTC

    Status: Investigating We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). 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) dbt platform CLI (EMEA AWS) (Degraded performance)

  4. identified May 15, 2026, 04:37 PM UTC

    Status: Identified We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance) dbt platform CLI (EMEA AWS) (Degraded performance)

Read the full incident report →

Minor May 15, 2026

[US Cell 2 AWS] dbt Platform CLI State Selector Failing

Detected by Pingoru
May 15, 2026, 04:20 PM UTC
Resolved
May 15, 2026, 04:20 PM UTC
Duration
—
Timeline · 4 updates
  1. monitoring May 15, 2026, 04:17 PM UTC

    Status: Monitoring We have deployed a fix for State Selector that is causing runtime errors when using the latest dbt version. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational)

  2. resolved May 15, 2026, 04:20 PM UTC

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

  3. investigating May 15, 2026, 04:24 PM UTC

    Status: Investigating We're investigating an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). 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) dbt platform CLI (US Cell 2 AWS) (Degraded performance)

  4. identified May 15, 2026, 04:37 PM UTC

    Status: Identified We have identified an issue with State Selector that is causing runtime errors when using the latest version (dbt version: 2026.5.12+b52ab1d). A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance)

Read the full incident report →

Minor May 12, 2026

[APAC AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (APAC AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (APAC AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (APAC AWS) (Operational)

Read the full incident report →

Minor May 12, 2026

[EMEA AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (EMEA AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EMEA AWS) (Operational)

Read the full incident report →

Minor May 12, 2026

[EMEA Cell 1 AZURE] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 12, 2026

[EU Cell 1 GCP] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (EU Cell 1 GCP) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 12, 2026

[EU4 Cell 1 GCP] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 12, 2026

[JP Cell 1 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (JP Cell 1 AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 12, 2026

[US AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor May 12, 2026

[US Cell 1 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 1 AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 12, 2026

[US Cell 1 AZURE] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 1 AZURE) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 12, 2026

[US Cell 1 GCP] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 1 GCP) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 12, 2026

[US Cell 2 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 12, 2026

[US Cell 3 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 3 AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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 May 12, 2026

[US Cell 4 AWS] Bigquery connection jobs failing with error "Failed to generate profile due to incorrect credentials. Please double check credentials and try again."

Detected by Pingoru
May 12, 2026, 08:49 AM UTC
Resolved
May 12, 2026, 08:49 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 12, 2026, 07:30 AM UTC

    Status: Investigating We're actively investigating an issue with some deployment jobs using BigQuery connection failing to generate a profile and getting cancelled as a result. The symptoms would be cancelled job runs with statement "Failed to generate profile due to incorrect credentials. Please double check credentials and try again." Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

  2. monitoring May 12, 2026, 08:27 AM UTC

    Status: Monitoring We have identified the underlying issue and have implemented a fix. We're continuing to monitor. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (US Cell 4 AWS) (Operational)

  3. resolved May 12, 2026, 08:49 AM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. 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 May 11, 2026

[APAC AWS] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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 Admin API (APAC AWS) (Operational) dbt Copilot (APAC AWS) (Operational) Metadata Ingestion (APAC AWS) (Operational) IDE (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational) Semantic Layer (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational) Web Application (APAC AWS) (Operational)

Read the full incident report →

Minor May 11, 2026

[EMEA AWS] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Metadata Ingestion (EMEA AWS) (Operational) Admin API (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) Semantic Layer (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) IDE (EMEA AWS) (Operational) dbt Copilot (EMEA AWS) (Operational) Metadata API (EMEA AWS) (Operational)

Read the full incident report →

Minor May 11, 2026

[EMEA Cell 1 AZURE] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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) Admin API (EMEA Cell 1 AZURE) (Operational) dbt Copilot (EMEA Cell 1 AZURE) (Operational) Metadata Ingestion (EMEA Cell 1 AZURE) (Operational) IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational) Metadata API (EMEA Cell 1 AZURE) (Operational) Semantic Layer API (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 11, 2026

[EU Cell 1 GCP] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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 dbt platform CLI (EU Cell 1 GCP) (Operational) dbt Copilot (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational) Metadata Ingestion (EU Cell 1 GCP) (Operational) Admin API (EU Cell 1 GCP) (Operational) Metadata API (EU Cell 1 GCP) (Operational) Semantic Layer API (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 11, 2026

[EU4 Cell 1 GCP] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Metadata Ingestion (EU4 Cell 1 GCP) (Operational) Web Application (EU4 Cell 1 GCP) (Operational) dbt Copilot (EU4 Cell 1 GCP) (Operational) Metadata API (EU4 Cell 1 GCP) (Operational) Semantic Layer API (EU4 Cell 1 GCP) (Operational) dbt platform CLI (EU4 Cell 1 GCP) (Operational) Admin API (EU4 Cell 1 GCP) (Operational) Scheduled Jobs (EU4 Cell 1 GCP) (Operational) IDE (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 11, 2026

[US AWS] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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 (US AWS) (Operational) Metadata Ingestion (US AWS) (Operational) dbt Copilot (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Admin API (US AWS) (Operational) Metadata API (US AWS) (Operational) IDE (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) Semantic Layer API (US AWS) (Operational)

Read the full incident report →

Minor May 11, 2026

[US Cell 1 AWS] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Metadata Ingestion (US Cell 1 AWS) (Operational) Admin API (US Cell 1 AWS) (Operational) dbt Copilot (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational) Semantic Layer API (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) Metadata API (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 11, 2026

[US Cell 1 AZURE] dbt Studio issues with previewing and compiling code

Detected by Pingoru
May 11, 2026, 10:26 PM UTC
Resolved
May 11, 2026, 10:26 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 10:26 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-05-11 22:30 UTC. Between 2026-05-11 16:12 UTC and 2026-05-11 22:30 UTC an issue with a recent release resulted in the dbt Studio to not preview or compile code correctly. This has now been resolved. 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 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational) Metadata Ingestion (US Cell 1 AZURE) (Operational) Web Application (US Cell 1 AZURE) (Operational) dbt Copilot (US Cell 1 AZURE) (Operational) Scheduled Jobs (US Cell 1 AZURE) (Operational) Admin API (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational) Metadata API (US Cell 1 AZURE) (Operational)

Read the full incident report →