Minor impactResolvedDatabases

dbt Cloud incident: Scheduled jobs are intermittently affected by job failures caused by 403 error

dbt Cloud reported this minor-impact incident on its official status page on Jul 24, 2026, 07:58 UTC. It was resolved after 7h.

Right now dbt Cloud is operational. Live dbt Cloud status →

🔔 Get alerted when dbt Cloud has issuesFree · email alerts · no credit card
Jul 24, 2026, 07:58 UTC
started
Jul 24, 2026, 14:58 UTC
resolved
7h
duration
Minor
impact
  1. resolvedJul 24, 2026, 14:58 UTC

    Intermittent job run failures during the git repository clone step affected our EMEA infrastructure. This impacted job runs between 2026-07-24 00:00 UTC and 2026-07-24 11:08 UTC. The issue has not recurred for over 3.5 hours and all affected systems are functioning normally. Please contact Support at [[email protected]](mailto:[email protected]) if you continue to experience issues or have any follow-up questions.

  2. monitoringJul 24, 2026, 12:31 UTC

    Failure rates for job runs during the git repository clone step in our EMEA infrastructure remain at normal levels, with no further occurrences in the last 60 minutes. We have not identified or deployed a specific fix, and we are continuing to closely monitor. We will provide a further update once we can confirm full resolution, or sooner if the issue recurs.

  3. investigatingJul 24, 2026, 12:25 UTC

    > We're continuing to closely monitor an issue causing intermittent job failures during the git repository clone step within our EMEA infrastructure. We have seen no further occurrences in the last 45 minutes, though a root cause has not yet been confirmed. We will provide a further update within the hour, or sooner if there is a material change.

  4. investigatingJul 24, 2026, 11:46 UTC

    We're continuing to investigate intermittent job failures during the git repository clone step, affecting our EMEA infrastructure. Failure rates have dropped significantly since earlier today, and we've seen no further occurrences in the last 30 minutes. A root cause has not yet been confirmed. We're continuing to closely monitor and will provide a further update within the hour, or sooner if there is a material change.

  5. investigatingJul 24, 2026, 11:26 UTC

    We saw a further burst of job failures during the git repository clone step earlier, consistent with the intermittent pattern we've seen throughout this incident. A root cause has not yet been confirmed. We're continuing to closely monitor and investigate, and will provide a further update within the hour, or sooner if there is a material change.

  6. investigatingJul 24, 2026, 10:43 UTC

    The rate of job failures during the git repository clone step remains much lower than earlier today, though we're continuing to see occasional, isolated failures. A root cause has not yet been confirmed. We're continuing to closely monitor and will provide a further update within the hour, or sooner if there is a material change.

  7. investigatingJul 24, 2026, 10:14 UTC

    The rate of job failures during the git repository clone step has dropped significantly. We have not identified or deployed a specific fix, and we're continuing to closely monitor to confirm this improvement holds. We'll provide a further update once we can confirm full recovery, or sooner if the issue resumes.

  8. investigatingJul 24, 2026, 09:30 UTC

    We're continuing to investigate an issue causing intermittent job run failures during the git repository clone step, with an error referencing an HTTP 403 response, affecting our EMEA infrastructure only. Based on further investigation, we do not believe the dbt Studio IDE has been affected by this issue. Our engineering team continues to investigate and we will provide a further update within the hour.

  9. investigatingJul 24, 2026, 09:05 UTC

    We're continuing to investigate an issue causing intermittent job run failures during the git repository clone step, with an error referencing an HTTP 403 response. We've reduced the scope of this issue, it is affecting our EMEA infrastructure only. We're still confirming whether the dbt Studio IDE is affected for any users. Our engineering team continues to investigate and we will provide a further update within the hour.

  10. investigatingJul 24, 2026, 08:20 UTC

    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.

  11. investigatingJul 24, 2026, 07:58 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in dbt Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does dbt Cloud have incidents?

dbt Cloud reported 24 incidents in the last 90 days, 6 of them major or critical. A typical incident lasted 2h 4m. See dbt Cloud's uptime and incident history

dbt Cloud incident on Jul 24, 2026: Scheduled jobs are intermittently affected by job failures caused by 403 error · APIStatus.watch