# dbt Cloud: Git errors for projects connected to GitHub over SSH

> dbt Cloud Git operations failed for projects that use a dbt-managed repository or connect to GitHub with a deploy key. Job runs and dbt Studio git actions failed intermittently with "Permission denied (publickey)". The incident is resolved and lasted 1 hour and 46 minutes. Failed job runs can be re-run.

- Provider: [dbt Cloud](https://outages.cc/dbt.md)
- Type: Incident
- State: Resolved
- Worst impact: Partial outage
- Started: 2026-11-04 12:50 UTC
- Resolved: 2026-11-04 12:51 UTC (lasted 2 min)
- Official update: https://status.getdbt.com

## Updates from dbt Cloud

### resolved, 2026-11-04 12:51 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.

### identified, 2026-11-04 12:51 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.