dbt Cloud Outage History

dbt Cloud is up right now

dbt Cloud had 567 outages in the last 2 years totaling 5h 26m of downtime — averaging 23 incidents per month.

There were 567 dbt Cloud outages since January 27, 2026 totaling 5h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor July 29, 2026

[EMEA AWS] AI Codegen (Wizard) unavailable in EMEA

Detected by Pingoru
Jul 29, 2026, 09:18 AM UTC
Resolved
Jul 29, 2026, 09:18 AM UTC
Duration
Timeline · 2 updates
  1. monitoring Jul 29, 2026, 09:12 AM UTC

    Status: Monitoring Reported at 08:21 UTC on 29 July 2026, we identified errors affecting AI Codegen (Wizard) for users in EMEA. A fix was deployed at 08:35 UTC, and we are currently monitoring — the system appears to be functioning normally. We apologise for any disruption this may have caused. Affected components dbt Copilot (EMEA AWS) (Degraded performance)

  2. resolved Jul 29, 2026, 09:18 AM UTC

    Status: Resolved Since our last update, we've continued to monitor AI Codegen (Wizard) in EMEA and error rates have remained normal. As of 09:16 UTC, 29 July 2026, this incident is resolved. Affected components dbt Copilot (EMEA AWS) (Operational)

Read the full incident report →

Minor July 29, 2026

[EMEA Cell 1 AZURE] AI Codegen (Wizard) unavailable in EMEA

Detected by Pingoru
Jul 29, 2026, 09:18 AM UTC
Resolved
Jul 29, 2026, 09:18 AM UTC
Duration
Timeline · 2 updates
  1. monitoring Jul 29, 2026, 09:12 AM UTC

    Status: Monitoring Reported at 08:21 UTC on 29 July 2026, we identified errors affecting AI Codegen (Wizard) for users in EMEA. A fix was deployed at 08:35 UTC, and we are currently monitoring — the system appears to be functioning normally. We apologise for any disruption this may have caused. Affected components dbt Copilot (EMEA Cell 1 AZURE) (Degraded performance)

  2. resolved Jul 29, 2026, 09:18 AM UTC

    Status: Resolved Since our last update, we've continued to monitor AI Codegen (Wizard) in EMEA and error rates have remained normal. As of 09:16 UTC, 29 July 2026, this incident is resolved. Affected components dbt Copilot (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor July 27, 2026

[APAC AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (APAC AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (APAC AWS) (Operational)

Read the full incident report →

Minor July 27, 2026

[AU2 Cell 1 Azure] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor.

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Minor July 27, 2026

[EMEA AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (EMEA AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor July 27, 2026

[EMEA Cell 1 AZURE] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor.

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions.

Read the full incident report →

Minor July 27, 2026

[US AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (US AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (US AWS) (Operational)

Read the full incident report →

Minor July 27, 2026

[US Cell 1 AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (US Cell 1 AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor July 27, 2026

[US Cell 2 AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (US Cell 2 AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor July 27, 2026

[US Cell 3 AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (US Cell 3 AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor July 27, 2026

[US Cell 4 AWS] Certificate errors affecting the dbt platform

Detected by Pingoru
Jul 27, 2026, 06:50 PM UTC
Resolved
Jul 27, 2026, 06:50 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jul 27, 2026, 06:25 PM UTC

    Status: Investigating We're investigating an issue affecting the dbt platform in production. Users may see certificate warnings or "insecure connection" errors when accessing the platform. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. monitoring Jul 27, 2026, 06:44 PM UTC

    Status: Monitoring We have deployed a fix for the certificate issue that was causing "insecure connection" warnings when accessing the dbt platform on our US1, AU1, and EU1 instances. Access has returned to normal and we are continuing to monitor. Affected components Web Application (US Cell 4 AWS) (Full outage)

  3. resolved Jul 27, 2026, 06:50 PM UTC

    Status: Resolved A certificate configuration change affecting our multi-tenant AWS instances caused browsers to show certificate or "insecure connection" warnings when accessing the dbt platform. This impacted the US, AU, and EU/EMEA multi-tenant instances between approximately 2026-07-27 16:54 UTC and 2026-07-27 18:43 UTC. The issue has been resolved and all affected systems are functioning normally. Please contact Support at [email protected]: mailto:[email protected] if you continue to experience issues or have any follow-up questions. Affected components Web Application (US Cell 4 AWS) (Operational)

Read the full incident report →

Major July 24, 2026

[APAC AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error

Detected by Pingoru
Jul 24, 2026, 08:20 AM UTC
Resolved
Jul 24, 2026, 09:14 AM UTC
Duration
54m
Timeline · 3 updates
  1. investigating Jul 24, 2026, 07:58 AM UTC

    Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)

  2. investigating Jul 24, 2026, 08:01 AM UTC

    Status: Investigating We're investigating an issue with [X component/system] that is causing [the issue’s impact]. This is impacting [X component/system] in [Y region & tenant ] anytime after [H:MM time Eastern]. 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. [X component/system] is not impacted and should be running as expected. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)

  3. investigating Jul 24, 2026, 08:20 AM UTC

    Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (APAC AWS) (Degraded performance)

Read the full incident report →

Major July 24, 2026

[US AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error

Detected by Pingoru
Jul 24, 2026, 08:20 AM UTC
Resolved
Jul 24, 2026, 09:14 AM UTC
Duration
54m
Timeline · 2 updates
  1. investigating Jul 24, 2026, 07:58 AM UTC

    Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. investigating Jul 24, 2026, 08:20 AM UTC

    Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US AWS) (Degraded performance)

Read the full incident report →

Major July 24, 2026

[US Cell 1 AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error

Detected by Pingoru
Jul 24, 2026, 08:20 AM UTC
Resolved
Jul 24, 2026, 09:14 AM UTC
Duration
54m
Timeline · 3 updates
  1. investigating Jul 24, 2026, 07:58 AM UTC

    Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. investigating Jul 24, 2026, 08:01 AM UTC

    Status: Investigating We're investigating an issue with [X component/system] that is causing [the issue’s impact]. This is impacting [X component/system] in [Y region & tenant ] anytime after [H:MM time Eastern]. 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. [X component/system] is not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

  3. investigating Jul 24, 2026, 08:20 AM UTC

    Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)

Read the full incident report →

Major July 24, 2026

[US Cell 2 AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error

Detected by Pingoru
Jul 24, 2026, 08:20 AM UTC
Resolved
Jul 24, 2026, 09:14 AM UTC
Duration
54m
Timeline · 3 updates
  1. investigating Jul 24, 2026, 07:58 AM UTC

    Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. investigating Jul 24, 2026, 08:01 AM UTC

    Status: Investigating We're investigating an issue with [X component/system] that is causing [the issue’s impact]. This is impacting [X component/system] in [Y region & tenant ] anytime after [H:MM time Eastern]. 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. [X component/system] is not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

  3. investigating Jul 24, 2026, 08:20 AM UTC

    Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)

Read the full incident report →

Major July 24, 2026

[US Cell 3 AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error

Detected by Pingoru
Jul 24, 2026, 08:20 AM UTC
Resolved
Jul 24, 2026, 09:14 AM UTC
Duration
54m
Timeline · 3 updates
  1. investigating Jul 24, 2026, 07:58 AM UTC

    Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. investigating Jul 24, 2026, 08:01 AM UTC

    Status: Investigating We're investigating an issue with [X component/system] that is causing [the issue’s impact]. This is impacting [X component/system] in [Y region & tenant ] anytime after [H:MM time Eastern]. 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. [X component/system] is not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

  3. investigating Jul 24, 2026, 08:20 AM UTC

    Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)

Read the full incident report →

Major July 24, 2026

[US Cell 4 AWS] Scheduled jobs are intermittently affected by job failures caused by 403 error

Detected by Pingoru
Jul 24, 2026, 08:20 AM UTC
Resolved
Jul 24, 2026, 09:14 AM UTC
Duration
54m
Timeline · 3 updates
  1. investigating Jul 24, 2026, 07:58 AM UTC

    Status: Investigating We're investigating an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. The issue is currently intermittent. The dbt Cloud IDE and dbt Cloud CLI are not impacted and should be functioning as expected. The team is working on a resolution and we will provide updates as soon as new information becomes available.

  2. investigating Jul 24, 2026, 08:01 AM UTC

    Status: Investigating We're investigating an issue with [X component/system] that is causing [the issue’s impact]. This is impacting [X component/system] in [Y region & tenant ] anytime after [H:MM time Eastern]. 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. [X component/system] is not impacted and should be running as expected. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

  3. investigating Jul 24, 2026, 08:20 AM UTC

    Status: Investigating We're continuing to investigate an issue affecting some job runs across multiple regions. Users may see job runs fail during the git repository clone step, with an error referencing an HTTP 403 response. We've also received a report that this may be affecting the dbt Studio IDE for some users, and we're confirming the scope of that now. The issue is intermittent. Our engineering team is actively investigating and we will provide updates as soon as new information becomes available. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)

Read the full incident report →

Minor July 22, 2026

[APAC AWS] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (APAC AWS) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (APAC AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (APAC AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (APAC AWS) (Operational)

Read the full incident report →

Minor July 22, 2026

[AU2 Cell 1 Azure] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (AU2 Cell 1 Azure) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (AU2 Cell 1 Azure) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (AU2 Cell 1 Azure) (Operational)

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

    Status: Resolved 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. Affected components Web Application (AU2 Cell 1 Azure) (Operational)

Read the full incident report →

Minor July 22, 2026

[EMEA AWS] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (EMEA AWS) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (EMEA AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EMEA AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor July 22, 2026

[EMEA Cell 1 AZURE] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (EMEA Cell 1 AZURE) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor July 22, 2026

[EU Cell 1 GCP] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (EU Cell 1 GCP) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (EU Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EU Cell 1 GCP) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor July 22, 2026

[EU4 Cell 1 GCP] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (EU4 Cell 1 GCP) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (EU4 Cell 1 GCP) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (EU4 Cell 1 GCP) (Operational)

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

    Status: Resolved 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. Affected components Web Application (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor July 22, 2026

[JP Cell 1 AWS] Unable to create or edit environment variables in dbt platform user interface

Detected by Pingoru
Jul 22, 2026, 07:29 AM UTC
Resolved
Jul 22, 2026, 07:29 AM UTC
Duration
Timeline · 5 updates
  1. investigating Jul 22, 2026, 01:52 AM UTC

    Status: Investigating 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

    Status: Investigating 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. Affected components Web Application (JP Cell 1 AWS) (Degraded performance)

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

    Status: Identified 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. Affected components Web Application (JP Cell 1 AWS) (Degraded performance)

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

    Status: Monitoring 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. Affected components Web Application (JP Cell 1 AWS) (Operational)

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

    Status: Resolved 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. Affected components Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →