Telecom providers need two separate but coordinated processes when a network failure affects emergency communications: one to notify affected 911 or 988 facilities quickly, and another to submit accurate outage reports to the Federal Communications Commission (FCC).
Two FCC notices released in September 2026 highlight why treating these responsibilities as a single reporting task can cause problems.
The first notice, issued September 25, focuses on timely, useful notifications to emergency-service facilities. The second, issued September 29, addresses the quality and completeness of reports submitted through the Network Outage Reporting System (NORS).
For network operations centers (NOCs), carriers, mobile virtual network operators (MVNOs), wholesale transport providers, and compliance teams, the practical message is clear: detecting an outage, communicating its impact, and documenting its cause are connected responsibilities, but they require different actions.
The September 25 FCC Notice Puts Emergency-Service Communication First
The FCC’s September 25 notice on 911 and 988 outage notifications reminds covered communications providers that affected emergency-service facilities need actionable information as soon as possible.
Under the applicable rules, providers must notify potentially affected 911 or 988 special facilities no later than 30 minutes after discovering a qualifying outage. Notifications must be sent sooner whenever possible.
The FCC also expects providers to take reasonable steps to discover outages. Waiting for customers to complain is not a substitute for appropriate network monitoring.
The obligation matters because public safety answering points (PSAPs), which receive and process emergency calls, need to understand whether their services are affected.
A useful notification should explain:
- Which provider and services are affected.
- When the incident began, including the relevant time zone.
- Which geographic areas may be affected.
- Whether emergency calls, callback information, or location information may be disrupted.
- How the emergency-service facility can contact the provider.
- The best-known cause and estimated restoration time, when available.
- Whether the message is an initial notification, an update, or a final assessment.
The FCC’s concern is not simply whether a notification was transmitted. The information must help emergency-service personnel understand the potential consequences.
A generic message stating that a provider is experiencing technical difficulties offers little operational value.
An alert identifying a possible loss of 911 call routing in a specific service area gives the receiving facility a much stronger basis for response.
Providers should communicate the information they reasonably have available rather than delay notification until every technical detail is confirmed. Unknown information must not be presented as established fact.
Emergency Notifications and NORS Reports Follow Different Rules
A common source of confusion is the difference between notifying an emergency-service facility and reporting an outage to the FCC.
The FCC’s outage reporting requirements under 47 CFR § 4.9 establish different reporting duties depending on the provider, service, incident characteristics, and applicable thresholds.
For many qualifying outages involving cable, wireless, wireline, and certain other providers, the rules require an initial NORS notification to the FCC within 120 minutes of discovery.
Interconnected VoIP providers have different NORS notification deadlines, including provisions for 240-minute and 24-hour reporting depending on the outage category.
These FCC filing deadlines must not be confused with the separate 30-minute requirement to notify potentially affected 911 or 988 special facilities.
For qualifying outages, covered providers may also have subsequent reporting obligations. Certain provider categories must submit an initial report within 72 hours and a final report within 30 days. The exact requirements depend on the applicable section of the rules.
An effective incident management system therefore needs at least two distinct reporting tracks.
The emergency-service notification track focuses on immediate operational consequences for potentially affected facilities.
The NORS reporting track focuses on providing the FCC with the information required to assess the disruption, its scale, and its causes.
One incident may trigger both processes, but completing one does not automatically satisfy the other.
Telecom professionals who need broader background on how these requirements fit into federal communications regulation can use NATEWIN’s regulatory learning path covering FCC, 911, CALEA, and spectrum requirements.
The September 29 Notice Raises Expectations for Report Quality
The FCC’s September 29 guidance on NORS filings addresses another operational problem: reports that fail to explain what happened.
The notice identifies several areas requiring attention.
Incident Descriptions Must Explain the Actual Disruption
A NORS report should provide an understandable account of the event.
Internal alarm codes, unexplained abbreviations, and incomplete ticket notes may not adequately describe the impact.
A useful incident description identifies the affected service, the sequence of relevant events, the actions taken to restore operations, and the available evidence concerning the cause.
At the final-report stage, the FCC expects providers to use the findings available from a reasonable investigation rather than automatically classify an incident as unresolved.
Affected-User Estimates Need Supporting Evidence
The FCC specifically warns against substituting an operator’s entire subscriber base for a reasonable estimate of potentially affected users when better information is available.
For example, an outage affecting one regional component does not necessarily mean every customer served by that provider experienced a disruption.
Operations teams should use appropriate technical evidence, such as affected network elements, service areas, routing dependencies, and relevant subscriber information, to develop the estimate required by the applicable reporting rules.
When precise information is unavailable, a reasonable estimate should be identified as such and updated when better evidence becomes available.
This is particularly important for organizations whose incident systems were designed mainly to restore network service rather than measure customer impact.
Outsourcing Network Infrastructure Does Not Automatically Remove Reporting Responsibilities
The September 29 notice also addresses non-facilities-based resellers, including MVNOs.
An MVNO may provide mobile services using another operator’s radio access network and supporting infrastructure.
That arrangement does not automatically exempt the MVNO from relevant NORS obligations.
The FCC explains that covered resellers may have reporting responsibilities for qualifying outages involving facilities they lease or otherwise use.
This creates an important dependency.
A reseller may rely on an underlying network provider for technical incident information while remaining responsible for determining and meeting its own applicable reporting obligations.
Contracts and operational agreements should therefore address how outage information reaches the responsible teams, what information will be shared, and how updates will be handled.
The September guidance is a reminder of existing responsibilities, not a new blanket reporting requirement for every network interruption.
Qualifying Outages Must Be Distinguished From Ordinary Network Alarms
Not every packet loss event, equipment alarm, or brief service interruption triggers the same federal reporting obligation.
The definitions in 47 CFR § 4.5 distinguish general network outages from incidents that potentially affect 911 or 988 special facilities.
For example, the regulatory definition of an outage potentially affecting a 911 special facility includes several alternative conditions involving call routing, selective routers, switching equipment, or emergency-call location information.
Some conditions involve specified duration and user-minute thresholds. Others have different technical criteria.
For 988, the definition addresses loss of the Lifeline’s ability to receive, process, or forward calls, subject to the stated duration and user-minute conditions.
A provider therefore needs evidence about the affected service and network function before deciding which notification requirements apply.
This distinction protects against two problems.
The first is underreporting: a provider incorrectly assumes an outage does not qualify because it affects relatively few ordinary customer services while overlooking a separate emergency-service criterion.
The second is poor-quality reporting: a provider sends broad, unnecessary alerts without reasonably determining which special facilities may actually be affected.
The goal should be accurate classification followed by timely action—not minimizing reporting or sending indiscriminate notifications.
Build an Outage Response Process That Works Across Providers
The two September notices point toward a practical improvement: telecom incident procedures should connect network evidence, regulatory classification, facility communication, and ongoing investigation.
A useful workflow begins before any outage occurs.
Establish Clear Ownership
The network operations team should know who identifies potential emergency-service impact.
The regulatory or compliance team should maintain a documented method for determining applicable reporting obligations.
A designated communications function should know who contacts affected facilities and how those contacts are recorded.
These responsibilities may overlap in smaller organizations, but the process should never depend on employees guessing who is responsible.
Maintain Reliable Emergency-Service Contact Information
Under the applicable FCC rules, covered providers must exercise special diligence to maintain appropriate emergency-service contact information, including the specified annual confirmation requirements.
Contact management should be part of normal operations rather than something attempted during a major incident.
Providers should also identify alternative communication methods for situations in which their normal systems are unavailable.
Preserve Evidence Across the Incident
Incident records should connect discovery times, affected facilities, network alarms, service-impact estimates, notification history, mitigation actions, and restoration evidence.
Where another carrier or vendor contributes to call processing or transport, relevant discovery information should reach the responsible provider promptly. The FCC’s September 25 notice emphasizes that the use of third parties does not remove the covered provider’s responsibility.
The same incident record can support technical recovery, public-safety communication, and later regulatory filings without assuming those outputs require identical information.
Treat Restoration and Reporting as Separate Completion Checks
A network may return to normal before the regulatory reporting process is finished.
Conversely, an initial report may be submitted while engineers are still investigating the root cause.
Closing a technical incident should not automatically close associated notification or filing tasks.
Before final closure, teams should confirm that required restoration messages, follow-up reports, and investigation records have been completed.
For a practical approach to maintaining consistent procedures, NATEWIN’s guide to writing reusable telecom engineering playbooks provides a related foundation for documenting operational knowledge.
A Short Exercise Can Reveal Reporting Weaknesses Before an Actual Outage
Telecom operators can test these processes through a controlled tabletop exercise without deliberately interrupting live emergency services.
An exercise could involve a hypothetical wholesale transport failure that disrupts a subset of emergency calls.
Participants should work through the same questions they would face during a real incident:
- Who receives the first technical warning, including information from third-party providers?
- Who determines whether the applicable 911 or 988 outage criteria are met?
- Which emergency-service facilities may be affected?
- Who prepares and sends required notifications?
- Can the team produce a defensible estimate of affected users?
- How are updates, service restoration, and final investigation findings documented?
The most useful result is not a declaration that the organization passed the exercise.
It is a short, assigned improvement plan identifying missing contacts, unreliable data, unclear ownership, slow escalation, or documentation that would not support a complete filing.
Network operations, public-safety communications, regulatory compliance, vendor management, and incident response should all participate when their responsibilities are relevant.
The exercise should also check the timing of the first follow-up notification. Under the applicable 911 and 988 rules, additional material information must be communicated promptly, with the first required follow-up generally due no later than two hours after initial contact for the specified provider categories. Restoration information must also reach affected facilities as required.
What Telecom Operators Should Prioritize
The September 2026 notices do not mean every communications provider suddenly faces an entirely new reporting framework.
They show that the FCC is emphasizing how existing responsibilities are carried out.
For telecom operators, three improvements deserve particular attention: identifying emergency-service impact promptly, maintaining accurate communication with affected facilities, and producing meaningful technical evidence for regulatory reports.
These improvements require cooperation between engineering, regulatory, customer-impact analysis, and supplier-management teams.
The strongest outage response process is one that can answer three questions with defensible evidence: Who is affected, who has been informed, and what do we know about the cause and recovery?
A provider that can answer those questions accurately is better prepared to support public safety, manage service restoration, and meet its applicable reporting responsibilities.