The technology disruptions affecting the Federal Aviation Administration (FAA), Microsoft 365, and Amazon Web Services (AWS) in November 2026 have raised important questions about how organizations govern increasingly complex infrastructure. Within four days, failures involving telecommunications networks, enterprise cloud applications, and cloud authentication services interrupted operations across different sectors. Although the incidents were unrelated and involved distinct technical circumstances, they demonstrated how infrastructure dependencies can create operational risks that extend beyond the systems where problems originate.
The FAA issued a nationwide ground stop on November 13 after telecommunications instability affected air traffic control systems. Microsoft experienced a significant Microsoft 365 service disruption beginning November 12, affecting email and functions dependent on Exchange Online. On November 15, AWS reported authentication and connectivity problems within its US-EAST-1 region, affecting several cloud services and customers relying on shared infrastructure.
None of these incidents was established as a cyberattack. Their significance lies in the operational consequences of infrastructure instability, software defects, and technology dependencies. For CIOs and business executives, the events illustrate why IT governance must extend beyond routine maintenance and technical support to include architecture oversight, change management, vendor accountability, and business continuity planning.
Table of Contents
FAA telecommunications failure demonstrates the importance of infrastructure visibility
On November 13, 2026, the FAA issued a nationwide ground stop after instability developed within its telecommunications infrastructure. According to the agency’s November 15 explanation, excessive data traffic overwhelmed portions of the FAA Telecommunications Infrastructure network, commonly known as FTI. The system experienced approximately 1,000 connection attempts every four to five seconds, affecting the stability of communications and radar feeds used by air traffic controllers.
The FAA’s preliminary investigation identified two potential sources of excessive traffic: A radar site in Amarillo, Texas, and a radio communications facility in El Dorado, Arkansas. Network service provider L3Harris had been performing work at the Arkansas location, including deploying a new router. Engineers isolated the suspected sources and disabled certain router functionality to stabilize the network.
The disruption affected 17 of the FAA’s 22 Air Route Traffic Control Centers and spread into several terminal radar approach control facilities. The agency implemented the ground stop as a precaution while maintaining essential communications and safely managing aircraft already in flight. Operations resumed at approximately 8:15 p.m. Eastern Time.
The FAA reported approximately 12,462 flight cancellations that Friday, while emphasizing that not every cancellation was directly attributable to the ground stop. Its investigation also distinguished instability involving legacy telecommunications infrastructure from the agency’s broader modernization initiative.
For enterprise IT leaders, the incident illustrates why infrastructure governance requires detailed knowledge of network architecture, system dependencies, and the potential consequences of configuration changes. A component operating at one location can affect services across a much larger environment when systems share underlying communications infrastructure.
Microsoft’s outage exposes the complexity of shared cloud services
Microsoft’s November 12–13 disruption affected organizations relying on Microsoft 365 for communication, collaboration, and business operations. According to Microsoft’s preliminary post-incident report, the incident began at 16:20 UTC on November 12, with the preliminary report recording an incident end time of 16:10 UTC on November 13. Microsoft subsequently announced full recovery across remaining affected customers and regions on November 14, reflecting the distinction between the preliminary incident timeline and the broader restoration announcement.
The most significant impact involved Exchange Online, with users experiencing difficulty accessing mailboxes through Outlook and other email clients. Email delivery was also delayed for many customers. Additional effects involved functions within Microsoft Teams, SharePoint, OneDrive, Copilot, Defender, and other services that depend on Exchange Online capabilities.
Microsoft’s preliminary investigation identified three interacting technical factors contributing to the disruption. A latent software defect within its networking gateway affected request processing, while increased traffic following a Microsoft Teams gateway failover placed additional pressure on shared infrastructure. Approximately 14% of gateway server capacity was also temporarily unavailable, reducing the environment’s ability to absorb the increased workload. Together, these conditions overwhelmed affected servers and contributed to service interruptions across multiple applications.
The findings demonstrate how several individually manageable infrastructure conditions can combine to create a significant operational problem. A software defect may remain dormant until changes in traffic patterns expose it, while temporarily reduced capacity can limit the system’s ability to recover from unexpected demand. For organizations dependent on shared cloud platforms, these interactions reinforce the importance of understanding service dependencies rather than treating individual applications as entirely separate systems.
The outage also illustrates why cloud governance should include vendor escalation procedures, service availability monitoring, dependency mapping, and realistic continuity planning. Although customers cannot directly control Microsoft’s global infrastructure, they remain responsible for preparing their own operations to withstand temporary interruptions to essential services.
AWS connectivity problems highlight regional and identity dependencies
On November 15, AWS reported increased connectivity problems within its US-EAST-1 region in Northern Virginia. According to the AWS Health Dashboard’s incident-specific report, the disruption involved authentication errors, signup problems, and connectivity issues affecting several services.
Customers using AWS IAM Identity Center experienced authentication difficulties, including problems accessing the AWS Management Console and services dependent on that identity infrastructure. AWS also reported connectivity issues affecting a subset of Network Load Balancers operating within a single Availability Zone.
AWS engineers investigated the problems and implemented mitigation measures to restore affected services. Most services recovered after the authentication issues were addressed, while a smaller group of customers experienced continued connectivity problems until the remaining load-balancer issue was resolved.
The incident illustrates why cloud resilience cannot be evaluated solely according to whether an application is hosted by a major infrastructure provider. Organizations must also consider regional dependencies, identity services, network configurations, and the architecture supporting access to critical applications.
An application may remain operational at the infrastructure level while users cannot authenticate or establish reliable connections. Similarly, a service deployed within a single Availability Zone may face different availability risks from one designed to operate across multiple zones.
AWS recommended that customers requiring immediate resolution for the affected load-balancer configuration consider deploying targets across multiple Availability Zones. This recommendation reflects a broader architectural principle: Resilience depends on how cloud services are configured and interconnected, not simply on the provider hosting them.
Why enterprise IT governance must extend beyond technical maintenance
The three incidents demonstrate different failure scenarios, but each raises questions about how organizations identify and manage technology dependencies.
Traditional IT management often emphasizes device maintenance, software updates, help desk operations, and troubleshooting. These activities remain essential, but they do not fully address the governance requirements of modern enterprise environments.
Businesses increasingly depend on hybrid infrastructure combining on-premises systems, cloud applications, telecommunications providers, specialized software, and external technology partners. Decisions involving one component can influence the reliability of several others.
A managed IT services provider can support organizations through infrastructure monitoring, proactive maintenance, technical support, and coordinated IT administration. However, businesses should evaluate whether their service arrangements also address architecture documentation, vendor coordination, change management, and continuity planning.
These responsibilities should be clearly defined because infrastructure support does not automatically include every aspect of enterprise architecture or business continuity governance.
For mid-sized organizations, establishing a coordinated operating model can be particularly valuable when internal technology resources are limited and multiple vendors support different parts of the environment.
Dependency mapping is becoming a critical management requirement
One of the most important lessons from the November disruptions is the need to understand how technology systems depend on one another.
Dependency mapping identifies the infrastructure, applications, services, and external providers required to support a particular business function. This information helps technology teams understand which systems may be affected when a component becomes unavailable.
For example, a business application may depend on cloud hosting, identity authentication, network connectivity, database services, and external integrations. If employees cannot access the application, the problem may originate in any of these components.
Without documented dependencies, troubleshooting can become fragmented as teams investigate individual systems without understanding the broader architecture.
Organizations should maintain records identifying critical applications, their supporting infrastructure, responsible vendors, and relevant recovery requirements. These records should be reviewed whenever major technology changes occur.
Dependency mapping also supports investment decisions because it helps executives identify systems whose failure could interrupt multiple business processes.
Change management must account for operational consequences
The FAA incident provides a particularly relevant example of why technology changes require disciplined governance. Network equipment replacement and configuration adjustments are routine activities, but they can produce unexpected consequences when existing dependencies are not fully understood.
Effective change management should begin with an assessment of the systems potentially affected by a proposed modification. Technical teams should evaluate compatibility requirements, operational risk, maintenance timing, and available rollback procedures before implementing significant changes.
Testing should reflect realistic operating conditions whenever practical, particularly when changes involve essential infrastructure or services with limited tolerance for downtime.
Organizations should also establish approval requirements proportionate to the potential business impact. A routine workstation update does not necessarily require the same oversight as a network configuration change affecting multiple facilities.
After implementation, monitoring should confirm that the intended changes are functioning correctly and that connected systems have not developed unexpected problems.
These procedures cannot eliminate every technical failure, but they can reduce avoidable disruptions and improve the organization’s ability to respond when changes produce unintended consequences.
Cloud resilience requires more than selecting a reliable provider
The Microsoft and AWS incidents illustrate why organizations should distinguish between provider reliability and the resilience of their own application architecture.
Cloud providers operate extensive infrastructure and offer services designed to support availability, scalability, and recovery. However, the availability experienced by an individual customer depends partly on how those services are configured and which dependencies the organization uses.
A business may distribute application workloads across multiple servers while relying on a single identity service. Another organization may maintain redundant databases but depend on one external integration to complete essential transactions.
These dependencies can create operational bottlenecks even when other components remain available.
IT governance should therefore evaluate redundancy, authentication dependencies, recovery requirements, and alternative operating procedures according to the importance of each business function.
Not every organization requires multi-region infrastructure or complex failover arrangements. These investments should be justified by business requirements, recovery objectives, and the consequences of downtime.
The objective is to establish resilience appropriate to the organization’s actual operational risk rather than implementing unnecessary technical complexity.
Five governance priorities for CIOs and business executives
The November incidents provide an opportunity for organizations to evaluate whether their technology governance practices adequately support operational resilience.
Establish clear ownership of critical systems
Every essential application and infrastructure component should have an identified business owner and technical support responsibility. Organizations should understand which internal teams and external providers are accountable for maintenance, monitoring, incident escalation, and recovery.
Maintain accurate infrastructure documentation
Technology inventories should identify critical assets, cloud services, network connections, software dependencies, and relevant vendor relationships. Documentation should be updated when systems are introduced, modified, or retired.
Strengthen change management and testing
Organizations should establish risk-based procedures for infrastructure changes, software upgrades, and configuration modifications. These procedures should include testing, approval requirements, rollback planning, and monitoring appropriate to the potential operational consequences.
Review cloud architecture and identity dependencies
IT teams should evaluate how essential applications depend on authentication platforms, network services, cloud regions, and external integrations. Where business requirements justify additional resilience, organizations should consider redundancy and alternative access arrangements.
Test business continuity and recovery procedures
Continuity exercises should include scenarios involving unavailable cloud applications, telecommunications disruptions, authentication failures, and third-party service interruptions. Testing should assess both technical recovery capabilities and the organization’s ability to maintain essential business functions.
Why operational resilience belongs in executive reporting
Technology governance becomes more effective when executive leadership receives information that connects technical performance to business consequences.
Traditional IT reports may emphasize ticket volumes, system uptime, patch completion, and infrastructure utilization. These measures provide useful operational information, but they do not necessarily explain whether the organization is prepared for a significant technology disruption.
Executives should also understand which systems support critical business processes, whether recovery procedures have been tested, and which dependencies present material operational risks.
Reporting should identify unresolved infrastructure concerns, significant vendor dependencies, modernization priorities, and the business implications of proposed technology investments.
For healthcare organizations, these discussions may involve clinical system availability and administrative continuity. Manufacturers may prioritize production applications, supplier integrations, and operational technology. Professional services firms may concentrate on secure access to client information and collaboration platforms.
Although the priorities differ, the governance objective remains consistent: Technology decisions should support operational reliability and clearly defined business requirements.
What the November 2026 outages mean for enterprise technology strategy
The FAA, Microsoft, and AWS disruptions demonstrate that sophisticated technology environments remain vulnerable to failures involving infrastructure instability, software defects, and shared service dependencies.
These incidents should not be interpreted as evidence that cloud computing or infrastructure modernization is inherently unreliable. They demonstrate that technology resilience depends on architecture, implementation, governance, and recovery planning.
Organizations cannot prevent every failure affecting an external provider or interconnected system. They can, however, improve their readiness through accurate dependency mapping, disciplined change management, coordinated vendor oversight, and tested continuity procedures.
For CIOs and business executives, the priority is to establish a technology operating model that connects infrastructure management with enterprise risk and business continuity.
As organizations become increasingly dependent on interconnected systems, operational resilience will depend less on the reliability of individual components and more on how effectively the entire technology environment is governed.