Companies / dbt Labs / changes
dbt Labs change history
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Unable to Access dbt Platform dbt Labs reported a critical outage affecting dbt Platform web application loading, logins, and Admin API access. It started at 2026-10-13 22:04 UTC and was resolved at 2026-10-14 04:33 UTC, lasting 6 h 29 min. A deployed fix restored normal operation. | Major incident | |
| Major incident: Schema Hydration Panic Major outage: Fusion Stable scheduled jobs and Studio IDE encountered “No schema found for get columns in relation call” errors from 2026-09-18 23:31 UTC to 2026-09-19 14:30 UTC (14 h 58 min). A fix reached Latest and Stable release tracks; customers no longer needed the temporary Fusion Extended workaround. | Major incident | |
| Major incident: State usage metrics not being ingested dbt Labs reported a major degradation in state usage data ingestion across all warehouses, leaving displayed metrics potentially out of date. It started at 2026-09-10 01:19 UTC and was resolved at 2026-09-10 09:14 UTC, lasting 7 h 55 min. A fix was deployed, ingestion fully recovered, and affected data caught up. | Major incident | |
| Major incident: User Login Sessions Terminated dbt Platform users were logged out of active sessions and temporarily unable to log in during a major incident starting 2026-09-08 18:30 UTC. The incident lasted 4 h 46 min and was resolved at 2026-09-08 23:16 UTC after a fix was deployed to prevent sessions from terminating. | Major incident | |
| Critical incident: dbt Platform not responding dbt Labs reported a critical outage in US Cell 1 GCP, with increased API errors and loss of access to dbt; its final update said all services were down. The incident started at 2026-09-04 14:20 UTC and was resolved at 2026-09-04 15:51 UTC (1 h 31 min). The vendor said it implemented measures to prevent recurrence. | Major incident | |
| Major incident: Git Failures in dbt Platform dbt Labs reported a major Git outage starting 2026-08-17 15:02 UTC, lasting 6 h 19 min and resolving at 2026-08-17 21:21 UTC. A widespread GitHub outage caused failures in dbt deps, repository connections, Studio IDE, Scheduled Jobs and GitHub authentication; dbt confirmed all affected systems were functioning normally. | Major incident | |
| Critical incident: Certificate errors affecting the dbt platform A critical dbt platform incident caused certificate or "insecure connection" warnings on US, AU, and EU/EMEA multi-tenant AWS instances after a certificate configuration change. The incident started at 2026-07-27 16:54 UTC and was resolved at 2026-07-27 18:50 UTC, lasting 1 h 56 min; dbt deployed a fix and reported normal access restored. | Major incident | |
| Critical incident: Job runs failing at the git clone step dbt Labs reported a critical outage from 2026-07-21 07:45 UTC to 2026-07-21 12:52 UTC (5 h 7 min). Scheduled, CI, and API-triggered GitHub job runs failed at “Clone git repository” across all regions (multi-tenant and single-tenant) because of upstream GitHub SSH deploy key authentication failures. GitHub resolved the issue; failed runs can be retried. | Major incident | |
| Major incident: Some EMEA customers experiencing Git clone failures (403 errors) on thier accounts Major Git clone failures (403 errors) affected EMEA scheduled and triggered jobs using the GitHub App integration; IDE and CLI were unaffected. Failures began 2026-07-18 23:00 UTC; the incident was tracked from 2026-07-19 07:33 UTC until resolution at 2026-07-19 13:55 UTC (6 h 22 min). Errors normalized without a deployed fix; no definitive root cause was identified. | Major incident |