The FCC's July 2026 NG911 Order: What It Actually Requires of PSAPs and Carriers
The Second Report and Order expands who counts as a covered 911 service provider, retires annual certifications, and gives 911 Authorities direct information rights. Most obligations land on ESInet and NGCS operators.
By IPA-IAC · 7 min · 6 August 2026
The FCC’s NG911 reliability order — the Second Report and Order in PS Docket Nos. 21-479 and 13-75, circulated for the Commission’s June 25, 2026 open meeting and published in the Federal Register on July 10, 2026 — is being read in a lot of agencies as a new set of PSAP obligations. It largely is not.
The order’s requirements fall on a newly expanded category of service providers. What PSAPs and 911 Authorities get is mostly a new right to information, plus a clearer answer about who is accountable when a multi-state outage takes their calls down. That is a meaningful change, but it is a different change than “new mandates for dispatch centers.”
Here is what the item actually does.
The Problem It Addresses
The Commission’s 911 reliability framework dates to 2013, adopted after the June 2012 derecho left millions without 911 service for as long as several days — including four PSAPs in the National Capital Region that lost service completely. That framework required covered 911 service providers (CSPs) to certify annually against three benchmarks: circuit diversity, central-office backup power, and diverse network monitoring.
Those rules were written for a legacy architecture in which incumbent wireline networks carried calls through selective routers to central offices serving PSAPs. The Commission’s stated problem is blunt: as the NG911 transition proceeded, major multi-state 911 outages increased, and “too often, these outages have occurred in parts of transitional NG911 systems outside the scope of the 911 reliability framework adopted in 2013.”
In other words, the entities whose failure was actually taking 911 down were frequently not covered entities at all.
Change One: Who Counts as a Covered Provider
The central action is redefining CSP to reach “service providers that control or operate critical pathways and components in NG911 networks.” The updated definition expressly includes:
- Operators of Emergency Services IP networks (ESInets)
- Next Generation Core Services (NGCS) providers
This closes the gap above. An ESInet or NGCS operator whose failure can cause a significant outage is now subject to federal reliability standards, rather than sitting adjacent to a framework built around incumbent carriers.
The Commission’s reasoning is that these providers deliver NG911 capabilities functionally equivalent to the call routing, automatic location information, and automatic number identification functions that covered legacy facilities performed — which is the same logic the 2013 rules used, applied to current architecture.
Change Two: Modernized Reliability Benchmarks
The three benchmarks are retained in structure but rewritten for IP networks, drawing on best practices identified by the Commission’s CSRIC advisory committee:
Physical diversity now contemplates automatic rerouting, load balancing, and geographic distribution of routing facilities, transport nodes, and node links sufficient to eliminate single points of failure. The legacy version was about tagged circuits and annual diversity audits; the IP version is about whether traffic actually fails over.
Operational integrity replaces “central-office backup power.” It covers continuous power for location information server (LIS) and legacy network gateway (LNG) facilities, plus the capability to switch over automatically to geographically diverse facilities. The rename reflects that in an IP architecture, the question is not only whether a building has generators.
Network monitoring now means geographically distributed automatic disruption detection and alarm mechanisms appropriate to IP systems, rather than physically diverse monitoring links audited once a year.
Importantly, these are presumptively reasonable measures, not the only permitted ones. CSPs may satisfy their obligations through reasonable alternative measures — including measures requested by state, territorial, local, or tribal 911 Authorities. That clause is where a 911 Authority with specific local requirements has room to push, and it is worth knowing it exists before a negotiation rather than after.
Change Three: Annual Certifications Are Gone
This is the deregulatory half, and it cuts against the assumption that the order simply adds burden.
The requirement that CSPs file annual compliance certifications is eliminated. In its place: an 18-month transition period, after which CSPs file an initial reliability certification under the new rules and update it only when there is a material change.
For 911 Authorities, the practical consequence is that the annual filing cadence you may have relied on as a monitoring rhythm disappears. There will be an initial certification and then silence unless something material changes — which makes the new access rights below the thing to actually use.
Change Four: What 911 Authorities Get
Two provisions matter here.
Access to CSP certifications and reports, subject to confidentiality safeguards. State and local 911 Authorities can obtain key reliability, interoperability, and accessibility information directly from covered providers rather than inferring it. This is the order’s most useful grant to the public-safety side, and it is the one most likely to go unexercised, because using it requires someone in the authority to know it exists and to ask.
A codified enforcement path. The order codifies the Public Safety and Homeland Security Bureau’s process for investigating and remediating noncompliance. Predictable process cuts both ways — it gives providers notice, and it gives authorities a defined route for a complaint.
Interoperability: Reporting Now, Requirements Maybe
The order requires NGCS and ESInet CSPs to report their recent actions to enable interstate NG911 interoperability, and it adopts an NG911-specific definition of “interoperability” to end the ambiguity about what the word covers.
Reporting is not a performance mandate. The accompanying Second Further Notice of Proposed Rulemaking proposes going further — requiring multi-party interstate interoperability testing of 911 traffic — and separately seeks comment on integrating direct video calling into NG911 for accessibility. Both are proposals at the comment stage, not rules. Agencies planning around mandatory multi-state testing are planning around something that has not been adopted.
Where OSP Obligations Actually Come From
This is the most common point of confusion, so it is worth separating cleanly.
Carrier-side duties in the NG911 transition come from the July 2024 NG911 transition order, not from this one. That framework is two-phased and authority-initiated: a 911 Authority submits a valid request to originating service providers (OSPs) in its jurisdiction, and the OSP must comply with that phase’s requirements within a defined period — six months per phase for nationwide providers, twelve months per phase for non-nationwide providers. An OSP may petition the Bureau to challenge a request within 60 days of receiving it.
Those rules took effect in March 2025, and uptake has been substantial: 911 Authorities have issued more than 190 Phase 1 requests and one Phase 2 request, covering parts or all of 28 states and encompassing more than 2,200 PSAPs.
So when a vendor or carrier cites “the FCC’s new NG911 requirements,” establish which item they mean. Delivery obligations, valid-request mechanics, and per-phase deadlines are 2024. Reliability benchmarks, the expanded CSP definition, and certification reform are 2026.
Practical Next Steps
Identify your CSPs under the new definition. Whoever operates your ESInet and provides your Next Generation Core Services is now very likely a covered provider. Confirm it in writing.
Ask for the certification. Once the transition period runs and initial certifications are filed, request yours under the access provision. With the annual cadence retired, an initial certification plus material-change updates is the whole record.
Put your local reliability requirements in writing. The alternative-measures provision explicitly contemplates measures requested by 911 Authorities. A documented request is worth more than a preference expressed in a meeting.
Confirm exact effective and compliance dates from the Federal Register text. The Commission’s fact sheet describes the item in prospective terms and the codified rules appear in the order’s appendix; the operative dates for your obligations should come from the published version rather than from a summary — including this one.
Separate reliability from procurement. The order does not tell you which vendor to buy. It tells you which questions have federal answers now, which is a useful filter to carry into technology procurement and into any CAD/RMS interoperability discussion where “interoperable” has been doing a lot of undefined work.