Home / Companies / Bandwidth / Blog / Post Details
Content Deep Dive

The state of NG911 in 2026: Robin Erkkila | Bandwidth

Blog post from Bandwidth

Post Details
Company
Date Published
Author
Robin Erkkila
Word Count
1,237
Company Posts That Month
8
Language
English
Hacker News Points
-
Post removed?
No
Summary

Next Generation 911 (NG911) aims to replace legacy analog emergency-call infrastructure with IP-based networks, but its adoption has been slowed by fragmented governance across devices, carriers, 911 networks, and local Public Safety Answering Points (PSAPs). A new FCC order creates a mechanism for local authorities that meet specified readiness requirements to request NG911 service from originating service providers, which must comply within six months, aligning incentives between locally governed emergency systems and federally regulated carriers. The transition has two stages: Phase 1 routes voice calls through IP connections while retaining legacy location systems, and Phase 2 transmits location data over IP and retires older Automatic Location Information databases, though differing local technical approaches make the latter more difficult. More than 800 PSAPs reportedly have Phase 1 connectivity, while Phase 2 remains at an early stage. California’s delayed and costly statewide deployment illustrates the risks of unresolved governance and coordination, while more advanced states demonstrate the value of establishing clear oversight before implementing technology. The passage also argues that carriers and enterprises will need to prepare for growing NG911 connection requirements, and presents Bandwidth’s network aggregation service as one approach to reducing the operational complexity of routing emergency calls across legacy and modern networks.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.