dbt Cloud Outage History

dbt Cloud had 438 outages in the last 2 years — averaging 18 incidents per month.

There were 438 dbt Cloud outages since January 27, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getdbt.com

Minor May 28, 2026

[JP Cell 1 AWS] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 Scheduled Jobs (JP Cell 1 AWS) (Degraded performance) IDE (JP Cell 1 AWS) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (JP Cell 1 AWS) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 28, 2026

[US AWS] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 IDE (US AWS) (Degraded performance) Scheduled Jobs (US AWS) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US AWS) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor May 28, 2026

[US Cell 1 AWS] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 IDE (US Cell 1 AWS) (Degraded performance) Scheduled Jobs (US Cell 1 AWS) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 AWS) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 28, 2026

[US Cell 1 AZURE] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 Scheduled Jobs (US Cell 1 AZURE) (Degraded performance) IDE (US Cell 1 AZURE) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 AZURE) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 28, 2026

[US Cell 1 GCP] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 IDE (US Cell 1 GCP) (Degraded performance) Scheduled Jobs (US Cell 1 GCP) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 GCP) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US Cell 1 GCP) (Operational)

Read the full incident report →

Minor May 28, 2026

[US Cell 2 AWS] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 Scheduled Jobs (US Cell 2 AWS) (Degraded performance) IDE (US Cell 2 AWS) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 28, 2026

[US Cell 3 AWS] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 IDE (US Cell 3 AWS) (Degraded performance) Scheduled Jobs (US Cell 3 AWS) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 3 AWS) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor May 28, 2026

[US Cell 4 AWS] dbt1410 warnings

Detected by Pingoru: May 28, 2026, 09:22 PM UTC
Resolved: May 28, 2026, 09:22 PM UTC
Duration: —

Timeline · 4 updates

investigating May 28, 2026, 05:36 PM UTC

Status: Investigating We're investigating an issue with incorrect logging that is causing Warn dbt1410: dbt State service was requested but no validated client is available for node to surface during command execution. This is impacting Scheduled Jobs anytime after 12 PM Eastern. This is not resulting in errors and runs should still be completing successfully. 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 Scheduled Jobs (US Cell 4 AWS) (Degraded performance) IDE (US Cell 4 AWS) (Degraded performance)
identified May 28, 2026, 06:01 PM UTC

Status: Identified We have identified an issue with Scheduled Jobs that resulted in Warn dbt1410 logs occurring in runs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)
monitoring May 28, 2026, 06:09 PM UTC

Status: Monitoring We have deployed a fix for Scheduled Jobs that was causing the incorrect logging. Scheduled Jobs are starting to return to normal state and we are continuing to monitor. Affected components Scheduled Jobs (US Cell 4 AWS) (Degraded performance)
resolved May 28, 2026, 09:22 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally as of 5 PM Eastern. Between 12 PM Eastern and 5 PM Eastern an issue with Scheduled Jobs resulted in an incorrect warning being displayed in runs, along with some increased timing in run execution. We have put measures in place to prevent a recurrence 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 Scheduled Jobs (US Cell 4 AWS) (Operational)

Read the full incident report →

Minor May 27, 2026

[EMEA AWS] Intermittent errors with dbt Copilot and AI-powered features

Detected by Pingoru: May 27, 2026, 01:15 PM UTC
Resolved: May 27, 2026, 01:15 PM UTC
Duration: —

Timeline · 4 updates

investigating May 27, 2026, 12:47 PM UTC

Status: Investigating We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected. Affected components dbt Copilot (EMEA AWS) (Degraded performance)
identified May 27, 2026, 12:52 PM UTC

Status: Identified We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix. Affected components dbt Copilot (EMEA AWS) (Degraded performance)
monitoring May 27, 2026, 12:56 PM UTC

Status: Monitoring A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved. Affected components dbt Copilot (EMEA AWS) (Degraded performance)
resolved May 27, 2026, 01:15 PM UTC

Status: Resolved dbt Copilot and AI-powered features are operating normally. This incident is now resolved. We have put measures in place to prevent a recurrence and the dbt Copilot has 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 dbt Copilot (EMEA AWS) (Operational)

Read the full incident report →

Minor May 27, 2026

[US AWS] Intermittent errors with dbt Copilot and AI-powered features

Detected by Pingoru: May 27, 2026, 01:15 PM UTC
Resolved: May 27, 2026, 01:15 PM UTC
Duration: —

Timeline · 4 updates

investigating May 27, 2026, 12:47 PM UTC

Status: Investigating We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected. Affected components dbt Copilot (US AWS) (Degraded performance)
identified May 27, 2026, 12:52 PM UTC

Status: Identified We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix. Affected components dbt Copilot (US AWS) (Degraded performance)
monitoring May 27, 2026, 12:56 PM UTC

Status: Monitoring A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved. Affected components dbt Copilot (US AWS) (Degraded performance)
resolved May 27, 2026, 01:15 PM UTC

Status: Resolved dbt Copilot and AI-powered features are operating normally. This incident is now resolved. We have put measures in place to prevent a recurrence and the dbt Copilot has 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 dbt Copilot (US AWS) (Operational)

Read the full incident report →

Minor May 27, 2026

[US Cell 1 AWS] Intermittent errors with dbt Copilot and AI-powered features

Detected by Pingoru: May 27, 2026, 01:15 PM UTC
Resolved: May 27, 2026, 01:15 PM UTC
Duration: —

Timeline · 4 updates

investigating May 27, 2026, 12:47 PM UTC

Status: Investigating We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected. Affected components dbt Copilot (US Cell 1 AWS) (Degraded performance)
identified May 27, 2026, 12:52 PM UTC

Status: Identified We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix. Affected components dbt Copilot (US Cell 1 AWS) (Degraded performance)
monitoring May 27, 2026, 12:56 PM UTC

Status: Monitoring A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved. Affected components dbt Copilot (US Cell 1 AWS) (Degraded performance)
resolved May 27, 2026, 01:15 PM UTC

Status: Resolved dbt Copilot and AI-powered features are operating normally. This incident is now resolved. We have put measures in place to prevent a recurrence and the dbt Copilot has 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 dbt Copilot (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 27, 2026

[US Cell 1 AZURE] Intermittent errors with dbt Copilot and AI-powered features

Detected by Pingoru: May 27, 2026, 01:15 PM UTC
Resolved: May 27, 2026, 01:15 PM UTC
Duration: —

Timeline · 4 updates

investigating May 27, 2026, 12:47 PM UTC

Status: Investigating We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected. Affected components dbt Copilot (US Cell 1 AZURE) (Degraded performance)
identified May 27, 2026, 12:52 PM UTC

Status: Identified We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix. Affected components dbt Copilot (US Cell 1 AZURE) (Degraded performance)
monitoring May 27, 2026, 12:56 PM UTC

Status: Monitoring A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved. Affected components dbt Copilot (US Cell 1 AZURE) (Degraded performance)
resolved May 27, 2026, 01:15 PM UTC

Status: Resolved dbt Copilot and AI-powered features are operating normally. This incident is now resolved. We have put measures in place to prevent a recurrence and the dbt Copilot has 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 dbt Copilot (US Cell 1 AZURE) (Operational)

Read the full incident report →

Minor May 27, 2026

[US Cell 2 AWS] Intermittent errors with dbt Copilot and AI-powered features

Detected by Pingoru: May 27, 2026, 01:15 PM UTC
Resolved: May 27, 2026, 01:15 PM UTC
Duration: —

Timeline · 4 updates

investigating May 27, 2026, 12:47 PM UTC

Status: Investigating We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected. Affected components dbt Copilot (US Cell 2 AWS) (Degraded performance)
identified May 27, 2026, 12:52 PM UTC

Status: Identified We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix. Affected components dbt Copilot (US Cell 2 AWS) (Degraded performance)
monitoring May 27, 2026, 12:56 PM UTC

Status: Monitoring A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved. Affected components dbt Copilot (US Cell 2 AWS) (Degraded performance)
resolved May 27, 2026, 01:15 PM UTC

Status: Resolved dbt Copilot and AI-powered features are operating normally. This incident is now resolved. We have put measures in place to prevent a recurrence and the dbt Copilot has 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 dbt Copilot (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[APAC AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 IDE (APAC AWS) (Full outage) dbt platform CLI (APAC AWS) (Full outage) Scheduled Jobs (APAC AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (APAC AWS) (Full outage) IDE (APAC AWS) (Full outage) dbt platform CLI (APAC AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (APAC AWS) (Full outage) IDE (APAC AWS) (Full outage) Scheduled Jobs (APAC AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components IDE (APAC AWS) (Full outage) Scheduled Jobs (APAC AWS) (Full outage) dbt platform CLI (APAC AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components IDE (APAC AWS) (Operational) Scheduled Jobs (APAC AWS) (Operational) dbt platform CLI (APAC AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[EMEA AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 (EMEA AWS) (Full outage) Scheduled Jobs (EMEA AWS) (Full outage) IDE (EMEA AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 (EMEA AWS) (Full outage) IDE (EMEA AWS) (Full outage) Scheduled Jobs (EMEA AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (EMEA AWS) (Full outage) IDE (EMEA AWS) (Full outage) Scheduled Jobs (EMEA AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components IDE (EMEA AWS) (Full outage) Scheduled Jobs (EMEA AWS) (Full outage) dbt platform CLI (EMEA AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components IDE (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational) dbt platform CLI (EMEA AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[JP Cell 1 AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (JP Cell 1 AWS) (Full outage) IDE (JP Cell 1 AWS) (Full outage) dbt platform CLI (JP Cell 1 AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (JP Cell 1 AWS) (Full outage) IDE (JP Cell 1 AWS) (Full outage) dbt platform CLI (JP Cell 1 AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components IDE (JP Cell 1 AWS) (Full outage) dbt platform CLI (JP Cell 1 AWS) (Full outage) Scheduled Jobs (JP Cell 1 AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components IDE (JP Cell 1 AWS) (Full outage) Scheduled Jobs (JP Cell 1 AWS) (Full outage) dbt platform CLI (JP Cell 1 AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components dbt platform CLI (JP Cell 1 AWS) (Operational) IDE (JP Cell 1 AWS) (Operational) Scheduled Jobs (JP Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[US AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US AWS) (Full outage) dbt platform CLI (US AWS) (Full outage) IDE (US AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US AWS) (Full outage) IDE (US AWS) (Full outage) dbt platform CLI (US AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US AWS) (Full outage) IDE (US AWS) (Full outage) Scheduled Jobs (US AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components Scheduled Jobs (US AWS) (Full outage) dbt platform CLI (US AWS) (Full outage) IDE (US AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components Scheduled Jobs (US AWS) (Operational) dbt platform CLI (US AWS) (Operational) IDE (US AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[US Cell 1 AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US Cell 1 AWS) (Full outage) IDE (US Cell 1 AWS) (Full outage) dbt platform CLI (US Cell 1 AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US Cell 1 AWS) (Full outage) dbt platform CLI (US Cell 1 AWS) (Full outage) IDE (US Cell 1 AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 1 AWS) (Full outage) Scheduled Jobs (US Cell 1 AWS) (Full outage) dbt platform CLI (US Cell 1 AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components Scheduled Jobs (US Cell 1 AWS) (Full outage) dbt platform CLI (US Cell 1 AWS) (Full outage) IDE (US Cell 1 AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components IDE (US Cell 1 AWS) (Operational) Scheduled Jobs (US Cell 1 AWS) (Operational) dbt platform CLI (US Cell 1 AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[US Cell 2 AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 IDE (US Cell 2 AWS) (Full outage) Scheduled Jobs (US Cell 2 AWS) (Full outage) dbt platform CLI (US Cell 2 AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 IDE (US Cell 2 AWS) (Full outage) Scheduled Jobs (US Cell 2 AWS) (Full outage) dbt platform CLI (US Cell 2 AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Full outage) IDE (US Cell 2 AWS) (Full outage) dbt platform CLI (US Cell 2 AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components IDE (US Cell 2 AWS) (Full outage) dbt platform CLI (US Cell 2 AWS) (Full outage) Scheduled Jobs (US Cell 2 AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components IDE (US Cell 2 AWS) (Operational) Scheduled Jobs (US Cell 2 AWS) (Operational) dbt platform CLI (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[US Cell 3 AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US Cell 3 AWS) (Full outage) IDE (US Cell 3 AWS) (Full outage) dbt platform CLI (US Cell 3 AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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) (Full outage) Scheduled Jobs (US Cell 3 AWS) (Full outage) IDE (US Cell 3 AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components dbt platform CLI (US Cell 3 AWS) (Full outage) IDE (US Cell 3 AWS) (Full outage) Scheduled Jobs (US Cell 3 AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components Scheduled Jobs (US Cell 3 AWS) (Full outage) dbt platform CLI (US Cell 3 AWS) (Full outage) IDE (US Cell 3 AWS) (Full outage)
resolved May 26, 2026, 06:00 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components IDE (US Cell 3 AWS) (Operational) dbt platform CLI (US Cell 3 AWS) (Operational) Scheduled Jobs (US Cell 3 AWS) (Operational)

Read the full incident report →

Minor May 26, 2026

[US Cell 4 AWS] dbt Platform experiencing connectivity issues

Detected by Pingoru: May 26, 2026, 06:00 PM UTC
Resolved: May 26, 2026, 06:00 PM UTC
Duration: —

Timeline · 5 updates

investigating May 26, 2026, 02:00 PM UTC

Status: Investigating We're investigating connectivity issues that's affecting the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US Cell 4 AWS) (Full outage) IDE (US Cell 4 AWS) (Full outage) dbt platform CLI (US Cell 4 AWS) (Full outage)
investigating May 26, 2026, 04:44 PM UTC

Status: Investigating We are continuing to investigate connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. 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 Scheduled Jobs (US Cell 4 AWS) (Full outage) IDE (US Cell 4 AWS) (Full outage) dbt platform CLI (US Cell 4 AWS) (Full outage)
identified May 26, 2026, 05:03 PM UTC

Status: Identified We have identified the connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. A fix is being implemented, and we will provide an update shortly. Affected components IDE (US Cell 4 AWS) (Full outage) dbt platform CLI (US Cell 4 AWS) (Full outage) Scheduled Jobs (US Cell 4 AWS) (Full outage)
monitoring May 26, 2026, 05:32 PM UTC

Status: Monitoring We have deployed a fix that was causing connectivity issues affecting all warehouse connections across the Studio IDE, CLI and Jobs. We are continuing to monitor. Affected components Scheduled Jobs (US Cell 4 AWS) (Full outage) IDE (US Cell 4 AWS) (Full outage) dbt platform CLI (US Cell 4 AWS) (Full outage)
resolved May 26, 2026, 06:26 PM UTC

Status: Resolved Between 10:00 AM Eastern and 2:00 PM Eastern, a release related to how we route traffic resulted in connectivity failures to all warehouse connections over PrivateLink within AWS-hosted dbt platform environments. Affected components Scheduled Jobs (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 May 25, 2026

[US AWS] Snowflake jobs may time out on Latest release track

Detected by Pingoru: May 25, 2026, 09:03 PM UTC
Resolved: May 25, 2026, 09:03 PM UTC
Duration: —

Timeline · 4 updates

investigating May 22, 2026, 04:59 PM UTC

Status: Investigating We're investigating an issue with the Snowflake adapter on the Latest release track that is causing some dbt jobs to fail when fetching large query result sets. The Snowflake connector is hitting a 7-second connection timeout while retrieving result data from Snowflake's internal storage, surfacing in run logs as: "Failed to fetch the large result set batch data_1 ... ConnectTimeoutError ... timed out (connect timeout=7)" This is impacting jobs running on the Latest release track in deployments using Snowflake. The team is investigating the underlying cause and will provide updates at approximately 15-minute intervals as new information becomes available. Workaround Switching affected jobs to the Compatible or Extended release track resolves the failures immediately. For production workloads, we recommend Extended going forward as the most stable option. Affected components Scheduled Jobs (US AWS) (Degraded performance)
identified May 22, 2026, 06:09 PM UTC

Status: Identified We have identified an issue with a recent Snowflake adapter release that resulted in some dbt jobs failing when fetching large query result sets. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US AWS) (Degraded performance)
monitoring May 25, 2026, 06:43 PM UTC

Status: Monitoring We have deployed a fix for the Snowflake adapter that resulted in some dbt jobs failing when fetching large query result sets. We are continuing to monitor. Affected components Scheduled Jobs (US AWS) (Degraded performance)
resolved May 25, 2026, 09:03 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence and the Snowflake adapter has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US AWS) (Operational)

Read the full incident report →

Minor May 25, 2026

[US Cell 2 AWS] Snowflake jobs may time out on Latest release track

Detected by Pingoru: May 25, 2026, 09:03 PM UTC
Resolved: May 25, 2026, 09:03 PM UTC
Duration: —

Timeline · 4 updates

investigating May 22, 2026, 04:59 PM UTC

Status: Investigating We're investigating an issue with the Snowflake adapter on the Latest release track that is causing some dbt jobs to fail when fetching large query result sets. The Snowflake connector is hitting a 7-second connection timeout while retrieving result data from Snowflake's internal storage, surfacing in run logs as: "Failed to fetch the large result set batch data_1 ... ConnectTimeoutError ... timed out (connect timeout=7)" This is impacting jobs running on the Latest release track in deployments using Snowflake. The team is investigating the underlying cause and will provide updates at approximately 15-minute intervals as new information becomes available. Workaround Switching affected jobs to the Compatible or Extended release track resolves the failures immediately. For production workloads, we recommend Extended going forward as the most stable option. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
identified May 22, 2026, 06:09 PM UTC

Status: Identified We have identified an issue with a recent Snowflake adapter release that resulted in some dbt jobs failing when fetching large query result sets. A fix is being implemented, and we will provide an update shortly. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
monitoring May 25, 2026, 06:43 PM UTC

Status: Monitoring We have deployed a fix for the Snowflake adapter that resulted in some dbt jobs failing when fetching large query result sets. We are continuing to monitor. Affected components Scheduled Jobs (US Cell 2 AWS) (Degraded performance)
resolved May 25, 2026, 09:03 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. We have put measures in place to prevent a recurrence and the Snowflake adapter has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Scheduled Jobs (US Cell 2 AWS) (Operational)

Read the full incident report →

Minor May 24, 2026

[EMEA AWS] Error retrieving publications: the Cloud Artifacts API is currently unavailable. Please try again later.

Detected by Pingoru: May 24, 2026, 09:29 PM UTC
Resolved: May 24, 2026, 09:29 PM UTC
Duration: —

Timeline · 2 updates

monitoring May 24, 2026, 09:26 PM UTC

Status: Monitoring Between May 24, 8:52 pm – May 24, 8:55 pm UTC, a small number of runs trying to retrieve publication artifacts experienced the following error: "Error retrieving publications: the Cloud Artifacts API is currently unavailable. Please try again later." The issue has since been resolved and we're continuing to monitor. Apologies for any inconveniences this has caused Affected components Scheduled Jobs (EMEA AWS) (Degraded performance) Admin API (EMEA AWS) (Degraded performance)
resolved May 24, 2026, 09:29 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 Admin API (EMEA AWS) (Operational) Scheduled Jobs (EMEA AWS) (Operational)

Read the full incident report →

Minor May 22, 2026

[APAC AWS] Billing Admin Page Requests Intermittently Failing

Detected by Pingoru: May 22, 2026, 09:03 PM UTC
Resolved: May 22, 2026, 09:03 PM UTC
Duration: —

Timeline · 5 updates

investigating May 22, 2026, 04:22 PM UTC

Status: Investigating We're investigating an issue with the Billing Admin Page that is causing some requests to fail or time out with 5XX errors. This is impacting the Billing Usage in all instances. The team is working on a resolution and we will provide updates as soon as new information becomes available. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (APAC AWS) (Degraded performance)
monitoring May 22, 2026, 04:44 PM UTC

Status: Monitoring The issue with the Billing Admin Page that was causing requests to fail or time out with 5XX errors appears to have been resolved. All monitors have returned to green and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (APAC AWS) (Operational)
identified May 22, 2026, 07:23 PM UTC

Status: Identified We have identified an issue with the Billing Admin Page that resulted in requests failing or timing out with 5XX errors. This is due to a bug with a third-party dependency, and the vendor is working on a fix. We will provide an update shortly. Affected components Web Application (APAC AWS) (Degraded performance)
monitoring May 22, 2026, 08:57 PM UTC

Status: Monitoring Our third-party vendor has deployed a fix for the issue that was causing the Billing Admin Page to fail or time out with 5XX errors. The Billing Admin Page has returned to its normal state and we are continuing to monitor. Other dbt platform services (IDE, scheduler, runs, API) are not impacted and should be running as expected. Affected components Web Application (APAC AWS) (Operational)
resolved May 22, 2026, 09:04 PM UTC

Status: Resolved The issue has been resolved, and all affected systems are now functioning normally. Our vendor has deployed a fix, and the Billing Admin Page has returned to normal. Please contact Support via email [email protected] "[email protected]": mailto:[email protected] if you continue to experience delays and are unsure of the root cause. Affected components Web Application (APAC AWS) (Operational)

Read the full incident report →