Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts
Jul 19, 07:33 UTCJul 19, 13:55 UTC
Duration
6h 22m
Impact
Major
Root cause
Deployment
dbt Labs, 90 days
33 incidents
Affected
Not listed by the vendor.
Final update
**Update , 13:52 UTC** Git clone errors on prod-emea have not recurred and success rates have remained normal. We have not identified a definitive root cause on our side and are continuing to investigate internally. We are resolving this incident, but will follow up if new information becomes available.
Timeline
- Resolved · Jul 19, 13:55 UTC
**Update , 13:52 UTC** Git clone errors on prod-emea have not recurred and success rates have remained normal. We have not identified a definitive root cause on our side and are continuing to investigate internally. We are resolving this incident, but will follow up if new information becomes available.
- Monitoring · Jul 19, 10:29 UTC
**Update , 10:29 UTC** Git clone errors have remained at normal levels since our last update, with no recurrence. No fix was deployed on our side, and a specific root cause has not yet been confirmed. We are continuing to monitor
- Monitoring · Jul 19, 09:54 UTC
Update , 09:50 UTC Git clone error rates for scheduled and triggered job runs in the EMEA region via our GitHub App integration are starting to return to normal. The issue appears to be resolving on its own; no fix has been deployed on our side. We have not yet confirmed a specific root cause , investigation is ongoing, with focus on the GitHub App's authentication path. We are closely monitoring to confirm this recovery holds.
- Investigating · Jul 19, 08:09 UTC
Update , 08:04 UTC We've confirmed this issue is isolated to scheduled and triggered job runs in the EMEA region that use our GitHub App integration to clone repositories. The dbt platform IDE and CLI are not affected , we've verified successful Git activity through those paths throughout the incident window. Our team has traced the failures to the GitHub App's authentication path and is now working on validating the installation configuration for this region. We will continue to provide updates at approximately 30-minute intervals or as soon as new information becomes available. Next update by 08:34 UTC.
- Investigating · Jul 19, 07:33 UTC
We're investigating an issue with Git clone operations via our GitHub App integration that is causing scheduled jobs to fail when cloning repositories. Starting from 2026-07-18 23:00 UTC. 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.
More from dbt Labs
Full historyJobs list and Environment pages failing to loadlasted 4h 19mGit errors for projects connected to GitHub over SSHlasted 2h 13mdbt Studio error loop with restarting dbt Studiolasted 1h 26mExpired GitLab project access tokens not refreshing causing failures in posting commit statuseslasted 1h 51mdbt Wizard SQL execution failinglasted 2h 6mDegraded performance across dbt platformlasted 4h 36m