dbt Cloud Outage History

dbt Cloud is up right now

There were 292 dbt Cloud outages since February 4, 2026 totaling 6h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor March 6, 2026

[US Cell 1 GCP] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 dbt platform CLI (US Cell 1 GCP) (Degraded performance) Web Application (US Cell 1 GCP) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 1 GCP) (Degraded performance) Web Application (US Cell 1 GCP) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 1 GCP) (Operational) Web Application (US Cell 1 GCP) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (US Cell 1 GCP) (Partial outage) Web Application (US Cell 1 GCP) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 GCP) (Partial outage) dbt platform CLI (US Cell 1 GCP) (Partial outage) Web Application (US Cell 1 GCP) (Operational)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational) dbt platform CLI (US Cell 1 GCP) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 dbt platform CLI (US Cell 1 GCP) (Operational) IDE (US Cell 1 GCP) (Operational) Web Application (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 2 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 Web Application (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US Cell 2 AWS) (Degraded performance) dbt platform CLI (US Cell 2 AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 2 AWS) (Operational) Web Application (US Cell 2 AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 Web Application (US Cell 2 AWS) (Partial outage) dbt platform CLI (US Cell 2 AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 2 AWS) (Partial outage) Web Application (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 dbt platform CLI (US Cell 2 AWS) (Operational) IDE (US Cell 2 AWS) (Operational) Web Application (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 3 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 dbt platform CLI (US Cell 3 AWS) (Degraded performance) Web Application (US Cell 3 AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 3 AWS) (Degraded performance) Web Application (US Cell 3 AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 3 AWS) (Operational) Web Application (US Cell 3 AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 Web Application (US Cell 3 AWS) (Partial outage) dbt platform CLI (US Cell 3 AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Partial outage) IDE (US Cell 3 AWS) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational) Web Application (US Cell 3 AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 Web Application (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Operational) IDE (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 4 AWS] Elevated errors in dbt Cloud CLI and Studio on multiple instances

Detected by Pingoru
Mar 06, 2026, 10:05 PM UTC
Resolved
Mar 06, 2026, 10:05 PM UTC
Duration
—
Timeline · 7 updates
  1. investigating Mar 06, 2026, 06:32 PM UTC

    Status: Investigating We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. 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 Web Application (US Cell 4 AWS) (Degraded performance) dbt platform CLI (US Cell 4 AWS) (Degraded performance)

  2. identified Mar 06, 2026, 06:47 PM UTC

    Status: Identified We're investigating an issue with dbt Cloud CLI and Studio that is causing elevated 5xx errors to users globally. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US Cell 4 AWS) (Degraded performance) dbt platform CLI (US Cell 4 AWS) (Degraded performance)

  3. monitoring Mar 06, 2026, 07:02 PM UTC

    Status: Monitoring We have deployed a fix for an issue with dbt Cloud CLI and Studio that caused elevated 5xx errors to users globally. dbt Cloud CLI and Studio has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 4 AWS) (Operational) Web Application (US Cell 4 AWS) (Operational)

  4. investigating Mar 06, 2026, 07:05 PM UTC

    Status: Investigating We're investigating the session occupied errors in Studio. 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 dbt platform CLI (US Cell 4 AWS) (Partial outage) Web Application (US Cell 4 AWS) (Partial outage)

  5. identified Mar 06, 2026, 08:29 PM UTC

    Status: Identified We have identified the cause of the session occupied errors in Studio. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 4 AWS) (Partial outage) Web Application (US Cell 4 AWS) (Operational) dbt platform CLI (US Cell 4 AWS) (Partial outage)

  6. monitoring Mar 06, 2026, 09:07 PM UTC

    Status: Monitoring We have deployed a fix for the cause of the session occupied errors in Studio. Studio IDE has returned to its normal state and we are continuing to monitor. Affected components dbt platform CLI (US Cell 4 AWS) (Operational) Web Application (US Cell 4 AWS) (Operational) IDE (US Cell 4 AWS) (Operational)

  7. resolved Mar 06, 2026, 10:05 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 Web Application (US Cell 4 AWS) (Operational) IDE (US Cell 4 AWS) (Operational) dbt platform CLI (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[APAC AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (APAC AWS) (Partial outage) Metadata API (APAC AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (APAC AWS) (Operational) Metadata API (APAC AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[EMEA AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (EMEA AWS) (Partial outage) Metadata API (EMEA AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (EMEA AWS) (Operational) Metadata API (EMEA AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[EMEA Cell 1 AZURE] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (EMEA Cell 1 AZURE) (Partial outage) Metadata API (EMEA Cell 1 AZURE) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (EMEA Cell 1 AZURE) (Operational) Metadata API (EMEA Cell 1 AZURE) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 (EMEA Cell 1 AZURE) (Operational) Web Application (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 6, 2026

[EU Cell 1 GCP] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (EU Cell 1 GCP) (Partial outage) Metadata API (EU Cell 1 GCP) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Metadata API (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (EU Cell 1 GCP) (Operational) Metadata API (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[EU4 Cell 1 GCP] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (EU4 Cell 1 GCP) (Partial outage) Web Application (EU4 Cell 1 GCP) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Metadata API (EU4 Cell 1 GCP) (Operational) Web Application (EU4 Cell 1 GCP) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (EU4 Cell 1 GCP) (Operational) Metadata API (EU4 Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[US AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US AWS) (Partial outage) Metadata API (US AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (US AWS) (Operational) Metadata API (US AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 AWS) (Operational) Web Application (US AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 1 AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Web Application (US Cell 1 AWS) (Partial outage) Metadata API (US Cell 1 AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 1 AWS) (Operational) Metadata API (US Cell 1 AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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) Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 1 AZURE] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (US Cell 1 AZURE) (Partial outage) Web Application (US Cell 1 AZURE) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Metadata API (US Cell 1 AZURE) (Operational) Web Application (US Cell 1 AZURE) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (US Cell 1 AZURE) (Operational) Metadata API (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 1 GCP] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (US Cell 1 GCP) (Partial outage) Web Application (US Cell 1 GCP) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Metadata API (US Cell 1 GCP) (Operational) Web Application (US Cell 1 GCP) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (US Cell 1 GCP) (Operational) Metadata API (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 2 AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (US Cell 2 AWS) (Partial outage) Web Application (US Cell 2 AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 2 AWS) (Operational) Metadata API (US Cell 2 AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (US Cell 2 AWS) (Operational) Metadata API (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 3 AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (US Cell 3 AWS) (Partial outage) Web Application (US Cell 3 AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Web Application (US Cell 3 AWS) (Operational) Metadata API (US Cell 3 AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (US Cell 3 AWS) (Operational) Metadata API (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 4 AWS] Metadata API returning HTTP 500 errors

Detected by Pingoru
Mar 06, 2026, 06:10 PM UTC
Resolved
Mar 06, 2026, 06:10 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:35 PM UTC

    Status: Identified We have identified an issue with Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. A fix is being implemented, and we will provide an update shortly. Affected components Metadata API (US Cell 4 AWS) (Partial outage) Web Application (US Cell 4 AWS) (Partial outage)

  2. monitoring Mar 06, 2026, 06:03 PM UTC

    Status: Monitoring We have deployed a fix for Metadata API that resulted in API calls returning HTTP 500 errors on all GraphQL queries. The Metadata API calls has returned to its normal state and we are continuing to monitor. Affected components Metadata API (US Cell 4 AWS) (Operational) Web Application (US Cell 4 AWS) (Operational)

  3. resolved Mar 06, 2026, 06:10 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 Web Application (US Cell 4 AWS) (Operational) Metadata API (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor March 5, 2026

[EU Cell 1 GCP] Connectivity Errors When Starting dbt Studio and Deployment Runs

Detected by Pingoru
Mar 05, 2026, 06:55 PM UTC
Resolved
Mar 05, 2026, 06:55 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 05, 2026, 03:57 PM UTC

    Status: Investigating We are investigating an intermittent issue with an internal service that is causing connectivity failures. As a result, some users in the GCP US and EMEA regions may experience: 1. Failures when starting dbt Studio sessions 2. Delays when executing or cancelling deployment runs This behavior has been observed starting around 10:18 AM Eastern. Our engineering team is actively working on a resolution. We will post the next update in approximately 15 minutes, or sooner if new information becomes available. Affected components IDE (EU Cell 1 GCP) (Full outage) Scheduled Jobs (EU Cell 1 GCP) (Full outage)

  2. monitoring Mar 05, 2026, 05:11 PM UTC

    Status: Monitoring We have deployed a fix for connectivity issues in an internal service that was causing failures in starting dbt Studio and delays in executing/canceling deployment runs. Both dbt Studio and scheduled jobs have returned to its normal state and we are continuing to monitor. Affected components Scheduled Jobs (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)

  3. resolved Mar 05, 2026, 06:55 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-03-05 8:06 PM EST. Between 10:18 AM EST and 8:06 PM EST an issue with an internal service resulted in failures in starting dbt Studio and scheduled jobs . We have put measures in place to prevent a recurrence and the dbt Studio and scheduled jobs have returned to normal. 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 (EU Cell 1 GCP) (Operational) Scheduled Jobs (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 5, 2026

[US Cell 1 GCP] Connectivity Errors When Starting dbt Studio and Deployment Runs

Detected by Pingoru
Mar 05, 2026, 06:55 PM UTC
Resolved
Mar 05, 2026, 06:55 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 05, 2026, 03:57 PM UTC

    Status: Investigating We are investigating an intermittent issue with an internal service that is causing connectivity failures. As a result, some users in the GCP US and EMEA regions may experience: 1. Failures when starting dbt Studio sessions 2. Delays when executing or cancelling deployment runs This behavior has been observed starting around 10:18 AM Eastern. Our engineering team is actively working on a resolution. We will post the next update in approximately 15 minutes, or sooner if new information becomes available. Affected components IDE (US Cell 1 GCP) (Full outage) Scheduled Jobs (US Cell 1 GCP) (Full outage)

  2. monitoring Mar 05, 2026, 05:11 PM UTC

    Status: Monitoring We have deployed a fix for connectivity issues in an internal service that was causing failures in starting dbt Studio and delays in executing/canceling deployment runs. Both dbt Studio and scheduled jobs have returned to its normal state and we are continuing to monitor. Affected components IDE (US Cell 1 GCP) (Operational) Scheduled Jobs (US Cell 1 GCP) (Operational)

  3. resolved Mar 05, 2026, 06:55 PM UTC

    Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 2026-03-05 8:06 PM EST. Between 10:18 AM EST and 8:06 PM EST an issue with an internal service resulted in failures in starting dbt Studio and scheduled jobs . We have put measures in place to prevent a recurrence and the dbt Studio and scheduled jobs have returned to normal. 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 (US Cell 1 GCP) (Operational) Scheduled Jobs (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 5, 2026

[APAC AWS] Linting Error from Request Dependency Warning

Detected by Pingoru
Mar 05, 2026, 03:49 AM UTC
Resolved
Mar 05, 2026, 03:49 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 04, 2026, 11:04 PM UTC

    Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (APAC AWS) (Degraded performance)

  2. monitoring Mar 05, 2026, 12:49 AM UTC

    Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (APAC AWS) (Operational) IDE (APAC AWS) (Operational)

  3. resolved Mar 05, 2026, 03:49 AM 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 IDE (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational)

Read the full incident report →

Minor March 5, 2026

[EMEA AWS] Linting Error from Request Dependency Warning

Detected by Pingoru
Mar 05, 2026, 03:49 AM UTC
Resolved
Mar 05, 2026, 03:49 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 04, 2026, 11:04 PM UTC

    Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA AWS) (Degraded performance)

  2. monitoring Mar 05, 2026, 12:49 AM UTC

    Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)

  3. resolved Mar 05, 2026, 03:49 AM 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 IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)

Read the full incident report →

Minor March 5, 2026

[EMEA Cell 1 AZURE] Linting Error from Request Dependency Warning

Detected by Pingoru
Mar 05, 2026, 03:49 AM UTC
Resolved
Mar 05, 2026, 03:49 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 04, 2026, 11:04 PM UTC

    Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EMEA Cell 1 AZURE) (Degraded performance)

  2. monitoring Mar 05, 2026, 12:49 AM UTC

    Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational)

  3. resolved Mar 05, 2026, 03:49 AM 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 IDE (EMEA Cell 1 AZURE) (Operational) dbt platform CLI (EMEA Cell 1 AZURE) (Operational)

Read the full incident report →

Minor March 5, 2026

[EU Cell 1 GCP] Linting Error from Request Dependency Warning

Detected by Pingoru
Mar 05, 2026, 03:49 AM UTC
Resolved
Mar 05, 2026, 03:49 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 04, 2026, 11:04 PM UTC

    Status: Identified We have identified an issue with Linting that resulted in a Request Dependency Warning. A fix is being implemented, and we will provide an update shortly. Affected components IDE (EU Cell 1 GCP) (Degraded performance)

  2. monitoring Mar 05, 2026, 12:49 AM UTC

    Status: Monitoring We have deployed a fix for the reported linting error and are currently monitoring the performance. Please contact us at [email protected] with any questions or concerns. Affected components dbt platform CLI (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)

  3. resolved Mar 05, 2026, 03:49 AM 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 dbt platform CLI (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational)

Read the full incident report →

Looking to track dbt Cloud downtime and outages?

Pingoru polls dbt Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when dbt Cloud reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track dbt Cloud alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring dbt Cloud for free

5 free monitors · No credit card required