Key Takeaways

  • The FCC is investigating a January 2026 Verizon outage that lasted at least ten hours and left millions unable to make calls or texts
  • Public comments are being solicited on the outage’s impact on consumers, businesses, and emergency response services
  • The inquiry focuses heavily on 911 access, PSAP operations, and the adequacy of Verizon’s public communications during the disruption

The Federal Communications Commission’s Public Safety and Homeland Security Bureau has opened a formal proceeding to gather details about the wide‑ranging Verizon outage that occurred on January 14, 2026. The agency wants to understand not only how millions of wireless subscribers were affected, but also how the disruption rippled across public safety systems, enterprise operations, and government networks that rely on always‑on connectivity. It is an event that forces an uncomfortable question: what happens when one of the nation’s largest carriers simply goes dark for hours?

The outage, which lasted at least ten hours according to the FCC’s notice, left many Verizon customers unable to make or receive calls or text messages. Reports of phones stuck in “SOS mode” circulated widely, highlighting how quickly people recognized something was wrong. Although SOS mode allows emergency calling in theory, the Bureau is seeking to determine whether subscribers could actually reach 911 during the event—particularly those who experienced complete loss of mobile voice and data service.

Critical incidents like this often expose the hidden interdependencies between carriers. The FCC is asking whether customers on other networks were able to complete calls to Verizon numbers, raising potential questions about cross-network termination and routing during major outages. It serves as a reminder that network reliability is not a single-provider concern; resilience is intertwined across the ecosystem.

The Bureau’s inquiry also explores Verizon’s own handling of the incident. Key questions focus on how customers learned about the outage and whether the company’s communication was timely and effective enough to inform consumers, enterprise customers, and emergency services. For businesses—especially hospitals and other critical infrastructure providers—lack of clear information can impact operations almost as much as the outage itself. The FCC is refraining from any early judgment; this phase is about collecting data rather than assigning blame.

Public sector entities are another focal point. Many state and local agencies rely on prioritized voice and data services for first responders. The Bureau is asking whether those services were disrupted and, if so, how emergency operations were affected. The questions extend beyond pure connectivity into operational tempo, seeking to determine if the outage slowed dispatch, complicated coordination, or forced agencies onto backup systems designed only for short-term use. The notice invites agencies to describe the real operational conditions they faced.

Public Safety Answering Points (PSAPs) sit at the center of the most sensitive line of inquiry. The FCC wants to know how many 911 calls were attempted during the outage and whether any of those attempts failed. It also asks if the calls that did go through were delivered with the correct automatic number and location information. While such details may seem minor, they can determine whether first responders find a caller in minutes or lose precious time. PSAPs train for scenarios where they cannot verify caller location, but the operational reality creates significant risk.

Text-to-911 is also on the table. For PSAPs capable of receiving emergency texts, the Bureau asks whether inbound or outbound messages were disrupted. The fact that the FCC explicitly highlights this point demonstrates how quickly text-based emergency communication has become a core component of public safety infrastructure.

Another notable thread concerns notification. Did Verizon provide timely and actionable information to PSAPs about the outage? If not, how did they learn of it—through their own call monitoring systems, through local reports, or simply by being unable to receive calls? The lack of accurate information can significantly impact resource planning. For example, some PSAPs might shift additional staff into call-taking positions when they expect spikes, but they can only do that if they are aware of the situation. The Bureau is seeking descriptions of the contingency measures PSAPs implemented and whether those measures effectively maintained public access to emergency services.

The FCC is encouraging comments not only through its electronic filing system but also via a dedicated email address, VerizonOutage2026@fcc.gov, for individuals who want to share experience-based accounts. The comment window runs through March 16, 2026, giving stakeholders several weeks to assemble input. It is a broad call to participate, with telecom companies, public safety agencies, enterprises, and ordinary consumers all playing a role in painting a full picture of the outage and its consequences.

This proceeding, designated PS Docket No. 26‑21, is being treated as exempt under the FCC’s ex parte rules, meaning discussions with Commission staff do not require disclosure. This approach is intended to streamline the fact-finding process so the Bureau can assess what happened and what systemic vulnerabilities the incident might reveal.

While the FCC’s notice doesn’t speculate on future regulatory action, the level of detail in its questions hints at areas where policy adjustments or reliability mandates could eventually surface. Mobile networks have become essential infrastructure—not just for consumers, but for emergency responders and government operations. Events like the January outage underscore how fragile those systems can be, making this inquiry particularly urgent as the stakes go far beyond dropped calls.