dbt Cloud Outage History
dbt Cloud is up right nowdbt Cloud had 699 outages in the last 2 years totaling 4h 4m of downtime — averaging 29 incidents per month.
There were 699 dbt Cloud outages since January 27, 2026 totaling 4h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
[AU2 Cell 1 Azure] Schema Hydration Panic
Timeline · 7 updates
[EMEA AWS] Schema Hydration Panic
Timeline · 7 updates
[EMEA Cell 1 AZURE] Schema Hydration Panic
Timeline · 7 updates
[EU Cell 1 GCP] Schema Hydration Panic
Timeline · 7 updates
[EU4 Cell 1 GCP] Schema Hydration Panic
Timeline · 7 updates
[JP Cell 1 AWS] Schema Hydration Panic
Timeline · 7 updates
[US AWS] Schema Hydration Panic
Timeline · 7 updates
[US Cell 1 AWS] Schema Hydration Panic
Timeline · 7 updates
[US Cell 1 AZURE] Schema Hydration Panic
Timeline · 7 updates
[US Cell 1 GCP] Schema Hydration Panic
Timeline · 7 updates
[US Cell 2 AWS] Schema Hydration Panic
Timeline · 7 updates
[US Cell 3 AWS] Schema Hydration Panic
Timeline · 7 updates
[US Cell 4 AWS] Schema Hydration Panic
Timeline · 7 updates
[US5 Cell 1 AWS] Schema Hydration Panic
Timeline · 7 updates
[US Cell 1 AWS] Intermittent errors on the Discovery API
Timeline · 2 updates
- monitoring Sep 10, 2026, 02:28 PM UTC
Status: Monitoring We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved. Affected components Metadata API (US Cell 1 AWS) (Degraded performance)
- resolved Sep 10, 2026, 04:45 PM UTC
Status: Resolved 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. Affected components Metadata API (US Cell 1 AWS) (Operational)
[US Cell 2 AWS] Intermittent errors on the Discovery API
Timeline · 2 updates
- monitoring Sep 10, 2026, 02:28 PM UTC
Status: Monitoring We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved. Affected components Metadata API (US Cell 2 AWS) (Degraded performance)
- resolved Sep 10, 2026, 04:45 PM UTC
Status: Resolved 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. Affected components Metadata API (US Cell 2 AWS) (Operational)
[US Cell 3 AWS] Intermittent errors on the Discovery API
Timeline · 2 updates
- monitoring Sep 10, 2026, 02:28 PM UTC
Status: Monitoring We've deployed a fix for an issue affecting the Discovery API that caused intermittent errors for some job run and metadata queries. This impacted customers on our North America multi-tenant deployment between approximately 9:03 AM and 9:35 AM ET. EU and Single Tenant deployments were not affected. The Discovery API has returned to normal operation and we're continuing to monitor before marking this resolved. Affected components Metadata API (US Cell 3 AWS) (Degraded performance)
- resolved Sep 10, 2026, 04:45 PM UTC
Status: Resolved 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. Affected components Metadata API (US Cell 3 AWS) (Operational)
[AU2 Cell 1 Azure] dbt Copilot unavailable on Azure single-tenant deployments
Timeline · 1 update
- investigating Sep 10, 2026, 04:39 PM UTC
Status: Investigating We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly. Affected components dbt Copilot (AU2 Cell 1 Azure) (Degraded performance)
[EMEA Cell 1 AZURE] dbt Copilot unavailable on Azure single-tenant deployments
Timeline · 1 update
- investigating Sep 10, 2026, 04:39 PM UTC
Status: Investigating We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly. Affected components dbt Copilot (EMEA Cell 1 AZURE) (Degraded performance)
[US Cell 1 AZURE] dbt Copilot unavailable on Azure single-tenant deployments
Timeline · 1 update
- investigating Sep 10, 2026, 04:39 PM UTC
Status: Investigating We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly. Affected components dbt Copilot (US Cell 1 AZURE) (Degraded performance)
[US AWS] Increased error rates associated with dbt MCP and dbt Wizard
Timeline · 3 updates
- investigating Sep 10, 2026, 01:46 PM UTC
Status: Investigating We're currently investigating an increase in errors related to dbt MCP and Wizard. The team is working on a resolution and we will provide updates as soon as new information becomes available. Affected components dbt Copilot (US AWS) (Degraded performance)
- monitoring Sep 10, 2026, 02:08 PM UTC
Status: Monitoring We have deployed a fix to mitigate the issue and are currently monitoring. Affected components dbt Copilot (US AWS) (Degraded performance)
- resolved Sep 10, 2026, 02:27 PM UTC
Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 1:57 PM UTC Affected components dbt Copilot (US AWS) (Operational)
[APAC AWS] State usage metrics not being ingested
Timeline · 4 updates
- investigating Sep 10, 2026, 08:02 AM UTC
Status: Investigating We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this. Affected components Metadata Ingestion (APAC AWS) (Degraded performance)
- identified Sep 10, 2026, 08:14 AM UTC
Status: Identified We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience. Affected components Metadata Ingestion (APAC AWS) (Degraded performance)
- monitoring Sep 10, 2026, 08:52 AM UTC
Status: Monitoring A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this. Affected components Metadata Ingestion (APAC AWS) (Operational)
- resolved Sep 10, 2026, 09:14 AM UTC
Status: Resolved This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience Affected components Metadata Ingestion (APAC AWS) (Operational)
[AU2 Cell 1 Azure] State usage metrics not being ingested
Timeline · 4 updates
- investigating Sep 10, 2026, 08:02 AM UTC
Status: Investigating We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this. Affected components Metadata Ingestion (AU2 Cell 1 Azure) (Degraded performance)
- identified Sep 10, 2026, 08:14 AM UTC
Status: Identified We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience. Affected components Metadata Ingestion (AU2 Cell 1 Azure) (Degraded performance)
- monitoring Sep 10, 2026, 08:52 AM UTC
Status: Monitoring A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this. Affected components Metadata Ingestion (AU2 Cell 1 Azure) (Operational)
- resolved Sep 10, 2026, 09:14 AM UTC
Status: Resolved This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience Affected components Metadata Ingestion (AU2 Cell 1 Azure) (Operational)
[EMEA AWS] State usage metrics not being ingested
Timeline · 4 updates
- investigating Sep 10, 2026, 08:02 AM UTC
Status: Investigating We're currently investigating an issue affecting the ingestion of state usage data. As a result, state usage data displayed may not reflect the most recent activity and could appear out of date. This is affecting accounts across all warehouses. Our team is actively investigating the cause, and we will share a further update within the next hour. We apologize for any inconvenience and appreciate your patience while we work to resolve this. Affected components Metadata Ingestion (EMEA AWS) (Degraded performance)
- identified Sep 10, 2026, 08:14 AM UTC
Status: Identified We've identified the cause of the issue affecting the ingestion of state usage data and are rolling out a fix now. State usage data may continue to appear out of date until the fix is fully deployed and the affected data has backfilled. We'll post an update once we've confirmed the issue is resolved and data has caught up. We apologize for the inconvenience and appreciate your patience. Affected components Metadata Ingestion (EMEA AWS) (Degraded performance)
- monitoring Sep 10, 2026, 08:52 AM UTC
Status: Monitoring A fix for the issue affecting ingestion of state usage data has been deployed. We're now monitoring to confirm state usage data has fully caught up and remains accurate. We'll post a final update once we've confirmed the issue is resolved.Thank you for your patience while we worked through this. Affected components Metadata Ingestion (EMEA AWS) (Operational)
- resolved Sep 10, 2026, 09:14 AM UTC
Status: Resolved This incident has been resolved. State usage data ingestion has fully recovered, and affected data has caught up. We apologize for any inconvenience this may have caused and thank you for your patience Affected components Metadata Ingestion (EMEA AWS) (Operational)