dbt Cloud incident
[EMEA Cell 1 AZURE] Snowflake Authentication failure in Development environments if the Account name has an '_'
dbt Cloud experienced a minor incident on June 25, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Jun 24, 2026, 04:14 PM UTC
Status: Identified 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. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)
- monitoring Jun 24, 2026, 07:18 PM UTC
Status: Monitoring 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. Affected components IDE (EMEA Cell 1 AZURE) (Operational)
- resolved Jun 25, 2026, 03:41 PM UTC
Status: Resolved 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. Affected components IDE (EMEA Cell 1 AZURE) (Operational)