dbt Cloud Outage History

Started Jul 29, 2026, 09:12 AM UTC· resolved Jul 29, 2026, 09:18 AM UTC

1. monitoring Jul 29, 2026, 09:12 AM UTC

   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.

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

   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.

Read the full incident report →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 27, 2026, 06:25 PM UTC· resolved Jul 27, 2026, 06:50 PM UTC

1. investigating Jul 27, 2026, 06:25 PM UTC

   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

   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

   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 →

Started Jul 24, 2026, 08:20 AM UTC· resolved Jul 24, 2026, 09:14 AM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

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

   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.

Read the full incident report →

Started Jul 24, 2026, 08:20 AM UTC· resolved Jul 24, 2026, 09:14 AM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

Read the full incident report →

Started Jul 24, 2026, 08:20 AM UTC· resolved Jul 24, 2026, 09:14 AM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

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

   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.

Read the full incident report →

Started Jul 24, 2026, 08:20 AM UTC· resolved Jul 24, 2026, 09:14 AM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

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

   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.

Read the full incident report →

Started Jul 24, 2026, 08:20 AM UTC· resolved Jul 24, 2026, 09:14 AM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

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

   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.

Read the full incident report →

Started Jul 24, 2026, 08:20 AM UTC· resolved Jul 24, 2026, 09:14 AM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

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

   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.

Read the full incident report →

Started Jul 24, 2026, 07:58 AM UTC· resolved Jul 24, 2026, 02:58 PM UTC

1. investigating Jul 24, 2026, 07:58 AM UTC

   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

   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.

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

   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.

4. investigating Jul 24, 2026, 09:05 AM UTC

   We're continuing to investigate an issue causing intermittent job run failures during the git repository clone step, with an error referencing an HTTP 403 response. We've reduced the scope of this issue, it is affecting our EMEA infrastructure only. We're still confirming whether the dbt Studio IDE is affected for any users. Our engineering team continues to investigate and we will provide a further update within the hour.

5. investigating Jul 24, 2026, 09:30 AM UTC

   We're continuing to investigate an issue causing intermittent job run failures during the git repository clone step, with an error referencing an HTTP 403 response, affecting our EMEA infrastructure only. Based on further investigation, we do not believe the dbt Studio IDE has been affected by this issue. Our engineering team continues to investigate and we will provide a further update within the hour.

6. investigating Jul 24, 2026, 10:14 AM UTC

   The rate of job failures during the git repository clone step has dropped significantly. We have not identified or deployed a specific fix, and we're continuing to closely monitor to confirm this improvement holds. We'll provide a further update once we can confirm full recovery, or sooner if the issue resumes.

7. investigating Jul 24, 2026, 10:43 AM UTC

   The rate of job failures during the git repository clone step remains much lower than earlier today, though we're continuing to see occasional, isolated failures. A root cause has not yet been confirmed. We're continuing to closely monitor and will provide a further update within the hour, or sooner if there is a material change.

8. investigating Jul 24, 2026, 11:26 AM UTC

   We saw a further burst of job failures during the git repository clone step earlier, consistent with the intermittent pattern we've seen throughout this incident. A root cause has not yet been confirmed. We're continuing to closely monitor and investigate, and will provide a further update within the hour, or sooner if there is a material change.

9. investigating Jul 24, 2026, 11:46 AM UTC

   We're continuing to investigate intermittent job failures during the git repository clone step, affecting our EMEA infrastructure. Failure rates have dropped significantly since earlier today, and we've seen no further occurrences in the last 30 minutes. A root cause has not yet been confirmed. We're continuing to closely monitor and will provide a further update within the hour, or sooner if there is a material change.

10. investigating Jul 24, 2026, 12:25 PM UTC

    "We're continuing to closely monitor an issue causing intermittent job failures during the git repository clone step within our EMEA infrastructure. We have seen no further occurrences in the last 45 minutes, though a root cause has not yet been confirmed. We will provide a further update within the hour, or sooner if there is a material change. "

11. monitoring Jul 24, 2026, 12:31 PM UTC

    Failure rates for job runs during the git repository clone step in our EMEA infrastructure remain at normal levels, with no further occurrences in the last 60 minutes. We have not identified or deployed a specific fix, and we are continuing to closely monitor. We will provide a further update once we can confirm full resolution, or sooner if the issue recurs.

12. resolved Jul 24, 2026, 02:58 PM UTC

    Intermittent job run failures during the git repository clone step affected our EMEA infrastructure. This impacted job runs between 2026-07-24 00:00 UTC and 2026-07-24 11:08 UTC. The issue has not recurred for over 3.5 hours 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 →

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 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 →