dbt Cloud Outage History

Status: Resolved Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata. Affected components Metadata API (US Cell 1 AZURE) (Operational)

Status: Resolved Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata. Affected components Metadata API (US Cell 1 GCP) (Operational)

Status: Resolved Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata. Affected components Metadata API (US Cell 2 AWS) (Operational)

Status: Resolved Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata. Affected components Metadata API (US Cell 3 AWS) (Operational)

Status: Resolved Between approximately 3:00 PM ET on April 6 and 11:30 AM ET on April 7, the Discovery API was returning stale model applied state data. Model metadata such as last execution timestamps and related attributes were not updating correctly after successful dbt Cloud job runs, causing incorrect data to be displayed in dbt Explorer and via the Discovery API. A fix was deployed to the metadata ingestion pipeline at 11:30 AM ET on April 7 and the incident was resolved. Going forward, metadata will update correctly after each successful run. Models affected during this period will not be retroactively corrected - users will need to trigger a new dbt Cloud run to refresh their metadata. Affected components Metadata API (US Cell 4 AWS) (Operational)

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Between 5:09 AM Eastern and 5:17AM Eastern an issue with the Scheduled Jobs resulted in Delayed Runs and Run Locks in US MT. The issue has since resolved itself. 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 Metadata Ingestion (US AWS) (Operational) Web Application (US AWS) (Operational) Scheduled Jobs (US AWS) (Operational) Metadata API (US AWS) (Operational) Semantic Layer API (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) dbt Copilot (US AWS) (Operational) Admin API (US AWS) (Operational) IDE (US AWS) (Operational)

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. Between 19:43 UTC and 20:09 UTC an issue with an internal service latency resulted in delays and failures of dbt invocations. We have put measures in place to prevent a recurrence and dbt invocations have returned to normal. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience delays and are unsure of the root cause. Affected components Metadata API (EMEA Cell 1 AZURE) (Operational) Admin API (EMEA Cell 1 AZURE) (Operational) Semantic Layer API (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational) dbt Copilot (EMEA Cell 1 AZURE) (Operational) IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational) Scheduled Jobs (EMEA Cell 1 AZURE) (Operational) Metadata Ingestion (EMEA Cell 1 AZURE) (Operational)

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 20:09 UTC. Between 19:43 UTC and 20:09 UTC an issue with an internal service latency resulted in delays and failures of dbt invocations. We have put measures in place to prevent a recurrence and dbt invocations have returned to normal. Please contact Support via email [email protected]: http://[email protected]/ if you continue to experience delays and are unsure of the root cause. Affected components Web Application (US Cell 1 AZURE) (Operational) Metadata Ingestion (US Cell 1 AZURE) (Operational) Admin API (US Cell 1 AZURE) (Operational) Metadata API (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational) Semantic Layer API (US Cell 1 AZURE) (Operational) dbt Copilot (US Cell 1 AZURE) (Operational) IDE (US Cell 1 AZURE) (Operational) Scheduled Jobs (US Cell 1 AZURE) (Operational)

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 7:43am Eastern. Between 5:56am Eastern and 7:43am Eastern, an issue with the internal database server resulted in users on the dbt Azure US Multi-Cell environment being unable to access the platform or experiencing service unavailability, Affected components IDE (US Cell 1 AZURE) (Operational) Scheduled Jobs (US Cell 1 AZURE) (Operational) Admin API (US Cell 1 AZURE) (Operational) Metadata API (US Cell 1 AZURE) (Operational) Metadata Ingestion (US Cell 1 AZURE) (Operational) dbt Copilot (US Cell 1 AZURE) (Operational) dbt platform CLI (US Cell 1 AZURE) (Operational) Web Application (US Cell 1 AZURE) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (APAC AWS) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (EMEA AWS) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (EMEA Cell 1 AZURE) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (EU Cell 1 GCP) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (EU4 Cell 1 GCP) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (JP Cell 1 AWS) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US AWS) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US Cell 1 AWS) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US Cell 1 AZURE) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US Cell 1 GCP) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US Cell 2 AWS) (Operational)

Status: Resolved The OpenAI outage has now been reported as resolved: https://status.openai.com/incidents/01KMP0CDV3T8QX1YPXHQMRN2EP. Please contact us at [email protected] if you encounter any issues and are unsure of the root cause. Affected components dbt Copilot (US Cell 3 AWS) (Operational)