dbt Cloud incident

[US AWS] us1.dbt.com is unreachable and showing 'something went wrong'

Minor Resolved View vendor source →

dbt Cloud experienced a minor incident on June 30, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 30, 2026, 09:30 PM UTC
Resolved
Jun 30, 2026, 09:30 PM UTC
Duration
—
Detected by Pingoru
Jun 30, 2026, 09:30 PM UTC

Update timeline

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

    Status: Investigating 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. Affected components Metadata API (US AWS) (Operational) Admin API (US AWS) (Operational) Metadata Ingestion (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) Web Application (US AWS) (Full outage) IDE (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Semantic Layer API (US AWS) (Operational) dbt Copilot (US AWS) (Operational)

  2. identified Jun 30, 2026, 06:40 PM UTC

    Status: Identified 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. Affected components dbt platform CLI (US AWS) (Operational) Metadata Ingestion (US AWS) (Operational) Metadata API (US AWS) (Operational) dbt Copilot (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) Semantic Layer API (US AWS) (Operational) Web Application (US AWS) (Full outage) IDE (US AWS) (Operational) Admin API (US AWS) (Operational)

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

    Status: Monitoring 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. Affected components Web Application (US AWS) (Operational) Metadata Ingestion (US AWS) (Operational) Admin API (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) IDE (US AWS) (Operational) Semantic Layer API (US AWS) (Operational) dbt Copilot (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Metadata API (US AWS) (Operational)

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

    Status: Resolved 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. Affected components Scheduled Jobs (US AWS) (Operational) Admin API (US AWS) (Operational) Web Application (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Metadata Ingestion (US AWS) (Operational) Semantic Layer API (US AWS) (Operational) IDE (US AWS) (Operational) Metadata API (US AWS) (Operational) dbt Copilot (US AWS) (Operational)