Changes / dbt Labs / Job runs failing at the git clone step
dbt Labs: Critical incident: Job runs failing at the git clone step
Summary
dbt Labs reported a critical outage from 2026-07-21 07:45 UTC to 2026-07-21 12:52 UTC (5 h 7 min). Scheduled, CI, and API-triggered GitHub job runs failed at “Clone git repository” across all regions (multi-tenant and single-tenant) because of upstream GitHub SSH deploy key authentication failures. GitHub resolved the issue; failed runs can be retried.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Job runs failing at the git clone step
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-21 07:45 UTC
Before: not present
After: 2026-07-21 12:52 UTC
Before: not present
After: We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 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: We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error.
Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected.
This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4
We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.
Before: not present
After: GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again.
Any runs that failed during the incident can now be retried.
We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.
Before: not present
After: This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication.
GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried.
We apologize for the disruption and thank you for your patience.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Job runs failing at the git clone step (this change) dbt Labs reported a critical outage from 2026-07-21 07:45 UTC to 2026-07-21 12:52 UTC (5 h 7 min). Scheduled, CI, and API-triggered GitHub job runs failed at “Clone git repository” across all regions (multi-tenant and single-tenant) because of upstream GitHub SSH deploy key authentication failures. GitHub resolved the issue; failed runs can be retried. | Major incident |