Major incident

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

Nov 4, 2026, 12:50 UTC

started

11:50 UTC

resolved

—

duration

Current status of dbt Cloud: Operational — live dbt Cloud status

Timeline

Nov 4, 2026, 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.
Nov 4, 2026, 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.
Nov 4, 2026, 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.
Nov 4, 2026, 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.

Updates as published by dbt Cloud.

Other services with incidents at the same time

This was part of a wider event: 15 services reported incidents within the hour.

Bling 13:39 UTC · 999 - Rejeicao: Erro nao catalogado no envio das NFCe a Sefaz do RS
Cloudflare 13:39 UTC · Network latency issues in NRT
SofaScore 13:39 UTC · Production errors
RIPE NCC 13:36 UTC · RPKI Publication as a Service rejecting publications
Blip 13:32 UTC · Issue affecting the user experience on the Portal and the Desk
Mercado Pago 13:13 UTC · QR MLC - QRC Aprobaciones
MRI Software 13:09 UTC · London DC (Maidenhead) - Reported Incident - Monitoring
Autotrader 13:01 UTC · AT Connect - Advertiser APIs
Flexera System Status Dashboard 12:59 UTC · Flexera One - SaaS Management - All regions - data aggregation failures
Moonshot AI 12:41 UTC · kimi fs服务异常
Scaleway 12:37 UTC · Cockpit (pl-waw) Traces ingestion is degraded
Kaseya 12:26 UTC · BMS - US - Multiple Customers Experiencing Resource Unavailable / Record Not Found Errors Across Modules
Axiom 12:14 UTC · Login issues
Dartmouth College 12:13 UTC · IRA Advancement data stale
Elastic Cloud (Public) 12:08 UTC · mOLTP PrivateLink connectivity issue

More dbt Cloud incidents

November 4, 2026 Jobs list and Environment pages failing to load
November 3, 2026 dbt Studio error loop with restarting dbt Studio
November 3, 2026 Expired GitLab project access tokens not refreshing causing failures in posting commit statuses
October 29, 2026 dbt Wizard SQL execution failing
October 28, 2026 Degraded performance across dbt platform
October 22, 2026 dbt deps failures in dbt job runs and Studio