Skip to content
dbt Labs · Data and observabilityJul 19, 2026, 07:33 UTC

Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts

MajorDeploymentUpdated 16h ago
Jul 19, 07:33 UTCJul 19, 13:55 UTC
Duration
6h 22m
Impact
Major
Root cause
Deployment
dbt Labs, 90 days
26 incidents
Affected
Not listed by the vendor.
Status page

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

  1. 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.
  2. 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
  3. 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.
  4. 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.
  5. 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 history
StartedIncidentDuration
Sep 2322:59 UTCIntermittent dbt deps failures4m
Sep 1823:31 UTCSchema Hydration Panic14h 58m
Sep 1014:28 UTCIntermittent errors on the Discovery API2h 17m
Sep 1013:46 UTCIncreased error rates associated with dbt MCP and dbt Wizard41m
Sep 1008:02 UTCState usage metrics not being ingested1h 13m
Sep 818:44 UTCUser Login Sessions Terminated4h 32m

Also caused by deployment or rollout

All
StartedIncidentDuration
Sep 1106:22 UTCIssues with Workers VPC hostname route resolution on 2026-09-11Cloudflare0m
Aug 2014:43 UTCIntermittent failures creating agent tasksGitHub9h 54m
Aug 2000:31 UTC[Medium] Issue with Microsoft Office Integration and Box EditBox1h 13m
Aug 622:22 UTCTrouble Using Search Bar For Some AdminsSlack2h 44m
Jul 200:17 UTCTraces, spans, logs inaccesible for query or ingestion in de and usSentry3h 39m
Jun 2915:28 UTCElevated error rates and latency for EAS Build, Workflows, and SubmitExpo14m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.