rewindex

Companiesdbt LabsIncidents

dbt Labs: Git errors for projects connected to GitHub over SSH

MajorStatus: resolvededitedStarted Resolved (2.2 h)4 updatesstatus.getdbt.com (opens in new tab)

Affected components: 01JBCBN080JGEJ8B0AWCAJK9RN01JBCBN0CAA2QVD10W6BKMPDRF01JBCBN1FAA7M1PF1A390EAREG01JBCBN1KQCDFX2SZ1WHPRVPYE01JBCBN2QJGPW8YNXDQY26T41V01JBCBN2VYP78DYVVARQJK3MJJ01JBCBN580QQW3WAG5DQTB2V3G01JBCBN5C72ZRZYFXJYB936JEA01JBCBN6G24WEX8Y2DDGMQ2V7501JBCD2ZXG0Y9ZGBC077TXQKN101JBCQQF8K02PQMM5WPGGVA2TC01JBCQQZ41M6BZCP649F5FFZYS01JBCQV9S7HYCF0Q81H55VWBGA01JBCQVPBNMJ60EVAVX611QWT201JBCR08X8CFND61GD5DW19N7801JBCR0NDT2ENWZZ6RZEF825KQ01JH8R89TPYCY0Z9X6W4DDPH2G01JH8R89TW25GVBJRS0C69K5H901JRKCJTBSJDQA2SECTV7GE3BT01JRKCJTC2FSGQQZQBZHCSX8BB01K1EH8NN4BA0WB81Z7PKWHZGY01K1EH8NN6PK7YBC7EV6QHG2WZ01K4T29F336RNJ2A0NFNNNAM7X01K4T29F35RK5FECSXM2SW4XE801KF46A8M6SCNZD8WWFNPB1QJA01KF46A8M70AMCM21TWN89Z56W01KSMXDZMBBVGS7F0J1867BF8401KSMXDZMNB8ZAGBC1K7WZENT601KX12QA4CYG2K1N0XW50BRB3X01KX12QA4EC01M2PN22RAW56SX

Timeline of updates

  1. 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.

  2. identified

    We've identified the cause as an incident at GitHub affecting Git operations (https://www.githubstatus.com/incidents/smtdswd1h2w4 (opens in new tab)). 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.

  3. 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.

  4. 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.

Changes Rewindex caught on this incident

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.

Impact, status and times are the vendor’s own, as last archived. View on status.getdbt.com (opens in new tab).

Cite this

Status incident (vendor impact label: major) posted by dbt Labs, started 2026-11-04 09:37 UTC, resolved after 2.2 h, 4 update(s); edited after publishing.

Title
Git errors for projects connected to GitHub over SSH
Vendor
dbt Labs
Date
URL
https://rewindex.com/company/dbt-labs/incidents/01M6K9RC8K3RCZZ9FBVSZCNYC4

dbt Labs profileRecent dbt Labs incidentsAll outages on November 4, 2026dbt Labs in November 2026MarkdownJSON