dbt Cloud Status

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Resolved: Microsoft Azure services have been restored by Microsoft. Please refer to the Microsoft Azure status page for more information: https://azure.status.microsoft/en-us/status/history/

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft is still working to migrate the impact of this incident. We will continue to monitor this incident and provide more updates as they become available.

Identified: Microsoft Azure is currently experiencing partial impact to some of the Azure Services in East US2 due to a configuration change in a regional networking service. This has resulted in degraded services across dbt Cloud services, including for the Web Application, IDE, and Scheduled Jobs.

The Microsoft status page for more information: https://azure.status.microsoft/en-us/status

We will continue to monitor this incident and provide more updates as they become available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/

Identified: We have implemented a fix for freshness checks in schema yaml files that was causing jobs to fail. The fix is currently in progress and undergoing the necessary steps for deployment to all affected environments.

We will provide further updates as soon as the fix has been fully deployed and verified.

Thank you for your continued patience as we work to complete this process.

Identified: We are continuing to work on a fix for this issue.

Identified: The cause of issue has been identified and the team is working on a solution.

Investigating: We're investigating an issue with freshness checks in schema yaml files causing jobs to fail.

Due to some recent changes, incorrect model freshness configurations which were previously ignored, are now getting validated and throwing errors, resulting in failed runs. This is impacting Jobs in all tenancies. The team is working on a resolution/rollback and we will provide updates at approximately 30 minutes intervals or as soon as new information becomes available.

Resolved: Github has identified the cause, deployed a fix and marked their incident as resolved. All affected systems should now be functioning normally as of 14 January 2025, 00:28 UTC. Kindly refresh the IDE and rerun job runs.

Please contact support at support@dbtlabs.com should the issue continue to persist. Thank you for your patience and understanding.

Investigating: Github is currently experiencing an incident that is causing git errors to be returned in the dbt Cloud IDE and job runs to get hung up on the clone step. The Github status page can be found here: https://www.githubstatus.com/