https://ultrastatus.cloudcauldron.io/ Every open incident on the clouds and services your work runs on. en Fri, 23 Oct 2026 20:34:06 GMT 2 https://health.aws.amazon.com/health/status aws:arn:aws:health:me-central-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_5E6B8_EF2498889B5 Sun, 01 Mar 2026 12:51:25 GMT We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal. AWS critical aws me-central-1 https://health.aws.amazon.com/health/status aws:arn:aws:health:me-south-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_E6426_01AD72B4E1E Mon, 02 Mar 2026 05:56:27 GMT We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. When the first Availability Zone was damaged in March, we began recommending that customers migrate their workloads to other Regions, and most did so before the Region became unavailable following the disruption of a second Availability Zone in April. Since then, we have supported the remaining customers in re-establishing their operations in alternate Regions, using backups where available or implementing alternative solutions to mitigate the impact of inaccessible data. In parallel, we assessed all affected infrastructure and exhausted every option for restoring data and resources that had not been migrated before the Region became unavailable. We remain committed to supporting our customers in Bahrain in the long term and will share a further update in early 2027. We have notified the relevant authorities and continue to work with them toward that goal. AWS critical aws me-south-1 https://www.cloudflarestatus.com/incidents/3ts1mfzs0khz cloudflare:3ts1mfzs0khz Fri, 23 Oct 2026 15:27:34 GMT A fix has been implemented and we are monitoring the results. Cloudflare minor https://stspg.io/2tmfhlrz2yz5 snowflake:9p16kxkml7v2 Fri, 28 Aug 2026 00:07:42 GMT Current status: Virtual warehouse capacity and provisioning have remained stable, and we do not expect further broad risk to customer workloads, but we will continue monitoring through periods of peak demand. Snowpark Container Services (SPCS) remains subject to capacity constraints. We continue to preserve available resources, coordinate with our third-party cloud provider, and work on additional capacity options. We have seen improvement, but workloads that require additional new capacity may still be affected. We continue to target late October before considering the SPCS impact mitigated, subject to sustained resource availability and service readiness. We will provide another update within seven days, or sooner if there is a significant change. Customer experience: Customers using virtual warehouses should no longer experience the broader provisioning impact associated with this incident. Customers with continuing or customer-specific reliability issues should contact Snowflake Support for assistance. Customers using Snowpark Container Services may still encounter delays, timeouts, or failures when starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. The remaining risk is concentrated in workloads that require additional new capacity; existing workloads generally continue to run normally. ETA: We have seen sustained stability in virtual warehouse capacity and provisioning since October 7, 2026. For Snowpark Container Services, we continue to target late October for mitigation as additional capacity and service readiness are validated. We will provide an updated ETA if that timeline changes. Workaround: For virtual warehouses, we are no longer recommending a broad migration to Gen1 as a workaround for this incident. Customers who previously moved affected warehouses to Gen1 may work with Snowflake Support or their account team to evaluate returning to Gen2. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support. Impact start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform is experiencing constrained compute capacity in the specified region, limiting the availability of compute resources for Snowpark Container Services and causing delays or failures when provisioning or resuming virtual warehouses. Snowflake minor gcp us-central1 https://status.getdbt.com/incidents/01M262ZQ2M7QC0S81N88BG36V9 dbt:01M262ZQ2M7QC0S81N88BG36V9 Thu, 10 Sep 2026 16:39:01 GMT We have identified an issue affecting dbt Copilot on single-tenant deployments hosted on Azure. Conversations are not retaining context, which means the assistant may be unable to continue a conversation or complete a request. A fix is being implemented and we will provide an update shortly. dbt Cloud minor