dbt Cloud incident

[EMEA AWS] Intermittent BigQuery job failures using Workload Identity Federation in EMEA

Minor Resolved View vendor source →

dbt Cloud experienced a minor incident on September 25, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Sep 25, 2026, 01:50 AM UTC
Resolved
Sep 25, 2026, 01:50 AM UTC
Duration
—
Detected by Pingoru
Sep 25, 2026, 01:50 AM UTC

Update timeline

  1. investigating Sep 24, 2026, 01:27 PM UTC

    Status: Investigating We're investigating an issue with BigQuery authentication that is causing some job runs to fail intermittently. This is impacting jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) while authenticating with Google Cloud, before any queries run. 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. In the meantime, rerunning a failed job or using Rerun from failure will usually succeed. Jobs using other BigQuery authentication methods, jobs on other data platforms, and dbt Studio are not impacted and should be running as expected. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  2. investigating Sep 24, 2026, 03:19 PM UTC

    Status: Investigating We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. Affected runs fail with "The service is currently unavailable" (HTTP 503) during the token exchange with Google Cloud. We haven't found any changes on our side, and the error appears to originate on Google Cloud's side. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  3. investigating Sep 24, 2026, 05:32 PM UTC

    Status: Investigating We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  4. investigating Sep 24, 2026, 06:41 PM UTC

    Status: Investigating We're continuing to investigate intermittent failures for jobs in the EMEA multi-tenant region (AWS) that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  5. monitoring Sep 24, 2026, 08:21 PM UTC

    Status: Monitoring We have not observed any further occurrences and are monitoring to confirm the issue has fully cleared. dbt job runs have returned to their normal state and we are continuing to monitor. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  6. identified Sep 24, 2026, 08:59 PM UTC

    Status: Identified We have identified an issue with intermittent failures for jobs that connect to BigQuery using Workload Identity Federation. If you're affected, please open a case with Google Cloud support about the 503 errors from the Workload Identity Federation token exchange. Once you receive more information from Google, you can share it with us by opening a dbt Support ticket so we can investigate further. We will provide further updates as soon as new information becomes available. Affected components Scheduled Jobs (EMEA AWS) (Degraded performance)

  7. monitoring Sep 25, 2026, 12:43 AM UTC

    Status: Monitoring The impacted component appears to be recovering, we will continue to monitor the performance. Please contact us at [email protected] with any questions or concerns. Affected components Scheduled Jobs (EMEA AWS) (Operational)

  8. resolved Sep 25, 2026, 01:50 AM 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)