Medical Microinstruments, Inc.

We have implemented a mitigation to redirect UAE traffic to an alternate data center (Mumbai) to address the ongoing service impact. Traffic is being steered to the Mumbai region, and we are actively monitoring system stability and performance. This mitigation primarily applies to automatically steered (roaming) UAE traffic. Customers in the affected region are advised to ensure their configurations align with previously shared guidance for alternate region routing, including any required updates to Network Tunnel Groups or Connector Groups. Customers already configured to alternate regions will continue using their configured region. Our engineering teams continue to investigate the underlying cause and are working closely with partners to ensure full service restoration. If you require any assistance, please contact us. We will provide guidance on the necessary actions.

Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat. More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages. Current status: The initial 10% of the deployment has saturated throughout the affected infrastructure and has proven successful. We’re now in the process of deploying another 40% of the fix while we continue monitoring service health. Additionally, we expect that some users may be incrementally remediated as the deployment continues to saturate throughout the affected environment. Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues. Start time: Wednesday, July 22, 2026, at 10:07 PM UTC Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact. Next update by: Sunday, September 20, 2026, at 3:00 AM UTC

Current status: Our third-party cloud platform provider has informed us that they expect to be able to provide additional capacity allocation by mid-October. In the meantime, we are working to preserve compute resources available to us, reduce non-essential resource consumption, and investigate any alternative methods to further reduce impact. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We'll provide another update by 23:00 UTC September 17, 2026. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resuming compute pools. Notebooks running on virtual warehouses are not affected. Additionally, starting from 04:00 UTC September 04, 2026, customers hosted in the specified region with workloads on second generation (Gen2) warehouses may experience delays or intermittent failures when resuming or starting virtual warehouses. This may result in longer than expected query run times or delays in completing data pipelines. Warehouses that are already running are largely unaffected. ETA: Based on information from our third-party cloud platform provider, we anticipate a solution in mid-October. Workaround: While we're focused on remediation, customers running Notebooks on virtual warehouses can delay migrating to Snowpark Container Services until this issue is resolved. For customers experiencing impact to virtual warehouses, and who have already performed a failover, we recommend remaining in the alternate region until we have received additional capacity allocation from the third-party provider. Customers who are continuing to experience impact to virtual warehouses may see additional relief by migrating workloads to first generation (Gen1) warehouses, which remain less impacted by this issue. Incident start time: 08:41 UTC August 09, 2026 Preliminary root cause: A third-party cloud platform provider is experiencing constrained compute capacity, affecting compute resource provisioning, and causing limited availability of compute resources as well as delays and intermittent failures when resuming or starting virtual warehouses in the specified region.

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

Frankfurt, Germany (Webex Calling) is currently experiencing a networking outage impacting service connectivity. The Cisco Webex Infrastructure team is actively investigating the issue and performing troubleshooting efforts to identify the root cause and restore normal operations as quickly as possible. Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitter Affected Cloud Agents: Frankfurt, Germany (Webex Calling) Start time: Jun 23, 2026, 10:36 PM UTC