Darling Consulting Group

Cloudflare continues to mitigate intermittent connectivity degradation for a small subset of customers caused by significant degradation of capacity in the region.

We are currently experiencing performance degradation affecting Microsoft 365 Archive Mailbox backups following our transition to a new Microsoft 365 API and a related one-time backend data reconciliation process.  Although the degradation is specific to Archive Mailbox processing, it has increased workload across the affected environment and may impact backup performance for other Microsoft 365 and Google Workspace services. As a result, some client organizations may see backup status reported as "In Progress" for longer than expected.  Our engineering teams are actively mitigating the impact by adding additional processing resources within the datacenter to accelerate Archive Mailbox processing and restore normal backup performance. What is impacted: - Backup processing and status reporting for Microsoft 365 and Google Workspace workloads - Some backups may remain in an "In Progress" state for upcoming 48 hours What is not impacted: - x360Cloud web application accessibility - Data restore functionality, including restores of Archive Mailbox data - Previously protected backup data We are actively monitoring the situation and working toward full recovery. The current estimated resolution timeframe is within 48 hours.

We've identified additional impacted instances and updated this messaging to reflect them. These customers will now receive communications about this incident going forward. These customers are also seeing zero values when accessing their site view traffic dashboard. We've completed the remediation step. The processing of the data backlog is now underway and will take several hours to complete. We'll provide an update in 5 hours, or sooner if additional information becomes available.

Current status: We're continuing our efforts to reduce virtual warehouse provisioning times, building on measures that have already shown improvement. In parallel, we're preserving available compute resources and coordinating with our third-party cloud provider to improve resource availability in the specified region. Resource availability continues to vary with demand, and provisioning delays or failures may still occur. We'll provide another update within 7 days. Customer experience: Over the past few weeks, we've seen periods of fewer failures as we continue working to preserve available compute resources. However, resource availability at our third-party cloud provider remains constrained. Customers in the specified region may still encounter failures, timeouts, or delays when running Snowpark Container Services workloads, including starting or resuming Notebooks and provisioning or resuming compute pools. Creating additional workloads in new accounts adds to demand for these limited resources. Customers setting up Snowpark Container Services services or jobs, or Openflow runtimes, in those accounts may therefore encounter more frequent provisioning failures or be unable to complete setup. Customers using second generation (Gen2) warehouses may also continue to experience delays or intermittent failures when starting or resuming their warehouses, which can extend query run times or delay completion of data pipelines. ETA: Our third-party cloud platform provider remains committed to making additional compute resources available in the specified region by end-October. We'll provide an updated ETA if that timeline changes. Workaround: Customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. Customers experiencing virtual warehouse resume delays can migrate affected warehouses to first generation (Gen1) using ALTER WAREHOUSE SET GENERATION = '1';. Gen1 warehouses are not affected by this capacity constraint. This is a short-term mitigation; Gen1 capacity is limited and performance characteristics may differ. There are currently no general workarounds available for Snowpark Container Services compute pool impact. Customers with specific compute pool failures should contact Snowflake Support for case-by-case assistance. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform experienced constrained compute capacity, causing limited availability of compute resources for Snowpark Container Services and delays or failures when provisioning or resuming virtual warehouses in the specified region.