Multiple undersea fiber optic cables in the Red Sea were severed earlier this week, causing significant latency issues for Microsoft’s Azure cloud platform, particularly affecting users in the Middle East and parts of Asia and Europe. The incident, reported starting September 6, 2025, disrupted normal data traffic routes that traverse this critical maritime communication corridor.
Microsoft confirmed that the cable cuts led to increased lat...
Microsoft confirmed that the cable cuts led to increased latency and service disruptions for Azure clients relying on network traffic passing through the Middle East. The company’s engineering teams rapidly responded by rerouting traffic through alternate network paths to maintain service continuity. Despite these efforts, users experienced slower response times due to the longer and less optimal routes the data had to travel[1][2][3].
In an official status update, Microsoft stated, “We do expec...
In an official status update, Microsoft stated, “We do expect higher latency on some traffic that previously traversed through the Middle East. Network traffic that does not traverse through the Middle East is not impacted.” The message reassured customers that no complete network outages occurred, as the rerouting prevented interruptions to Azure services. The company committed to ongoing monitoring, rebalancing, and optimizing routing to minimize customer impact while repairs are underway. However, the undersea fiber cuts are expected to take time to fix due to the logistical challenges involved in submarine cable repair operations[1][2][3].
By the evening of September 6, Microsoft reported that it wa...
By the evening of September 6, Microsoft reported that it was no longer detecting any active Azure issues, indicating that mitigation measures had successfully stabilized the platform’s performance[2]. The company has continued to provide daily updates to keep clients informed of any changes.
The Red Sea is a vital conduit for multiple international un...
The Red Sea is a vital conduit for multiple international undersea cables connecting Europe, Asia, and the Middle East. The disruption highlights the vulnerability of global internet infrastructure to physical damage in key maritime regions, which can have wide-ranging impacts on cloud service providers and their customers worldwide[4].
Microsoft has not disclosed the cause of the cable cuts or i...
Microsoft has not disclosed the cause of the cable cuts or identified responsible parties. The situation remains under close observation as repair efforts proceed to restore the cables and fully normalize network latency and bandwidth in the affected regions[1][2].
🔄 Updated: 9/7/2025, 3:40:50 PM
Multiple undersea fiber optic cables in the Red Sea were severed on September 6, 2025, causing increased latency and disruptions for Microsoft Azure users, particularly in the Middle East and Asia. Microsoft responded by rerouting traffic through alternate paths and reported that all Azure services were restored with no current outages as of September 7, but warned that some latency might persist for traffic previously routed through the affected cables[1][2][4][5]. A Microsoft statement noted, "Undersea fiber cuts can take time to repair; as such, we will continuously monitor, rebalance, and optimize routing to reduce customer impact in the meantime"[1][2].
🔄 Updated: 9/7/2025, 3:50:47 PM
Following the multiple undersea cable cuts in the Red Sea on September 6, 2025, which affected Microsoft Azure's service latency, no specific regulatory or government response has been publicly detailed by authorities so far. Microsoft stated it is continuously monitoring and optimizing routing to mitigate impact while repairs proceed, but official governmental actions or statements regarding the incident have not been reported in available sources. The incident highlights vulnerabilities in critical infrastructure without immediate regulatory intervention disclosed[1][2][3][4].
🔄 Updated: 9/7/2025, 4:01:07 PM
Following the multiple undersea cable cuts in the Red Sea on September 6, 2025, regional governments and regulators have yet to issue an official public response addressing the incident's cause or coordinated mitigation efforts. Microsoft reported increased latency on Azure services affecting traffic through the Middle East and noted efforts to reroute and optimize traffic while repairs are underway, but no governmental agencies have released statements detailing regulatory actions or infrastructure protections related to the event[1][2][3]. As of now, repair timelines remain unspecified, and the focus has been on service continuity by private operators rather than visible government intervention.
🔄 Updated: 9/7/2025, 4:10:47 PM
Azure experienced latency issues after multiple undersea fiber optic cables in the Red Sea were severed on September 6, 2025, disrupting traffic routes between Europe, Asia, and the Middle East. Microsoft acknowledged increased latency on traffic previously routed through the Middle East but emphasized that no traffic was interrupted due to rerouting via alternate paths, noting, "Undersea fiber cuts can take time to repair; as such, we will continuously monitor, rebalance, and optimize routing to reduce customer impact" [1][2][3][5]. Industry experts highlight the complexity and extended repair time of such subsea disruptions, signaling ongoing vulnerability for cloud services relying heavily on these critical infrastructures.
🔄 Updated: 9/7/2025, 4:20:49 PM
Following the multiple undersea cable cuts in the Red Sea on September 6, 2025, government and regulatory authorities have yet to issue official statements or identify the responsible parties. Microsoft noted the complexity of repairing undersea fiber cuts and emphasized ongoing monitoring and traffic rerouting to minimize service disruption, but no regulatory action or investigation details have been publicly disclosed as of now[1][4]. The situation continues to be closely monitored by both industry and regional authorities.
🔄 Updated: 9/7/2025, 4:30:58 PM
Following the multiple undersea cable cuts in the Red Sea on September 6, Microsoft Azure users in South Asia and the Gulf region reported significant latency spikes and degraded cloud performance, prompting widespread public frustration especially among businesses reliant on stable connectivity[1]. Consumers took to social media expressing concerns over disrupted multiplayer gaming and slow large file downloads, with some describing the latency as "unbearable" for critical online activities, while Microsoft communicated ongoing rerouting efforts and warned that higher latency might persist into September 7[1][3]. Despite Microsoft’s swift response and mitigation attempts, the incident highlighted the vulnerability of regional internet infrastructure and caused notable disruption before Azure services returned to normal[2][3].
🔄 Updated: 9/7/2025, 4:40:49 PM
Experts attribute the Azure latency issues to the simultaneous cuts of the SMW4 and IMEWE undersea cable systems near Jeddah, Saudi Arabia, which disrupted connectivity across the Middle East and parts of Asia, including India and Pakistan[2]. Microsoft acknowledged increased latency starting September 6 and emphasized that while traffic was rerouted to alternate paths, users could experience slower speeds until repairs are completed—a process that can take significant time for undersea cables[1][3]. Industry analysts highlight the vulnerability of global networks to regional cable failures, stressing the critical need for diversified routing infrastructure to mitigate such impacts.
🔄 Updated: 9/7/2025, 4:50:49 PM
The recent severing of multiple undersea cables in the Red Sea has prompted Microsoft to reroute Azure traffic, causing increased latency primarily affecting the Middle East and parts of Asia, but services have now been restored and remain operational[1][4][5]. This incident intensifies competition with Amazon AWS, the world's largest cloud provider, as Azure's temporary network delays could influence customer preferences and regional cloud service reliability perceptions[1]. Microsoft emphasized ongoing optimization efforts, stating, "We do expect higher latency on some traffic that previously traversed through the Middle East," while confirming no impact on traffic outside that region[1][3].
🔄 Updated: 9/7/2025, 5:00:54 PM
Azure experienced increased latency after multiple undersea fiber optic cables in the Red Sea were severed on September 6, 2025, disrupting network routes connecting Europe, Asia, and the Middle East. Microsoft rerouted traffic through alternate paths to maintain service continuity, with engineering teams actively monitoring and optimizing routing to reduce impact; Azure services are now reported operational, though some higher latency persists for traffic through the Middle East[1][3][4]. The incident drew international concern due to its effect on global internet infrastructure, highlighting vulnerabilities in undersea cable networks critical for intercontinental communications[3][4].
🔄 Updated: 9/7/2025, 5:10:46 PM
Following the multiple undersea cable cuts in the Red Sea affecting Azure latency, **Pakistan Telecommunications confirmed the cuts in a statement on Saturday, September 6**[3]. However, **Saudi Arabian authorities have not acknowledged the disruption and did not respond to requests for comment**, while the **UAE government also remained silent despite user reports of slower speeds on state-owned networks Du and Etisalat**[3]. No further regulatory or governmental interventions have been publicly announced as of September 7.
🔄 Updated: 9/7/2025, 5:20:49 PM
Microsoft Azure experienced significant latency issues starting September 6, 2025, following severance of two major undersea cable systems—the SEA-ME-WE-4 and IMEWE—near Jeddah, Saudi Arabia. These critical cables link Asia to Europe, and their damage disrupted traffic primarily for users in South Asia and the Gulf region, causing increased latency, packet loss, and service degradation for cloud-based applications reliant on this route[1][3]. Microsoft confirmed traffic rerouting efforts to alternative paths were underway but warned that “higher latency on some traffic” would persist into at least September 7, as repair and optimization continue[1][2].
🔄 Updated: 9/7/2025, 5:30:49 PM
Azure cloud services experienced increased latency after two major undersea cables, SEA-ME-WE-4 and IMEWE, were severed in the Red Sea near Jeddah, Saudi Arabia, on September 6, 2025. These cables are critical for connecting Asia to Europe, and their disruption forced Microsoft to reroute traffic, causing degraded performance and latency spikes for users in South Asia, the Middle East, and parts of Europe, especially affecting workloads dependent on Asia-Europe connectivity[2][4]. Microsoft stated that "undersea fiber cuts can take time to repair" and that they are "continuously monitoring, rebalancing, and optimizing routing" to mitigate impact, with service issues largely resolved by late September 6
🔄 Updated: 9/7/2025, 5:40:46 PM
Azure’s latency issues following multiple undersea cable cuts in the Red Sea have intensified competition in cloud connectivity routes, pressuring Microsoft to rapidly reroute traffic and optimize network paths. The SEA-ME-WE-4 and IMEWE cables—key long-haul links connecting Asia and Europe used by hyperscalers including Microsoft, Google, and Meta—experienced cuts that increased latency and packet loss for Azure users in South Asia and the Gulf, offering competitors a potential advantage in reliability during the disruption[2][1]. Microsoft acknowledged higher latency on affected routes through September 7, highlighting the strategic importance of diversifying undersea infrastructure in the cloud services competitive landscape[3].
🔄 Updated: 9/7/2025, 5:50:47 PM
Consumers and public reaction to Azure’s latency issues following multiple undersea cable cuts in the Red Sea has been marked by frustration and concern, especially in the Middle East and Asia where users faced increased delays. Many users reported disruptions to critical cloud services, prompting complaints on social media about slowed workflows, with some businesses warning of operational impacts. Microsoft acknowledged the problem, stating it rerouted traffic through alternate paths and expected "higher latency on some traffic that previously traversed through the Middle East," assuring daily updates as repairs continue[1][2].
🔄 Updated: 9/7/2025, 6:00:51 PM
Microsoft Azure experienced increased latency beginning September 6, 2025, after multiple undersea fiber optic cables in the Red Sea were severed, disrupting network routes connecting Europe, Asia, and the Middle East[3][4]. The company rerouted traffic through alternate paths to prevent interruptions and reported that by September 7, all Azure services in the Middle East were restored and operational, though some latency on affected routes may persist[1][2]. A Microsoft spokesperson stated, "We do expect higher latency on some traffic that previously traversed through the Middle East" and emphasized ongoing efforts to monitor and optimize routing until repairs are completed[1].