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.

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

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.

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.