dbt Cloud Outage History

dbt Cloud is up right now

dbt Cloud had 438 outages in the last 2 years totaling 3h 0m of downtime — averaging 18 incidents per month.

There were 438 dbt Cloud outages since January 27, 2026 totaling 3h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor March 6, 2026

[EMEA 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 (EMEA AWS) (Degraded performance) dbt platform CLI (EMEA 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 (EMEA AWS) (Degraded performance) Web Application (EMEA 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 Web Application (EMEA AWS) (Operational) dbt platform CLI (EMEA 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 (EMEA AWS) (Partial outage) dbt platform CLI (EMEA 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 (EMEA AWS) (Partial outage) Web Application (EMEA AWS) (Operational) IDE (EMEA 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 (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) IDE (EMEA 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 IDE (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational) Web Application (EMEA AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[EU 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 Web Application (EU Cell 1 GCP) (Degraded performance) dbt platform CLI (EU 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 (EU Cell 1 GCP) (Degraded performance) Web Application (EU 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 Web Application (EU Cell 1 GCP) (Operational) dbt platform CLI (EU 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 (EU Cell 1 GCP) (Partial outage) Web Application (EU 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 dbt platform CLI (EU Cell 1 GCP) (Partial outage) IDE (EU Cell 1 GCP) (Partial outage) Web Application (EU 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 IDE (EU Cell 1 GCP) (Operational) dbt platform CLI (EU Cell 1 GCP) (Operational) Web Application (EU 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 (EU Cell 1 GCP) (Operational) IDE (EU Cell 1 GCP) (Operational) Web Application (EU Cell 1 GCP) (Operational)

Read the full incident report →

Minor March 6, 2026

[JP Cell 1 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 (JP Cell 1 AWS) (Degraded performance) dbt platform CLI (JP Cell 1 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 (JP Cell 1 AWS) (Degraded performance) dbt platform CLI (JP Cell 1 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 Web Application (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 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 (JP Cell 1 AWS) (Partial outage) Web Application (JP Cell 1 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 (JP Cell 1 AWS) (Partial outage) IDE (JP Cell 1 AWS) (Partial outage) Web Application (JP Cell 1 AWS) (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 (JP Cell 1 AWS) (Operational) IDE (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 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 IDE (JP Cell 1 AWS) (Operational) dbt platform CLI (JP Cell 1 AWS) (Operational) Web Application (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US 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 AWS) (Degraded performance) dbt platform CLI (US 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 AWS) (Degraded performance) dbt platform CLI (US 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 AWS) (Operational) Web Application (US 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 AWS) (Partial outage) Web Application (US 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 AWS) (Operational) dbt platform CLI (US AWS) (Partial outage) IDE (US 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 IDE (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Web Application (US 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 IDE (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) Web Application (US AWS) (Operational)

Read the full incident report →

Minor March 6, 2026

[US Cell 1 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 1 AWS) (Degraded performance) Web Application (US Cell 1 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 1 AWS) (Degraded performance) Web Application (US Cell 1 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 1 AWS) (Operational) Web Application (US Cell 1 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 1 AWS) (Partial outage) dbt platform CLI (US Cell 1 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 1 AWS) (Operational) IDE (US Cell 1 AWS) (Partial outage) dbt platform CLI (US Cell 1 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 1 AWS) (Operational) IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 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 IDE (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational) Web Application (US Cell 1 AWS) (Operational)

Read the full incident report →

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 →