dbt Cloud Outage History

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 28, 2026, 05:36 PM UTC· resolved May 28, 2026, 09:22 PM UTC

1. investigating May 28, 2026, 05:36 PM UTC

   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.

2. identified May 28, 2026, 06:01 PM UTC

   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.

3. monitoring May 28, 2026, 06:09 PM UTC

   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.

4. resolved May 28, 2026, 09:22 PM UTC

   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.

Read the full incident report →

Started May 27, 2026, 12:47 PM UTC· resolved May 27, 2026, 01:15 PM UTC

1. investigating May 27, 2026, 12:47 PM UTC

   We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected.

2. identified May 27, 2026, 12:52 PM UTC

   We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix.

3. monitoring May 27, 2026, 12:56 PM UTC

   A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved.

4. resolved May 27, 2026, 01:15 PM UTC

   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.

Read the full incident report →

Started May 27, 2026, 12:47 PM UTC· resolved May 27, 2026, 01:15 PM UTC

1. investigating May 27, 2026, 12:47 PM UTC

   We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected.

2. identified May 27, 2026, 12:52 PM UTC

   We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix.

3. monitoring May 27, 2026, 12:56 PM UTC

   A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved.

4. resolved May 27, 2026, 01:15 PM UTC

   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.

Read the full incident report →

Started May 27, 2026, 12:47 PM UTC· resolved May 27, 2026, 01:15 PM UTC

1. investigating May 27, 2026, 12:47 PM UTC

   We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected.

2. identified May 27, 2026, 12:52 PM UTC

   We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix.

3. monitoring May 27, 2026, 12:56 PM UTC

   A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved.

4. resolved May 27, 2026, 01:15 PM UTC

   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.

Read the full incident report →

Started May 27, 2026, 12:47 PM UTC· resolved May 27, 2026, 01:15 PM UTC

1. investigating May 27, 2026, 12:47 PM UTC

   We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected.

2. identified May 27, 2026, 12:52 PM UTC

   We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix.

3. monitoring May 27, 2026, 12:56 PM UTC

   A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved.

4. resolved May 27, 2026, 01:15 PM UTC

   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.

Read the full incident report →

Started May 27, 2026, 12:47 PM UTC· resolved May 27, 2026, 01:15 PM UTC

1. investigating May 27, 2026, 12:47 PM UTC

   We're investigating reports of errors when using dbt Copilot and other AI-powered features in dbt platform. Other dbt platform functionality is unaffected.

2. identified May 27, 2026, 12:52 PM UTC

   We've identified the cause of the errors affecting dbt Copilot and AI-powered features and are applying a fix.

3. monitoring May 27, 2026, 12:56 PM UTC

   A fix has been applied. We're monitoring AI features across all regions to confirm the issue is fully resolved.

4. resolved May 27, 2026, 01:15 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:00 PM UTC

   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.

Read the full incident report →

Started May 26, 2026, 02:00 PM UTC· resolved May 26, 2026, 06:00 PM UTC

1. investigating May 26, 2026, 02:00 PM UTC

   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.

2. investigating May 26, 2026, 04:44 PM UTC

   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.

3. identified May 26, 2026, 05:03 PM UTC

   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.

4. monitoring May 26, 2026, 05:32 PM UTC

   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.

5. resolved May 26, 2026, 06:26 PM UTC

   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.

Read the full incident report →

Started May 24, 2026, 09:26 PM UTC· resolved May 24, 2026, 09:29 PM UTC

1. monitoring May 24, 2026, 09:26 PM UTC

   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

2. resolved May 24, 2026, 09:29 PM UTC

   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.

Read the full incident report →