Changesdbt LabsGit errors for projects connected to GitHub over SSH
dbt Labs: Incident silently edited: Git errors for projects connected to GitHub over SSH
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what dbt Labs removed; blue is what they added. Muted text is unchanged context.
Before: 2026-11-04 12:50 UTC
After: 2026-11-04 09:37 UTC
Before: 2026-11-04 12:51 UTC
After: 2026-11-04 11:50 UTC
Before: 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.
After: 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.
Before: We've identified the cause as an incident at GitHub affecting Git operations (https://www.githubstatus.com/incidents/smtdswd1h2w4). 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.
After: We've identified the cause as an incident at GitHub affecting Git operations (https://www.githubstatus.com/incidents/smtdswd1h2w4). 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.
Before: 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.
After: 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.
Before: 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.
After: 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.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
History of this incident
TodayWednesday, November 4Wed, Nov 4
1 rewrite, 1 incident change
- EditedEdited by the vendor
Git errors for projects connected to GitHub over SSHthis change
- MajorMajor incident
Cite this
Incident silently edited: Git errors for projects connected to GitHub over SSH on dbt Labs’s status page, changed 2026-11-04 13:43 UTC (change 2 of 2).
- Title
- Incident silently edited: Git errors for projects connected to GitHub over SSH
- Vendor
- dbt Labs
- Date
- URL
- https://rewindex.com/change/rc9f4cd272761ba