Git errors for projects connected to GitHub over SSH
Git operations failed for dbt Cloud projects that use a dbt-managed repository or connect to GitHub with a deploy key. The errors were "Permission denied (publickey)" in job runs and dbt Studio git actions. dbt Cloud reports that this incident is resolved. It lasted 1 minute and 43 seconds.
State
Resolved
Started
Lasted
2 min
Worst impact
Partial outage
Timeline
2 updatesMonitoring
2 min 100%
Updates
Times in UTCAs posted by dbt Cloud
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.
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.
dbt Cloud in the last 90 days
Full historyIncidents in 90 days
25
Days with an incident
26
Median duration
2 h 17 min
This incident
99% shorter than the median
Other dbt Cloud incidents
All incidentsdbt Cloud·dbt Studio error loop with restarting dbt Studio
dbt Cloud reported an error loop in dbt Studio that asked users to restart dbt Studio. The issue affected dbt Project Environments on versions 1.6 and 1.7. dbt Cloud resolved the issue after 86 minutes.
dbt Cloud·Expired GitLab project access tokens not refreshing causing failures in posting commit statuses
dbt Cloud did not post GitLab CI job commit statuses for existing projects with expired GitLab project access tokens. This affected a small number of customers in the EU2 (Azure) region. dbt Cloud reports that the issue is resolved and that it lasted about 111 minutes.
dbt Cloud·dbt Wizard SQL execution failing
The issue has been resolved, and all affected systems are now functioning normally as of 5:50pm UTC. Please contact Support via email [support@getdbt.com](http://support@getdbt.com) if you continue to experience delays and are unsure of the root cause.
dbt Cloud·Degraded performance across dbt platform
The issue has been resolved, and all affected systems are now functioning normally as of 19:35 UTC. Between 19:18- 19:35 UTC on 28 October, an issue with the dbt platform services resulted in errors for customers loading dbt Studio, running jobs, or using the API. We have put measures in place to prevent a recurrence and the platform has returned to normal. Please contact Support via email at [support@getdbt.com](mailto:support@getdbt.com) if you continue to experience delays and are unsure of the root cause
dbt Cloud·dbt deps failures in dbt job runs and Studio
The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence. Please contact Support via email [support@getdbt.com](http://support@getdbt.com "support@getdbt.com") if you continue to experience delays and are unsure of the root cause.
Follow dbt Cloud
Your coding agent knows when dbt Cloud is down, and tells you when a failure is theirs, not yours. You can also get dbt Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dbt" and tell me if dbt Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=dbt/feed subscribe https://outages.live/feed.xml?providers=dbtFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane