What Are the New VoIP 911 Rules Taking Effect in August 2026?
As of August 10, 2026, the FCC’s updated Next Generation 911 reliability rules under FCC 26-39 require VoIP providers and 911 communications service providers to meet modernized standards for IP-based emergency call delivery, network reliability, and interstate interoperability. For small businesses using cloud phone systems, this means your provider must now comply with stricter 911 infrastructure requirements, and you should verify that your registered E911 address is current and accurate for every user and location on your account.
Effective date is August 10, 2026. The rules were published in the Federal Register on July 10, 2026, with a compliance guide for small entities released July 27, 2026.
Your provider carries the compliance burden. The rules apply to interconnected VoIP providers and 911 service providers, not directly to end-user businesses. But your provider’s compliance depends partly on information you supply.
The biggest risk is an outdated E911 address. If your registered emergency address does not match where your team actually works, 911 responders could be dispatched to the wrong location.
What the FCC Changed on July 10
The FCC adopted the Second Report and Order in PS Docket Nos. 21-479 and 13-75 (FCC 26-39), modernizing 911 reliability rules for networks that have transitioned from legacy TDM (circuit-switched) infrastructure to IP-based systems. The order was published in the Federal Register on July 10, 2026, with rules taking effect on August 10, 2026.
The core changes affect how 911 communications service providers, which include interconnected VoIP providers, manage emergency call routing, network redundancy, and outage reporting. The FCC eliminated several legacy rules that applied only to older circuit-switched networks and replaced them with requirements tailored to how modern IP-based voice systems actually operate. The order also addresses interstate interoperability, meaning 911 calls that cross state lines must work seamlessly regardless of which NG911 system handles the routing.
For context, FCC data from May 2025 shows that 74.5 percent of residential and 80.2 percent of business wireline voice service in the United States is now IP-based. The rules reflect a regulatory framework catching up to how most businesses already receive phone service. If your company uses a VoIP system from any provider, these rules apply to the infrastructure carrying your calls.
Does This Apply to My Business?
The rules directly regulate VoIP providers, not the small businesses subscribing to their service. But the effect reaches you through two channels. First, your provider’s ability to deliver reliable 911 service depends on accuracy of the information you provide during setup and whenever your business moves or adds locations. Second, the FCC requires VoIP providers to warn customers about E911 limitations, including the fact that VoIP 911 may not function during internet or power outages.
This applies to every business using a cloud-based phone system, regardless of size. If your team includes remote workers, multiple office locations, or employees who use softphones from home, each of those endpoints should have a current E911 address registered with your provider. The most common scenario we see in our onboarding process at Phone Service Now is a business that set up their phone system once, verified the address at that time, and never updated it when they moved, added a second location, or shifted staff to remote work. That single oversight can send emergency responders to an old office.
Medical practices, law firms, home service companies, real estate teams, and staffing firms are the most common business types we work with, and all of them have at least one employee working from a location that does not match the original address on file. For any business evaluating how to choose the right business phone system, E911 compliance should be part of the decision criteria.
Why the FCC Updated 911 Rules Now
The transition from legacy 911 to NG911 has been underway for over a decade, but the pace accelerated in 2024 and 2025 as more public safety answering points (PSAPs) moved to IP-based systems. The old reliability rules were designed for a world where 911 calls traveled over dedicated copper circuits. Those rules did not account for the routing complexity, shared infrastructure, and software dependencies of modern VoIP and cloud-based voice systems.
The FCC noted that 911 outages continued to occur on IP-based networks, sometimes affecting thousands of callers for hours. A fiber optic line maintenance incident in Montana in March 2026 caused a 911 outage in Cascade County, illustrating how a single infrastructure event can disrupt emergency service on IP-based networks. The new rules require providers to implement specific reliability measures that address these vulnerabilities, including network redundancy, backup power, and faster outage reporting to PSAPs.
For small business owners, the practical takeaway is that your VoIP provider should be investing in the infrastructure behind your phone service, and you should be asking whether they are compliant with the August 2026 requirements. A provider that cannot confirm compliance is a risk you do not need to carry.
If you want to confirm that your business phone system meets the latest FCC 911 reliability requirements, or if you need help verifying your E911 address across all your locations, talk to our team.
What Do These Rules Mean for Your Day-to-Day Phone Service?
In practical terms, you should not notice a difference in how your phone system operates on August 11 compared to August 9. The rules do not change how you dial 911 or what happens when you place an emergency call. What changes is the standard your provider must meet behind the scenes.
Your provider must now ensure that their NG911 network components have adequate redundancy, that outage notifications reach affected 911 centers faster, and that their systems interoperate with NG911 infrastructure in any state where they deliver service. For businesses with employees in multiple states, this is meaningful. A provider that operates only in legacy-compatible mode may face compliance gaps that affect emergency call reliability for your remote team members.
One specific area to watch is E911 address accuracy for softphone and mobile app users. When an employee dials 911 from a VoIP softphone on their laptop at home, the system routes emergency services based on the registered address, not the device’s physical location. If that address has not been updated, the response goes to the wrong place. The FCC’s updated rules reinforce that providers must have processes to collect and maintain accurate location data, but the data itself comes from you.
What Should You Do Before August 10?
The compliance burden falls on your provider, but these steps protect your business and your team.
Verify every E911 address on your account. Log into your VoIP admin portal or contact your provider. Confirm that every user, extension, and location has the correct physical address registered for emergency services.
Update addresses for remote workers. Any employee using a softphone, desk phone, or mobile app from a location other than your primary office needs their home or current work address registered as their E911 address.
Ask your provider about NG911 compliance. Request written confirmation that your provider meets the FCC 26-39 requirements taking effect August 10, 2026. A compliant provider should be able to answer this clearly.
Test your 911 configuration without placing a live call. Some providers offer a non-emergency test mechanism (such as dialing 933 where available) to confirm that the system reads back the correct registered address. Ask your provider if this option exists.
Review what happens during an internet outage. VoIP 911 depends on your internet connection. Ask your provider what failover options exist, such as automatic routing to a mobile number if the primary connection drops.
Document your verification. Keep a record of when you last verified each E911 address, who verified it, and any provider confirmation of compliance. If a 911 issue ever arises, this documentation protects your business.
Common Mistakes with VoIP 911 Setup
We handle phone system setup for businesses every week, and the same E911 mistakes appear consistently. These are the ones that create the most risk.
Setting the E911 address once and never updating it. This is by far the most common issue. Businesses move, add locations, or shift employees to remote work and forget that their 911 address is still pointing to the old office. The fix takes less than five minutes, but it has to happen every time a location changes.
Assuming the VoIP app uses GPS for 911 location. It does not. Unlike a cell phone dialing 911, a VoIP softphone sends the registered address, not the device’s GPS coordinates. This is a fundamental difference that catches people off guard during an actual emergency.
Not registering E911 for toll-free or virtual numbers. If your business uses a toll-free number as its main line, E911 still needs a registered physical address associated with the account. Toll-free and virtual numbers do not automatically carry location data.
Ignoring the provider’s E911 disclosure. The FCC requires VoIP providers to provide a written disclosure about E911 limitations. This is not fine print you can skip. It tells you what your service cannot do in an emergency, and that information affects how you plan for business continuity.
In-House Landline vs. Cloud VoIP for 911
Businesses sometimes assume that keeping a traditional landline is safer for 911 than switching to VoIP. That assumption was more defensible five years ago than it is today. Here is how the two compare under the current FCC framework.
| Factor | Traditional Landline | Cloud VoIP (Compliant Provider) |
|---|---|---|
| 911 address accuracy | Tied to the physical line location | Registered per user; must be updated manually |
| Remote worker coverage | No coverage for off-site employees | E911 address can be set per user and location |
| Outage behavior | Works during power outages (copper) | Requires internet; failover options available |
| NG911 compatibility | Legacy; may not support text or data | Fully compatible with IP-based NG911 |
| Monthly cost per line | $40 to $75+ per line | $18.99 to $27.99 per user (Phone Service Now) |
| FCC 26-39 compliance | Not applicable (legacy framework) | Required as of August 10, 2026 |
| Best for | Single-location, no remote staff | Multi-location, remote teams, growing businesses |
For most small businesses with any remote employees or plans to grow, a compliant VoIP provider offers better 911 coverage than a landline because you can register addresses per user rather than per physical line. The key word is “compliant.” A VoIP provider that has not invested in NG911 reliability infrastructure is not a safer option than a landline. We built Phone Service Now to meet these standards from day one, and the affordable pricing structure reflects that compliance is included, not an add-on.
Frequently Asked Questions
Do the new 911 rules apply to my small business directly?
The FCC 26-39 rules apply to your VoIP provider, not to your business directly. However, your provider’s compliance depends on the accuracy of the E911 address information you supply. You are responsible for keeping that information current for every user and location on your account.
What happens if my E911 address is wrong when someone dials 911?
Emergency responders will be dispatched to the address registered in the system, not to the caller’s actual location. If that address is outdated or incorrect, responders go to the wrong place, which can delay life-saving assistance by critical minutes.
Does VoIP 911 work during a power or internet outage?
Standard VoIP 911 requires an active internet connection. If your internet goes down, 911 calls from your VoIP phones may not go through. Ask your provider about failover options such as automatic forwarding to a mobile number or battery backup for your router and phone equipment.
How do I check my current E911 address?
Log into your VoIP provider’s admin portal and look for the E911 or emergency services section. Each user or extension should show a registered physical address. If you cannot find it, contact your provider directly and ask them to confirm the address on file for every active line.
Is a traditional landline safer for 911 than VoIP?
Traditional copper landlines automatically transmit location data and work during power outages, which gives them a reliability advantage in single-location setups. However, a compliant VoIP provider offers per-user E911 registration that covers remote workers, which landlines cannot do. For multi-location businesses, VoIP with proper E911 setup provides broader coverage.
How often should I verify my E911 addresses?
Verify E911 addresses every time an employee changes work location, your office moves, you add a new line or user, or your provider makes a system change. At minimum, review all addresses quarterly. The verification takes minutes and the consequences of an outdated address are severe.
Next Steps
Start by verifying every E911 address on your account before August 10. If your current provider cannot confirm FCC 26-39 compliance, that is a signal worth taking seriously. For businesses comparing options, our guide to choosing a business phone system covers what to look for in a provider, including 911 compliance.
If you are setting up a VoIP system for the first time, our team walks you through E911 registration during onboarding so every address is verified before your first call goes live. Setup typically takes one business day from start to finish.
Ready to switch to a VoIP provider that handles 911 compliance from day one? Talk to our team about getting set up before the new rules take full effect.