dbt Cloud Outage History

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 22, 2026, 01:52 AM UTC· resolved Jul 22, 2026, 07:29 AM UTC

1. investigating Jul 22, 2026, 01:52 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

2. investigating Jul 22, 2026, 02:03 AM UTC

   We're investigating an issue with environment variable creation and editing in the dbt platform UI that is causing users to be unable to create or edit environment variables under environment settings, job overrides, and user overrides. The team is working on this and we will provide updates at approximately 30 minute intervals or as soon as new information becomes available.

3. identified Jul 22, 2026, 02:48 AM UTC

   We have identified the cause for the issue impacting environment variable creation and editing. A fix is being implemented, and we will provide an update shortly.

4. monitoring Jul 22, 2026, 05:29 AM UTC

   We have deployed a fix for the issue impacting environment variable creation and editing. The service has returned to its normal state and we are continuing to monitor.

5. resolved Jul 22, 2026, 07:29 AM UTC

   The issue has been resolved and affected system is now functioning normally as of 5:25 AM UTC. Earlier, we had an issue that impacted editing and creating environment variables. We have put measures in place to prevent a recurrence and the user interface is now back to normal. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience issues and are unsure of the root cause.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 21, 2026, 07:45 AM UTC· resolved Jul 21, 2026, 12:52 PM UTC

1. investigating Jul 21, 2026, 10:23 AM UTC

   We're investigating an issue with repository cloning that is causing scheduled, CI, and API-triggered job runs to fail at the "Clone git repository" step. This is impacting job runs across all regions (multi-tenant and single-tenant) anytime after approximately 3:40 AM ET (07:40 UTC). The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. identified Jul 21, 2026, 11:14 AM UTC

   We have identified the cause as an upstream GitHub incident affecting SSH authentication for deploy keys. Because the dbt platform uses deploy keys to clone Git repositories, scheduled, CI, and API-triggered runs that clone from GitHub are failing at the "Clone git repository" step with a Permission denied (publickey) error. Runs that connect to other providers (for example GitLab or Azure DevOps) are not affected. This is being addressed on GitHub's side. You can follow their progress here: https://www.githubstatus.com/incidents/g40zcbvchny4 We are monitoring closely and will provide an update as soon as GitHub's mitigation takes effect or we have more information.

3. monitoring Jul 21, 2026, 12:16 PM UTC

   GitHub has resolved the upstream incident affecting SSH deploy key authentication. As of approximately 7:45 AM ET (11:45 UTC), git clone error rates have returned to pre-incident levels and job runs are completing normally again. Any runs that failed during the incident can now be retried. We are continuing to monitor to confirm full and sustained recovery before marking this incident resolved.

4. resolved Jul 21, 2026, 12:59 PM UTC

   This incident is resolved. Scheduled, CI, and API-triggered job runs that clone from GitHub were failing at the "Clone git repository" step due to an upstream GitHub incident affecting SSH deploy key authentication. GitHub has resolved the underlying issue. Git clone error rates on the dbt platform have returned to normal and remained stable. Job runs are operating as expected, and any runs that failed during the incident can be safely retried. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Jul 19, 2026, 07:33 AM UTC· resolved Jul 19, 2026, 01:55 PM UTC

1. investigating Jul 19, 2026, 07:33 AM UTC

   We're investigating an issue with Git clone operations via our GitHub App integration that is causing scheduled jobs to fail when cloning repositories. Starting from 2026-07-18 23:00 UTC. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. investigating Jul 19, 2026, 08:09 AM UTC

   Update — 08:04 UTC We've confirmed this issue is isolated to scheduled and triggered job runs in the EMEA region that use our GitHub App integration to clone repositories. The dbt platform IDE and CLI are not affected — we've verified successful Git activity through those paths throughout the incident window. Our team has traced the failures to the GitHub App's authentication path and is now working on validating the installation configuration for this region. We will continue to provide updates at approximately 30-minute intervals or as soon as new information becomes available. Next update by 08:34 UTC.

3. monitoring Jul 19, 2026, 09:54 AM UTC

   Update — 09:50 UTC Git clone error rates for scheduled and triggered job runs in the EMEA region via our GitHub App integration are starting to return to normal. The issue appears to be resolving on its own; no fix has been deployed on our side. We have not yet confirmed a specific root cause — investigation is ongoing, with focus on the GitHub App's authentication path. We are closely monitoring to confirm this recovery holds.

4. monitoring Jul 19, 2026, 10:29 AM UTC

   Update — 10:29 UTC Git clone errors have remained at normal levels since our last update, with no recurrence. No fix was deployed on our side, and a specific root cause has not yet been confirmed. We are continuing to monitor

5. resolved Jul 19, 2026, 01:55 PM UTC

   Update — 13:52 UTC Git clone errors on prod-emea have not recurred and success rates have remained normal. We have not identified a definitive root cause on our side and are continuing to investigate internally. We are resolving this incident, but will follow up if new information becomes available.

Read the full incident report →

Started Jul 19, 2026, 07:33 AM UTC· resolved Jul 19, 2026, 01:55 PM UTC

1. investigating Jul 19, 2026, 07:33 AM UTC

   We're investigating an issue with Git clone operations via our GitHub App integration that is causing scheduled jobs to fail when cloning repositories. Starting from 2026-07-18 23:00 UTC. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available.

2. investigating Jul 19, 2026, 08:09 AM UTC

   Update — 08:04 UTC We've confirmed this issue is isolated to scheduled and triggered job runs in the EMEA region that use our GitHub App integration to clone repositories. The dbt platform IDE and CLI are not affected — we've verified successful Git activity through those paths throughout the incident window. Our team has traced the failures to the GitHub App's authentication path and is now working on validating the installation configuration for this region. We will continue to provide updates at approximately 30-minute intervals or as soon as new information becomes available. Next update by 08:34 UTC.

3. monitoring Jul 19, 2026, 09:54 AM UTC

   Update — 09:50 UTC Git clone error rates for scheduled and triggered job runs in the EMEA region via our GitHub App integration are starting to return to normal. The issue appears to be resolving on its own; no fix has been deployed on our side. We have not yet confirmed a specific root cause — investigation is ongoing, with focus on the GitHub App's authentication path. We are closely monitoring to confirm this recovery holds.

4. monitoring Jul 19, 2026, 10:29 AM UTC

   Update — 10:29 UTC Git clone errors have remained at normal levels since our last update, with no recurrence. No fix was deployed on our side, and a specific root cause has not yet been confirmed. We are continuing to monitor

5. resolved Jul 19, 2026, 01:55 PM UTC

   Update — 13:52 UTC Git clone errors on prod-emea have not recurred and success rates have remained normal. We have not identified a definitive root cause on our side and are continuing to investigate internally. We are resolving this incident, but will follow up if new information becomes available.

Read the full incident report →

Started Jul 16, 2026, 11:48 PM UTC· resolved Jul 17, 2026, 01:00 AM UTC

1. investigating Jul 16, 2026, 11:48 PM UTC

   We're investigating an issue with Studio IDE that is causing the page to refresh. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Deployment jobs are not impacted and should be running as expected.

2. monitoring Jul 17, 2026, 12:16 AM UTC

   Studio IDE has returned to its normal state and we are continuing to monitor.

3. resolved Jul 17, 2026, 01:00 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. We have confirmed that the impact was as a result of a GitHub outage: https://www.githubstatus.com/incidents/gxycch3076xk Please contact Support via email [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →