Job runs failing at the git clone step

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.

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.

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.