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.
Fabric customers may experience failures when adding Ontology V2 artifacts as a data source to their Data Agent. Affected users may see errors when attempting to configure or query Ontology V2-backed data through Data Agent. Engineers have identified the root cause and are actively working on deploying a fix. We expect to provide a resolution by October 9, 2026, end of day. Workaround:Customers with Ontology V2 artifacts that were upgraded from an existing V1 ontology can revert to using the original V1 artifact as their Data Agent data source.No workaround is currently available for Ontology V2 artifacts that were created directly without a prior V1 version.
Twilio customers may be experiencing MMS delivery delays from a subset of Twilio Long Codes to GCI network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 24 hours or as soon as more information becomes available.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
Core Cloud Services - Admin UI: Zscaler has detected an issue with its zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net Cloud. Affected customer may have missing ZCC flow logs for direct (Zscaler-bypassed) traffic in Web Insight. Customer data and network traffic is unaffected. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.Latest Update - Wed, 07 Oct 2026 21:34:24 UTCZscaler team is actively working on a mitigation and validating the fix to restore normal log visibility. Once validated, the fix will be applied across the affected environments.Update - Wed, 07 Oct 2026 11:15:48 UTCWe have identified the root cause of the issue and working on resolution.Update - Wed, 07 Oct 2026 21:34:24 UTCZscaler team is actively working on a mitigation and validating the fix to restore normal log visibility. Once validated, the fix will be applied across the affected environments.
Monitors
Amazon Web Services
Fabric customers using Data Pipelines in UK South may have experienced elevated queue times, resulting in delays or timeouts in pipeline execution. Engineers are investigating the issue and an update will be provided soon
Microsoft Fabric
Core Cloud Services - Admin UI: ZCC Flow Logging Issue (+4 more)
Zscaler Cloud