What Happens to Your Phones When the Internet Goes Down

Every business that considers switching to VoIP asks the same question: "What happens when the internet goes down?"

It is a fair question. With traditional phone lines, the phone system and the internet were completely separate. You could lose your internet connection and still make calls. VoIP ties your phones to your internet connection, and that feels like putting all your eggs in one basket.

Here is the truth: an internet outage does not have to mean phone silence. But it will, if you have not planned for it. This post covers exactly what happens to your phones when connectivity drops, what your provider does (or does not do) on their end, and how to set up your system so that calls keep flowing even when your internet does not.

The first thirty seconds: what your phones actually do

When your internet connection drops, your VoIP phones do not immediately know the internet is gone. They know something is wrong, but they cannot tell the difference between "the internet is down" and "there is a brief network hiccup."

Here is the sequence:

Seconds 0-5. Active calls drop. If you are on a call when the connection fails, the audio stops. VoIP sends packets every 20 milliseconds, and when those packets suddenly stop arriving, both sides hear silence. After a few seconds of silence, most VoIP applications and desk phones recognize the call has been lost and disconnect it. There is no graceful goodbye. The call simply ends.

Seconds 5-15. Phones detect the problem. Your desk phone or softphone tries to send its regular keepalive messages to the VoIP provider's server. These messages, called registration refreshes, are how your phone says "I'm still here, still reachable at this address." When those messages get no response, the phone knows something is wrong.

Seconds 15-30. Phones show an error state. The display changes. Desk phones typically show "No Service," "Network Unavailable," or "Unregistered." Softphone apps show a red indicator or a connection error banner. The phone starts trying to reconnect, sending registration attempts at increasing intervals.

At this point, your phones are paperweights. They cannot make or receive calls. The handsets still have power (assuming they are plugged in or have battery), but they have no connection to the phone system.

What happens to calls people try to make to you

This is where it gets interesting, and where preparation matters enormously. When someone calls your business number during an outage, the call does not just vanish into a void. It goes to your VoIP provider's servers, which are almost certainly not affected by your local internet outage. Those servers are in data centers with redundant connections.

Your provider receives the incoming call and tries to deliver it to your phones. It sends the call signaling to the IP address where your phones were last registered. That signaling gets no response, because your internet connection is down.

What happens next depends entirely on how your provider is configured:

Scenario 1: No failover configured

The provider tries to reach your phones, fails, and the caller hears ringing that goes unanswered, or the call goes to a generic voicemail box. If voicemail is not set up, the caller might get a "this number is not available" message or just endless ringing. This is the worst case and, unfortunately, the default for many small business VoIP setups.

Scenario 2: Voicemail catches the call

If voicemail is configured, the provider waits a few seconds for your phones to respond, then redirects the call to voicemail. The caller can leave a message, and you will get it (usually as an email notification or in the app) once your connection is restored or if you check from a mobile device. Better than nothing, but a customer calling with an urgent issue does not want to leave a message.

Scenario 3: Automatic failover to mobile

Many VoIP providers offer "find me / follow me" or simultaneous ring features. When your desk phone does not answer within a set number of rings, the system automatically forwards the call to your mobile phone over the regular cellular network. The caller may not even realize anything is wrong. They called your business number, it rang a couple extra times, and you answered.

Scenario 4: Cloud-based automatic rerouting

More sophisticated providers, particularly cloud PBX platforms, detect that your phones are unregistered and immediately reroute calls according to rules you have configured in advance. Calls might go to a different office location, to mobile phones, to an auto-attendant that gives callers options, or to a call queue staffed by remote workers on a different internet connection. This happens automatically, with no human intervention needed.

The difference between scenario 1 and scenario 4 is not technology. The technology exists in nearly every modern VoIP platform. The difference is whether someone took thirty minutes to configure it.

What you can still do during an outage

Your desk phones are down, but you probably still have options:

Mobile softphone apps. If your VoIP provider has a mobile app (most do now), and your phone has cellular data, you can make and receive calls on your business number from your mobile phone. You are going around the outage entirely, using the cellular network instead of your office internet to reach the VoIP provider. Your caller ID still shows your business number. The other party has no idea you are standing in a parking lot waiting for your ISP to fix things.

Wi-Fi calling from a neighbor or hotspot. If the outage is your office internet specifically, connecting a laptop or phone to a mobile hotspot or a nearby Wi-Fi network lets your softphone reconnect. Not ideal for an entire office, but it works for keeping one or two critical lines alive.

Forwarding at the provider level. Even without a mobile app, you can usually log into your VoIP provider's web portal (from your phone's cellular browser) and manually set up call forwarding to a mobile number. This is the manual version of the automatic failover described above.

Traditional cellular calls. If nothing else works, you have a phone in your pocket. You can make outbound calls from your personal mobile number. Not professional, but functional. Some VoIP providers offer a feature where outbound calls from your mobile can be routed through their system so that your business caller ID is displayed.

The outage everyone forgets: power

Internet outages get all the attention, but power outages are just as disruptive and more common. Here is what happens:

Your router and switches lose power. Even if your ISP's network is fine, your office network equipment needs electricity. No power to the router means no internet means no VoIP, same result as an internet outage.

PoE phones lose power too. Most desk phones are powered by Power over Ethernet from the network switch. When the switch loses power, the phones go dark entirely. No display, no nothing.

The ISP's equipment may fail too. If you have fiber, the ONT (the box where fiber enters your building) needs power. Many ISPs provide a small battery backup for the ONT, but those batteries typically last only a few hours. Cable modems and DSL modems also need power.

A UPS (uninterruptible power supply) on your router, switch, and ISP equipment gives you a buffer. A typical UPS can keep this gear running for 30 to 90 minutes, long enough to ride out most power blips and short enough to be affordable. For longer outages, you need either a generator or a cellular failover strategy.

How to set up your system so outages do not mean silence

This is the practical part. Here is what to configure, roughly in order of importance:

1. Configure call forwarding rules now, before you need them

Log into your VoIP provider's admin portal. Set up failover rules for every user and every ring group:

• If the desk phone does not answer in 15 seconds, ring the user's mobile phone.
• If the mobile does not answer in 15 seconds, go to voicemail.
• For main business numbers and ring groups, configure simultaneous ring to mobile phones so there is zero delay.

Do this today. Not when the outage happens. During an outage you may not have convenient access to the admin portal, and you will be too busy dealing with the immediate crisis to configure routing rules calmly.

2. Install your provider's mobile app

Every user who receives important calls should have the VoIP provider's mobile app installed on their phone, logged in, and tested. The app should be configured to use cellular data as a fallback when Wi-Fi is unavailable.

Test it. Turn off Wi-Fi on your phone and make a call through the app. If it works on cellular, you have a working backup. If you have never tested it, you do not have a backup. You have a hope.

3. Get a cellular failover device

For businesses where phone availability is critical, a cellular failover router is the gold standard. This is a device that sits alongside your primary router and contains a cellular SIM card. When it detects that your primary internet connection is down, it automatically activates the cellular connection and routes traffic through it.

Modern failover routers are smart. They can prioritize VoIP traffic on the cellular connection, ensuring that even if the cellular bandwidth is limited, voice calls get through. Some can even keep existing calls alive during the switchover if the failover happens fast enough.

The cost is the device itself (a few hundred dollars) plus a cellular data plan. For a business that loses revenue when phones are down, this pays for itself the first time it is needed.

4. Consider SD-WAN for multiple connections

If your business has two internet connections, say a primary fiber line and a backup cable connection, an SD-WAN solution can automatically route VoIP traffic over whichever connection is currently working best. If one goes down, traffic fails over to the other with no manual intervention and often no noticeable interruption.

SD-WAN is more common and more affordable than it used to be. Many business routers now include basic SD-WAN capabilities. For businesses with dedicated internet access as a primary line and a cheaper cable connection as backup, this provides robust redundancy.

5. Put critical network equipment on UPS

At minimum, put your router, your main network switch, and your ISP's equipment (modem, ONT) on a UPS. This keeps your phones alive during brief power interruptions, which account for a surprising number of "outages."

A $150 UPS that keeps your network stack running for 45 minutes eliminates the single most common cause of VoIP downtime for small businesses.

6. Set up monitoring and alerts

You should know about an outage before your customers tell you. Configure your VoIP provider's monitoring to alert you (via SMS to your mobile, not via email to your office computer) when phones go unregistered. Many providers offer this. If yours does not, a simple network monitoring tool that pings your office IP and texts you when it goes down serves the same purpose.

Knowing about the problem within minutes means you can activate manual failover procedures, notify staff to switch to mobile apps, and communicate proactively with customers rather than reactively.

The hidden advantage of hosted VoIP: nothing lives at your office

Here is something that gets lost in the "what if the internet goes down" conversation: with a hosted VoIP system, your actual phone system is not in your building.

With an on-premises PBX, traditional or IP-based, the brains of your phone system sits in a server closet in your office. If your building loses power, floods, catches fire, or simply has a bad router, the entire phone system goes down. The hardware that routes calls, stores voicemail, and manages your auto-attendant is physically present and physically vulnerable.

With hosted VoIP, none of that is in your building. The call routing logic, the voicemail system, the auto-attendant, the call queues, the recording infrastructure: all of it runs in your provider's data center. That data center has redundant power, redundant internet, redundant cooling, and redundant hardware. It is engineered to stay running when your office cannot.

Your desk phones are just endpoints. They are the equivalent of a monitor plugged into a remote computer. When your internet goes down, the monitor goes dark, but the computer is still running. The phone system is still live, still accepting incoming calls, still capable of routing them according to your rules. It just cannot reach the endpoints in your office.

This is the fundamental difference from on-premises systems and the reason hosted VoIP can actually be more resilient, not less. When your internet goes down:

• On-premises PBX: The phone system itself is unreachable. Incoming calls cannot be processed at all. No voicemail, no forwarding, no auto-attendant. The system is as dead as your internet connection.
• Hosted VoIP: The phone system is fully operational. It receives incoming calls, recognizes that your desk phones are unregistered, and executes whatever failover rules are configured. Forward to mobile, send to voicemail, route to another location, play a custom message. The intelligence is in the cloud, not in your building.

This also means recovery is fundamentally different. When your internet comes back after an on-premises PBX outage, you might need to reboot servers, wait for the PBX to restart, and hope that everything reinitializes correctly. With hosted VoIP, your phones simply re-register with the cloud platform and are immediately back online. There is nothing to reboot, nothing to recover. The phones reconnect and calls flow again.

The businesses most at risk during an internet outage are, counterintuitively, the ones with expensive on-premises IP-PBX systems. They have the same internet dependency as hosted VoIP but without the cloud-based failover safety net. Their phone system is both internet-dependent and locally vulnerable, the worst of both worlds.

What about the old phone system?

People sometimes argue that traditional phone lines were more reliable, and they are right. Copper phone lines carried their own power and worked during power outages. The public switched telephone network was engineered for five nines of reliability: 99.999% uptime, or about five minutes of downtime per year.

But that comparison misses context. Traditional phone systems had their own failure modes: PBX hardware failures, T1 line cuts, PRI card failures, analog line quality degradation. And when a traditional PBX failed, you needed a technician with specialized knowledge and possibly proprietary parts to fix it. Recovery could take hours or days.

A well-configured cloud VoIP system with cellular failover can match or exceed the practical reliability of a traditional phone system. The failure modes are different, not necessarily worse. And when something does fail, the recovery options are faster and more flexible. Forwarding calls to mobile phones takes seconds. Replacing a failed T1 card took a truck roll.

The key phrase is "well-configured." A VoIP system with no failover planning is genuinely less reliable than a traditional phone line. A VoIP system with proper failover planning is at least as reliable and far more flexible.

The real risk is not the technology

The biggest risk in VoIP reliability is not the technology. It is the gap between what the technology can do and what someone actually configured it to do.

Every major VoIP provider offers failover routing, mobile apps, and call forwarding rules. The features exist. But they require someone to set them up, test them, and maintain them. The businesses that experience total phone silence during an outage almost always have access to the tools that would have prevented it. They just never configured them.

This is not a technology problem. It is a planning problem. And it is completely solvable.

Spend thirty minutes this week. Set up your failover rules. Install the mobile app. Test a call over cellular. Run a VoIP quality test over both your primary connection and your failover to confirm each one can support voice traffic. Future you, standing in the office watching the router lights go dark, will be grateful.

For a complete picture of how VoIP calls work and where they can break down, see What Happens When You Press the Call Button. To understand the network factors that affect reliability, our Getting the Internet Right series covers everything from choosing an ISP to redundancy and failover planning.