dbt Cloud incident
[US Cell 3 AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error
dbt Cloud experienced a major incident on July 24, 2026, lasting 54m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jul 24, 2026, 07:58 AM UTC
Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.
- investigating Jul 24, 2026, 08:01 AM UTC
Status: Investigating We're investigating an issue with [X component/system] that is causing [the issue’s impact]. This is impacting [X component/system] in [Y region & tenant ] anytime after [H:MM time Eastern]. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. [X component/system] is not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)
- investigating Jul 24, 2026, 08:20 AM UTC
Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)