# dbt Labs: Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-07-19 07:33 UTC · Resolved: 2026-07-19 13:55 UTC · Duration: 6.4 h
- Updates: 5 · Affected components: 01JBCD2ZXG0Y9ZGBC077TXQKN1, 01JBCQVPBNMJ60EVAVX611QWT2
- [Vendor status page: https://status.getdbt.com/incidents/01KXWMNWR3ARKEXDT5D4MG7KGG](https://status.getdbt.com/incidents/01KXWMNWR3ARKEXDT5D4MG7KGG)
- [Company: dbt Labs](https://rewindex.com/company/dbt-labs.md)

## Summary

Major Git clone failures (403 errors) affected EMEA scheduled and triggered jobs using the GitHub App integration; IDE and CLI were unaffected. Failures began 2026-07-18 23:00 UTC; the incident was tracked from 2026-07-19 07:33 UTC until resolution at 2026-07-19 13:55 UTC (6 h 22 min). Errors normalized without a deployed fix; no definitive root cause was identified. _(machine-written, sol)_
## Timeline of updates

- **investigating** 2026-07-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.
- **investigating** 2026-07-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.
- **monitoring** 2026-07-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.
- **monitoring** 2026-07-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
- **resolved** 2026-07-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.

## Rewindex changes for this incident

- 2026-07-19 07:33 UTC: [Major incident: Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts](https://rewindex.com/change/i1ce0fbf2100333.md)


---
Canonical: https://rewindex.com/company/dbt-labs/incidents/01KXWMNWR3ARKEXDT5D4MG7KGG · Markdown: https://rewindex.com/company/dbt-labs/incidents/01KXWMNWR3ARKEXDT5D4MG7KGG.md · JSON: https://rewindex.com/api/v1/companies/dbt-labs/incidents/01KXWMNWR3ARKEXDT5D4MG7KGG · Generated 2026-10-18T09:54:02.695Z