# Git errors for projects connected to GitHub over SSH

- Provider: [dbt Cloud](https://down.guide/dbt-cloud)
- Level: confirmed
- Impact: Partial outage
- lasted 0m
- started 2026-11-04 12:50 UTC
- id: DWN-3a19837255
- Official page: https://status.getdbt.com/incidents/01M6K9RC8K3RCZZ9FBVSZCNYC4

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

[Postmortem](https://status.getdbt.com/incidents/01M6K9RC8K3RCZZ9FBVSZCNYC4)

## Updates from dbt Cloud
### 2026-11-04 09:37 UTC: investigating
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.

### 2026-11-04 10:07 UTC: identified
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.

### 2026-11-04 11:30 UTC: monitoring
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.

### 2026-11-04 11:50 UTC: resolved
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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).