Git errors for projects connected to GitHub over SSH

What to do

• Check whether your product depends on dbt Cloud. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-11-04 12:50 UTC and 2026-11-04 11:50 UTC may need a replay.

• Subscribe to dbt Cloud's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=dbt-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We've identified the cause as an incident at GitHub affecting Git operations ( ).

Updates from dbt Cloud 4

1. investigatingNov 4, 2026, 9:37 AM UTC

   We're investigating an issue with git operations that is causing job runs to fail at the "Clone git repository" step and dbt Studio git actions to fail with "Permission denied (publickey)". This is impacting Scheduled Jobs and the IDE for projects that use a dbt-managed repository or connect to GitHub with a deploy key, across multi-tenant regions on AWS, Azure and GCP, anytime after 09:37 UTC. The team is working on a resolution and we will provide updates as soon as new information becomes available. Projects that connect through the native GitHub integration or use other git providers are not impacted and should be running as expected.

   provider

2. identifiedNov 4, 2026, 10:07 AM UTC

   We've identified the cause as an incident at GitHub affecting Git operations ( ). Until GitHub resolves it, job runs and dbt Studio git actions may fail intermittently with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Accounts with repository caching enabled may see affected runs continue from the cached copy of the repository. We'll provide another update as GitHub makes progress.

   provider

3. monitoringNov 4, 2026, 11:30 AM UTC

   GitHub has mitigated the issue, and we're no longer seeing these errors in job runs or dbt Studio. We're monitoring to confirm things stay stable. Job runs that failed with this error can be re-run.

   provider

4. resolvedNov 4, 2026, 11:50 AM UTC

   This incident has been resolved. Between 09:37 and 11:23 UTC, an incident at GitHub caused some job runs and dbt Studio git actions to fail with "Permission denied (publickey)" for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Git operations have been stable since GitHub's fix. Any job run that failed with this error during that window can be re-run.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.