Changes / dbt Labs / Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts
dbt Labs: Major incident: Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts
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 from the diff below (Sol; type: incident outage). Check the diff before relying on it.
Major incidentLabel: outage (model (Jev), 87%)Changed Detected Source: status.getdbt.com (opens in new tab)
What changed
Before: not present
After: Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-07-19 07:33 UTC
Before: not present
After: 2026-07-19 13:55 UTC
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts (this change) 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. | Major incident |