A Quiet Hurricane Season Is Not a Continuity Plan: Keeping Phones and Internet Up When the Power Isn't
Here's an easy mistake to make in August: reading a calm forecast and quietly moving continuity planning to next quarter.
NOAA's updated outlook, issued August 6, gives a 75% chance of a below-normal 2026 Atlantic hurricane season, with 7 to 13 named storms and 2 to 6 hurricanes expected, driven by a strong El Niño suppressing development (NOAA Climate Prediction Center). Colorado State's final outlook agrees, putting the odds of a Category 3 or stronger U.S. landfall at just 16%.
That's genuinely good news. It's also not a plan.
Two things are worth remembering. First, most of the season's activity still falls in August through October, and the basin has already produced named storms as recently as this week (National Hurricane Center). Second, and more to the point for most of our customers: the outages that actually take Long Island and NYC businesses offline are rarely named storms at all. They're a nor'easter, a summer thunderstorm that drops a limb on a pole, a contractor's backhoe finding a fiber run, a transformer failure, or a carrier problem three towns over that has nothing to do with your building.
You don't get a forecast for those. So the question isn't whether a hurricane is coming — it's what happens to your phones, your internet, your card processing, and your cameras the next time the power or the circuit drops for four hours on a Tuesday.
What Actually Fails, In Order
When people say "we lost internet," what usually happened is a chain reaction. Understanding the chain is how you figure out where to spend.
Power goes first. Even a brief outage takes down your switch, your router, your access points, and your ISP's equipment. Desk phones drawing PoE from the switch go dark instantly. If your network gear isn't on battery, nothing downstream matters.
The circuit goes second. A cut line or a carrier fault takes your primary internet down while the power stays on. Everything is powered and nothing works, which is somehow more frustrating.
Then the dependencies surface. Cloud VoIP stops registering. Card terminals can't reach the processor. Cloud cameras stop uploading. Door access controllers may keep working locally but lose remote management and alerts. The alarm panel might be fine or might be silently offline, depending on how it communicates.
Finally, the human workaround kicks in — staff start using personal cell phones, customers can't reach you at your published number, callbacks come from unknown numbers, and nothing gets logged. That's the part that costs you money and reputation, and it's entirely avoidable.
The Good News About Cloud Phone Systems
If you're on hosted VoIP or UCaaS, you're already in a better position than a business with an on-premise PBX in a closet. Your call processing lives in a data center, not in your building. When your office goes dark, the platform is still up and still receiving your calls — the only question is where it sends them.
That means the most valuable continuity work is configuration, not hardware, and it costs nothing:
· Failover call routing. Set rules so that if desk phones stop registering, inbound calls automatically roll to mobile numbers, a secondary location, an answering service, or voicemail-to-email. Most platforms support this natively and most businesses have never configured it.
· Softphone and mobile app readiness. Every employee who takes customer calls should have the mobile app installed, logged in, and tested before they need it — not downloaded during an outage. Calls then still show your business number.
· Emergency greetings ready to go. Pre-record a "we're experiencing a service interruption" greeting and know how to activate it in under two minutes from a phone.
· Current 911 location records. If staff are working from home or a backup site, emergency calls need to reach the right dispatcher. This is worth verifying annually regardless.
Configuration-only changes are the highest-return continuity work available to most businesses. If you do nothing else from this article, do these four.
Where Hardware Actually Helps
Once routing is handled, two hardware investments do most of the remaining work.
Battery backup on the right gear. A UPS on the network rack — modem/ONT, router, primary switch — buys you through the brief outages that make up the majority of interruptions, and gives you a clean shutdown on longer ones. Size it for runtime, not just capacity, and add PoE injectors or a small UPS for critical access points and the phones at the front desk and any 24/7 station. Test it by pulling the plug once a year; batteries die quietly.
Cellular failover. A dual-WAN router with a 4G/5G backup path monitors your primary circuit and reroutes traffic automatically when it fails, typically switching within 15 to 30 seconds so desk phones keep ringing rather than calls being forwarded off-system. Industry pricing generally puts LTE/5G failover in the $50 to $150 per month range, a second physical ISP at $100 to $400, and SD-WAN — which runs both links simultaneously and is worth considering for multi-site businesses or chronic call-quality issues — at $200 to $500.
One detail that trips people up: a "second internet line" that shares the same conduit or pole route as your primary is not redundancy. It fails at the same moment for the same reason. Diversity of physical path is the whole point, which is often why cellular is the better backup even when a second wired circuit is available.
A One-Afternoon Continuity Check
You can complete this in a single afternoon, and it's worth documenting the results.
1. Identify what must keep working. Be honest and short. For most businesses it's: inbound phone, card processing, one or two cloud applications, and cameras. Not everything is critical, and pretending otherwise makes the plan too expensive to execute.
2. Check what's on battery today. Open the network closet. Note which devices are plugged into a UPS and how old that UPS is. Anything older than four years is a coin flip.
3. Pull the plug on your primary circuit. Deliberately, during a slow hour. Time how long until phones stop working, whether anything fails over, and what your staff actually does. This ten-minute test tells you more than any assessment.
4. Write the one-page runbook. Who calls the carrier, who activates the emergency greeting, who tells staff to switch to mobile apps, where the account numbers are, and what your published outage message says. Print it. A runbook that lives only in the cloud is unavailable exactly when you need it.
5. Confirm the outside vendors. Your alarm monitoring, elevator, and camera vendors each have assumptions about connectivity. Ask each one directly what happens to their system when your internet drops. The answers are sometimes surprising.
6. Note your callback path. If customers can't reach you for two hours, how do they know you're aware? A pre-written text or email template plus a website banner is enough, and takes ten minutes to prepare now versus an hour of improvising later.
The Long Island Reality
A few local factors make this more than theoretical here. Overhead distribution lines and mature tree canopy across Nassau and Suffolk mean wind events cause outages well below hurricane strength. Older commercial buildings often have a single service entrance and no practical second path. Coastal and low-lying commercial corridors add flood exposure to ground-floor equipment rooms — if your rack sits in a basement, elevating it is cheap insurance. And in multi-tenant buildings, your continuity depends partly on a landlord's equipment you don't control, which is worth confirming rather than assuming.
None of this requires an enterprise budget. For most small and mid-sized businesses, the meaningful version of this plan is a properly configured phone system, a UPS that actually works, a cellular failover path, and a one-page runbook. That's a modest recurring cost against the alternative of a day where nobody can reach you.
If You'd Rather Not Test This the Hard Way
PBXGlobal designs, installs, and supports the whole chain — cloud VoIP and UCaaS, network and cabling, failover connectivity, cameras, and door access — for businesses across Long Island and New York. That breadth is useful here specifically because continuity problems don't respect vendor boundaries.
We're happy to walk your setup with you, check your failover routing and battery backup, run the plug-pull test properly, and leave you with a written continuity plan you own. No obligation, and it's a good use of a quiet stretch in the season.
Reach out at info@pbxstore.com or +1 (877) 702-2077 to schedule a Business Continuity Review for your phones, network, and security systems.
Business Continuity, VoIP, Network Infrastructure, Tri-State Business
Comments