Accel Dashboard

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.

We are investigating elevated error rates affecting Durable Objects in Western Europe. Customers may see errors when using Durable Objects and related services. We will post updates as we learn more.

We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.

We are aware of a security issue involving eMudhra, a third-party certificate authority used to verify secure internet connections. Our security and engineering teams are assessing potential exposure and proactively updating affected software and certificate bundles across our services and applications. At this time, we have not identified evidence that Notion has been compromised in connection with this issue. This work is a preventative security measure, rather than a response to a service outage. We’re taking precautionary steps to update affected certificate-validation components and block trust in the affected certificates where needed.

Salesforce is aware of a publicly reported compromise of intermediate certificates issued by a third-party certificate authority. Salesforce is continuing to monitor the situation and may undertake proactive maintenance. We will provide updates here as appropriate.

Current status: Since our last update, we have seen improvement in Snowpark Container Services availability. Additional capacity became available in the specified region and has been reserved for customer workloads. Virtual warehouse capacity and provisioning performance also remain improved. We continue to monitor both services through periods of peak demand and are coordinating with our third-party cloud provider on additional capacity. While we have seen significant improvement across all affected services, workloads that require additional new capacity may still be affected, so we are continuing to monitor resource availability until the issue is fully resolved. We will provide another update within 7 days, or sooner if there is a material change. Customer experience: Customers using Snowpark Container Services should see improved ability to start or resume current supported workloads. However, delays, timeouts, or failures may still occur for workloads that require additional new capacity, including starting or resuming Notebooks, provisioning or resuming compute pools, or setting up OpenFlow runtimes. Existing workloads generally continue to run normally. Customers using virtual warehouses should continue to see improved availability when starting or resuming warehouses. Residual delays or intermittent failures may still occur while we validate the improvement under sustained demand. Customers with continued warehouse reliability issues should contact Snowflake Support for case-by-case assistance. ETA: We continue to expect additional compute resources to become available in the specified region by late October. The capacity currently available has improved service conditions, but the remaining risk will not be considered resolved until resource availability is sustained and customer impact remains mitigated. We will provide an updated ETA if the 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 based on current capacity, workload requirements, and observed reliability. Gen1 remains a possible short-term mitigation for customers who continue to experience verified Gen2 reliability issues, but performance and cost characteristics may differ. Customers running warehouse-based Notebooks may continue to defer migration to Snowpark Container Services where feasible. There is currently no general workaround for Snowpark Container Services compute pool impact; customers experiencing specific failures should contact Snowflake Support. Incident 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.

We are aware of an issue preventing some new Insights from being generated as expected. We have identified the root cause and are actively working on a hotfix to resolve the issue. We will deploy the fix as soon as possible and continue to provide updates on our progress.

We have identified the cause of an issue affecting one-time passcode verification calls for Hosted Numbers. Some customers are not receiving these calls, which prevents them from verifying their numbers and continuing with SMS hosting. Customers may need to enable the required geo permissions on their account and retry the verification call. We are working to resolve this and will provide another update in 4 hours or as soon as more information becomes available.

We're applying security updates to the Node.js runtime used by parts of Zapier, following a security release from the Node.js project. We have not identified any customer impact or evidence of exploitation, and no action is needed on your part. Some updates are rolling out now, so you may see brief latency to workflows while they complete.