dbt Cloud Outage History

Started Jul 10, 2026, 12:19 PM UTC· resolved Jul 10, 2026, 02:46 PM UTC

1. monitoring Jul 10, 2026, 12:19 PM UTC

   Beginning at approximately 2026-07-10 09:40 UTC, some users experienced intermittent slowness when signing in to login.dbt.com: http://login.dbt.com or loading account information, caused by an infrastructure resource constraint affecting a backend service. We identified the cause and applied a mitigation at approximately 2026-07-10 10:45 UTC, and performance returned to normal by approximately 2026-07-10 10:50 UTC. We are continuing to monitor while we work on a permanent fix.

2. resolved Jul 10, 2026, 02:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 10:50 UTC. Between 09:40 UTC and 10:50 UTC, an issue affecting login.dbt.com: http://login.dbt.com and account discovery resulted in intermittent slowness when signing in and loading account information. We have put measures in place to prevent a recurrence and the affected services have returned to normal. Please contact Support via email at [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jul 10, 2026, 12:19 PM UTC· resolved Jul 10, 2026, 02:46 PM UTC

1. monitoring Jul 10, 2026, 12:19 PM UTC

   Beginning at approximately 2026-07-10 09:40 UTC, some users experienced intermittent slowness when signing in to login.dbt.com: http://login.dbt.com or loading account information, caused by an infrastructure resource constraint affecting a backend service. We identified the cause and applied a mitigation at approximately 2026-07-10 10:45 UTC, and performance returned to normal by approximately 2026-07-10 10:50 UTC. We are continuing to monitor while we work on a permanent fix.

2. resolved Jul 10, 2026, 02:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 10:50 UTC. Between 09:40 UTC and 10:50 UTC, an issue affecting login.dbt.com: http://login.dbt.com and account discovery resulted in intermittent slowness when signing in and loading account information. We have put measures in place to prevent a recurrence and the affected services have returned to normal. Please contact Support via email at [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jul 10, 2026, 12:19 PM UTC· resolved Jul 10, 2026, 02:46 PM UTC

1. monitoring Jul 10, 2026, 12:19 PM UTC

   Beginning at approximately 2026-07-10 09:40 UTC, some users experienced intermittent slowness when signing in to login.dbt.com: http://login.dbt.com or loading account information, caused by an infrastructure resource constraint affecting a backend service. We identified the cause and applied a mitigation at approximately 2026-07-10 10:45 UTC, and performance returned to normal by approximately 2026-07-10 10:50 UTC. We are continuing to monitor while we work on a permanent fix.

2. resolved Jul 10, 2026, 02:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 10:50 UTC. Between 09:40 UTC and 10:50 UTC, an issue affecting login.dbt.com: http://login.dbt.com and account discovery resulted in intermittent slowness when signing in and loading account information. We have put measures in place to prevent a recurrence and the affected services have returned to normal. Please contact Support via email at [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jul 10, 2026, 12:19 PM UTC· resolved Jul 10, 2026, 02:46 PM UTC

1. monitoring Jul 10, 2026, 12:19 PM UTC

   Beginning at approximately 2026-07-10 09:40 UTC, some users experienced intermittent slowness when signing in to login.dbt.com: http://login.dbt.com or loading account information, caused by an infrastructure resource constraint affecting a backend service. We identified the cause and applied a mitigation at approximately 2026-07-10 10:45 UTC, and performance returned to normal by approximately 2026-07-10 10:50 UTC. We are continuing to monitor while we work on a permanent fix.

2. resolved Jul 10, 2026, 02:46 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 10:50 UTC. Between 09:40 UTC and 10:50 UTC, an issue affecting login.dbt.com: http://login.dbt.com and account discovery resulted in intermittent slowness when signing in and loading account information. We have put measures in place to prevent a recurrence and the affected services have returned to normal. Please contact Support via email at [email protected]: mailto:[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jul 07, 2026, 12:55 AM UTC· resolved Jul 07, 2026, 01:30 AM UTC

1. monitoring Jul 07, 2026, 12:55 AM UTC

   From ~00:01 UTC until ~00:06 UTC, a small number of deployment jobs may have experience a brief delay of ~4s (minimum) to ~5m (maximum) before starting. The underlying transient network issue has been resolved and we are continuing to monitor. There has been no other impact. Please contact us at [email protected] with any questions or concerns.

2. resolved Jul 07, 2026, 01:30 AM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 30, 2026, 06:36 PM UTC· resolved Jun 30, 2026, 09:30 PM UTC

1. investigating Jun 30, 2026, 06:36 PM UTC

   We're investigating an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. 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 Jun 30, 2026, 06:40 PM UTC

   We have identified an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error.. A fix is being implemented, and we will provide an update shortly.

3. monitoring Jun 30, 2026, 09:12 PM UTC

   We have deployed a fix for the API gateway domain that was causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. The website has returned to its normal state and we are continuing to monitor.

4. resolved Jun 30, 2026, 09:30 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5:12PM Eastern. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 30, 2026, 06:36 PM UTC· resolved Jun 30, 2026, 09:30 PM UTC

1. investigating Jun 30, 2026, 06:36 PM UTC

   We're investigating an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. 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 Jun 30, 2026, 06:40 PM UTC

   We have identified an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error.. A fix is being implemented, and we will provide an update shortly.

3. monitoring Jun 30, 2026, 09:12 PM UTC

   We have deployed a fix for the API gateway domain that was causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. The website has returned to its normal state and we are continuing to monitor.

4. resolved Jun 30, 2026, 09:30 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5:12PM Eastern. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 30, 2026, 06:36 PM UTC· resolved Jun 30, 2026, 09:30 PM UTC

1. investigating Jun 30, 2026, 06:36 PM UTC

   We're investigating an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. 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 Jun 30, 2026, 06:40 PM UTC

   We have identified an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error.. A fix is being implemented, and we will provide an update shortly.

3. monitoring Jun 30, 2026, 09:12 PM UTC

   We have deployed a fix for the API gateway domain that was causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. The website has returned to its normal state and we are continuing to monitor.

4. resolved Jun 30, 2026, 09:30 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5:12PM Eastern. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 30, 2026, 06:36 PM UTC· resolved Jun 30, 2026, 09:30 PM UTC

1. investigating Jun 30, 2026, 06:36 PM UTC

   We're investigating an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. 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 Jun 30, 2026, 06:40 PM UTC

   We have identified an issue that is causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error.. A fix is being implemented, and we will provide an update shortly.

3. monitoring Jun 30, 2026, 09:12 PM UTC

   We have deployed a fix for the API gateway domain that was causing the dbt login flow to be unreachable and sign-ups via the dbt VS Code extension to fail, displaying a "something went wrong" error. The website has returned to its normal state and we are continuing to monitor.

4. resolved Jun 30, 2026, 09:30 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 5:12PM Eastern. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 04:14 PM UTC· resolved Jun 25, 2026, 03:41 PM UTC

1. identified Jun 24, 2026, 04:14 PM UTC

   We are currently investigating an issue affecting Snowflake connections in dbt Cloud Development environments. Users attempting to set up new Snowflake connections with account identifiers containing underscores experience authorization failures. Existing sessions are not impacted, this only impacts new users re-authenticating to snowflake in the developer credentials. Workaround: Replace underscores with hyphens in the Snowflake Account field in your dbt Cloud connection settings (for example, my_account → my-account) and avoid using dynamic configuration containing {{env_var()}} config in the hostname field. Please reach out to [email protected] if you have any further queries.

2. monitoring Jun 24, 2026, 07:18 PM UTC

   We have deployed a fix for the Snowflake issue that was causing authentication issue affecting accounts with underscores in the account identifier. Rollout is now complete across production tenants. We are monitoring to confirm error rates remain at baseline. Please reach out to [email protected] if you have any further questions.

3. resolved Jun 25, 2026, 03:41 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally as of 20:18 UTC. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →

Started Jun 24, 2026, 02:00 PM UTC· resolved Jun 24, 2026, 02:00 PM UTC

1. resolved Jun 24, 2026, 02:00 PM UTC

   From 24 June 2:00 PM UTC to 25 June 2:00 PM UTC, users may have experienced latency or brief unavailability in API requests. These may have resulted in failed API requests, or job runs statuses not updating correctly. The issue has since been resolved and there should be no further impact. Please contact us at [email protected] with any questions or concerns. We thank you for your patience and understanding.

Read the full incident report →

Started Jun 19, 2026, 05:19 PM UTC· resolved Jun 19, 2026, 06:36 PM UTC

1. investigating Jun 19, 2026, 05:19 PM UTC

   We're investigating an issue with the Studio IDE that is causing the LSP Server connection to error. This is impacting server status and compilation in the Studio IDE anytime after June 18th around 2 PM 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.

2. identified Jun 19, 2026, 05:36 PM UTC

   We have identified an issue with the Studio IDE that is causing the LSP Server connection to error. A fix is being implemented, and we will provide an update shortly.

3. monitoring Jun 19, 2026, 05:50 PM UTC

   We have deployed a fix with the Studio IDE that is causing the LSP Server connection to error. We are continuing to monitor.

4. resolved Jun 19, 2026, 06:36 PM UTC

   The issue has been resolved, and all affected systems are now functioning normally. Please contact Support via email [email protected] "[email protected]": http://[email protected] if you continue to experience delays and are unsure of the root cause.

Read the full incident report →