Outages, botched UCaaS cutovers, and the AT&T copper sunset are all hitting Ohio businesses at once in 2026. Here's what they have in common — and what to do about it.
By Jonathan Eubanks · May 8, 2026 · 10 min read
This past week alone, three different telecom problems have walked into my office wearing three different costumes. A property manager in Westerville whose fire alarm vendor told her the panel "should be fine" through the AT&T copper cutover. A manufacturer in Hilliard whose four-month-old UCaaS migration is still dropping calls at the loading dock. A medical group in the Dayton area whose hosted phone system went silent for ninety minutes on a Tuesday afternoon because somebody else's data center had a bad day.
Three different industries. Three different vendors that don't know each other's names. And every time, the executive on the other side of my desk has the same look — the look of someone who thought they had bought "managed" service from a "national provider," and just figured out what those words actually mean in 2026.
Let me explain what these three storms have in common, because if you operate a multi-site business in Ohio, one of them is already in your driveway. You may just not have looked outside yet.
When you sign a contract with a national carrier, you're not really signing with one company. You're signing with a chain of them. Your "managed" service rides on top of an ISP, which rides on top of a hosting platform, which rides on top of hardware suppliers, fiber providers, and cloud platforms — any one of which can take you down without warning. You don't see the chain on the invoice. The invoice just says "Service Bundle — Tier 3." But every link is a single point of failure that nobody told you about.
The chain is also why the customer-service experience feels so broken. The big carriers have hundreds of thousands of accounts and a help desk built like a queue. When their vendor's vendor has a bad night, your ticket lands in a stack with ten thousand others and gets worked by somebody who has never seen your network, doesn't know your sites, and doesn't have authority to credit your account if they cause downtime. That isn't a failure of any individual rep. It's how the system was designed.
Now layer the three things hitting Ohio simultaneously this spring on top of that vendor stack, and you start to see why the phone is ringing.
The week of April 20 to 26, the U.S. logged 170 network outage events — a 19 percent jump from the week before. Verizon Business hit customers across multiple regions in a single afternoon on April 22. In January, a hosting provider with nodes here in Columbus went dark for 76 minutes — and downstream partners, companies that had nothing to do with the original outage, went down with it. Their customers couldn't reach their data, their phones didn't ring through, and their internal IT teams took the heat for breakage they didn't cause.
The squirrel that took out phone and internet for Medina County government back in February is the comic-relief version of the same story. We laugh because it's a squirrel. We should not be laughing about the fact that a critical-services line was that exposed in the first place.
Here's the test that matters when you think about your own setup: if your service goes down at 2 p.m. on a Tuesday, do you have one number you can call where the person who answers has the authority to do something about it? With most national-carrier accounts, the honest answer is no. You have a portal. You have a ticket queue. You have a rotating account team. What you don't have is a person with a name and a desk who is going to stay on the phone until your business is back up.
Three sites. 240 phones. A "twelve-week" cutover that's now in month seven. I keep hearing some version of that story all spring from operations leaders across the Midwest. The names of the providers change. The failures don't.
Here's what actually happens on a botched UCaaS migration. Number-porting dates slip — because the losing carrier has every incentive to stall, and nobody at the new provider is paid to fight that battle on your behalf. E911 records show up at the new platform with addresses that haven't been right since 2019, so when somebody dials 911 from the back of the warehouse, the dispatcher gets sent to the corporate front desk three miles away. The "complete feature parity" promised in the sales deck turns out to mean parity with somebody else's PBX. And nobody — nobody — tested the physical handsets on the actual network at the actual sites under actual call volume until cutover day.
Then the old PBX gets turned off. And the wheels come off.
The hidden costs are the part that makes a CFO's eye twitch. Professional services billed hourly because the original scope was wrong. Emergency network upgrades because the existing internet circuits can't carry the voice load. A new round of QoS work because nobody mapped jitter and latency before signing the contract. I've watched $25,000 quotes turn into $90,000 invoices, and the phones still drop calls at the loading dock. The industry data backs this up: more than 40 percent of cloud-communication migrations underperform in 2026, and organizations that skip a proper pre-cutover assessment see project timelines extend by 40 to 60 percent.
This is not a technology problem. RingCentral works. 8x8 works. Webex, Teams Phone, and Zoom Phone all work — when somebody who knows what they're doing runs the cutover. What you're really buying when you sign with a national provider is a queue: a shared project manager rotating through forty accounts, a sales engineer who hands you off to deployment, who hands you off to support, who has never seen your network. The post-go-live "managed service" is a portal and a ticket system.
Quick win: Pull the last 90 days of every telecom invoice and highlight every recurring line item under $50 a month. That short list is your hidden POTS, fax, alarm, and analog-circuit exposure — and it's the population the AT&T copper sunset is going to silence first.
Most building owners I talk to in Ohio still don't realize this is happening. AT&T begins decommissioning copper facilities in roughly 500 wire centers nationwide starting in June 2026 — about ten percent of its footprint in the first wave. Ohio is on the list. Under the FCC's revised rules, the carrier only has to give 90 days of advance notice before service stops at a specific location. By mid-November, a lot of those POTS lines simply stop working.
If your building has a fire alarm panel, an elevator emergency phone, or a security panel that calls a monitoring station — there's a real chance one of those is still riding analog copper. The fancy fire suppression system you spent six figures on talks to the central station through a $40-a-month phone line that's about to disappear. When that line goes dark, the digital alarm communicator transmitter in your fire panel can't reach the monitoring center. Your next inspection fails. Your insurance carrier finds out. Your tenants find out. And you find out that "we'll just move it to VoIP" doesn't actually work — most fire panels won't pass UL 864 over a standard SIP trunk, and the authority having jurisdiction in your city won't sign off either.
Here's the part that's making my phone ring this spring: businesses that called their existing carrier in March were quoted June install dates for replacement equipment. The ones who waited until April are looking at September — past the cutoff. The dedicated POTS-replacement vendors are booked. Hardware lead times for cellular failover units stretched to twelve weeks somewhere around Easter and they haven't come back down.
The decommission notices are sent by U.S. mail to the billing address on file. Most of those notices are sitting in an admin's inbox right now, unopened, while the clock runs.
Stand back from those three storms and the common pattern jumps out. In each case, the customer ends up acting as the integrator without knowing they signed up for the job. The carrier sells the service. The hosting platform runs the back end. The hardware vendor ships the boxes. The local installer racks them. The monitoring company watches the alarms. The fiber provider runs the line. And when something breaks — or fails to ship, or doesn't pass inspection, or gets ported wrong — every one of those vendors points at the other ones.
"Managed" service in 2026 has quietly been redefined. It used to mean "we own the outcome." It now mostly means "you have access to a portal where you can open a ticket about the outcome." That's a meaningful demotion, and it's the reason your IT director is exhausted, your CFO is angry, and your facilities manager is screaming into voicemail.
The fix is not bigger. It's shorter. The chain has to be shorter. The relationships have to be real. And one human being needs to own the outcome from quote to cutover to the night the squirrel chews through the line.
I'll tell you what we do at Buckeye, not because it's the only way, but because it's how the work actually gets done. We walk every site before we quote anything. We pull every invoice and read every line, including the ones the customer's been paying for years without questioning. We test the handsets on the actual network before the porting window opens. We map the analog circuits — the fire panels, the elevator phones, the alarm boxes, the modems on top of vending machines — and we tell you which ones are at risk, by name, with the wire-center data, before the carrier mails you a notice. And on the night of a cutover, somebody with a name is at every site or on a bridge, with the authority to call audibles when reality doesn't match the project plan.
That's not a heroic posture. That's just the work. The reason the national carriers don't do it is that it doesn't scale to a million accounts — and you and your business are not a million accounts. You're one business that needs to be up.
If you do nothing else after reading this, do these four things over the next ninety days. First, pull every telecom invoice from the last quarter and circle every recurring line item under $50 — that's your hidden analog and POTS exposure, and it's the population that the copper sunset is going to silence first. Second, walk every site and physically identify every fire panel, elevator phone, alarm dialer, and security panel — write down the phone number printed on each one. That list is your replacement-project scope. Third, look at your contract expiration dates for every voice and data service. Anything renewing in the next twelve months should be in a competitive-bid window, not on auto-renew. Fourth — and this is the one most organizations skip — walk into the next conversation with your provider and ask, in plain English: "Who at your company has the authority to credit my account if your service causes my business to go down?" The answer to that question tells you whether you have a partner or a portal.
Bottom line: The three storms aren't separate problems. They're three different bills coming due at the same time for the same underlying decision — the decision to buy "service" from a vendor stack where nobody owns the outcome. Outages will keep happening. Cutovers will keep going sideways. Copper will keep going dark on schedule. The choice you actually have is whether the person on the other end of your phone, the night something breaks, can fix it.
Get a Free Telecom Assessment from Buckeye Telecom → Serving Columbus, Ohio? Buckeye Telecom is headquartered at 1 Miranova Pl in downtown Columbus. Learn more about our Business Telecom Services Columbus Ohio — local support, no 800 numbers, one number that rings a person who can fix it. ← 7 Ways Ohio Businesses Overpay for TelecomOhio Telecom Buyer's Guide 2026 → ← Back to All Articles
Jonathan founded Buckeye Telecom in 2003 after years in the Columbus telecom industry — first at 5-Star distributors learning the carrier side, then carrying his own quota in telecom sales. He still works directly with clients — backed by the Buckeye team.
Talk to the Buckeye team — the owner is involved in every engagement, and there’s no advisory fee.
Prefer to talk now? Call or text 614-224-2003.