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

1. resolvedNov 4, 2026, 11:50 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.

2. monitoringNov 4, 2026, 11:30 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.

3. identifiedNov 4, 2026, 10:07 UTC

   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.

4. investigatingNov 4, 2026, 09:37 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in dbt Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [DE1][Network] - Load Balancer incident notificationMajor · Nov 4, 2026, 10:16 UTC
• Akamai: Edge Delivery issues between Indonesia and SingaporeMinor · Oct 25, 2026, 13:44 UTC
• Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)Minor · Oct 25, 2026, 13:54 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to Digi Mobil RomaniaMinor · Oct 26, 2026, 13:09 UTC
• Twilio: Voice Call Failures From Twilio Phone Numbers to GermanyMinor · Oct 27, 2026, 09:00 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to C-Spire United StatesMinor · Oct 27, 2026, 21:31 UTC
• Twilio: Silent Network Authentication (SNA) Failure Increase on Indosat in IndonesiaMinor · Oct 28, 2026, 12:14 UTC
• Linode: Service Issue - US-Southeast (Atlanta)Minor · Oct 31, 2026, 17:49 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Philippines Phone Numbers to Multiple Networks in PhilippinesMinor · Nov 2, 2026, 05:41 UTC
• Twilio: Media Streams Audio DelaysMinor · Nov 3, 2026, 01:29 UTC

How often does dbt Cloud have incidents?

dbt Cloud reported 34 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 2h 57m. See dbt Cloud's uptime and incident history