Comparing live pricing and terms from 400+ carriers and platforms
A fiber cut, a data center failure, a hosting outage - unrelated events, six weeks apart, taught Ohio businesses the same lesson: concentration risk, not bad luck.
On May 5, a contractor cut a fiber line in western Pennsylvania. Within the hour, Verizon customers across the eastern third of the country were down - Mahoning Valley, New York, Atlanta, New Orleans, parts of Florida. Field-service apps stopped syncing. Calls dropped outright. Full restoration took nearly seven hours.
Carriers use the word redundancy in every proposal and every SLA. What they often don't say is that redundant routes frequently share the same physical conduit and the same long-haul corridors. A single shovel can take down what was sold as three separate paths, because two of them ran through the same trench. The logical topology in the portal looks fine. The physical reality is that almost nobody on the carrier side verifies true diversity end to end.
The fix starts with asking your carrier, in writing, for the entrance facility and long-haul corridor each circuit actually travels. If they can't answer, that's your answer.
Three days later, on May 8, the air conditioning failed in an AWS data center in Northern Virginia. Servers shut themselves down to keep from overheating. Coinbase went offline for more than five hours. FanDuel went dark mid-trading. Thousands of smaller Midwest businesses that didn't know they depended on US-EAST-1 found their scheduling platforms, payroll, time clocks, CRMs, and cloud point-of-sale stumbling at once.
Ohio should pay attention here. The state is now the third-largest data center market in the country, and the same concentration that took down US-EAST-1 is being built into the grid around Columbus right now. For a multi-location business, the real question is no longer whether the cloud is reliable. It's whether you know which buildings your business actually runs out of, and what happens at your sites when one of those buildings fails.
While outages made headlines, a slower deadline kept advancing. AT&T is shutting down copper wire centers starting in June 2026, about 500 in the first wave, with Ohio on the list. By November 15, a lot of POTS lines 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 decent chance it still rides analog copper. When that line goes dark, the panel can't reach the monitoring center, and moving it to VoIP is not automatic - most fire panels won't pass UL864 over a standard SIP trunk, and the local authority having jurisdiction has to sign off too.
Businesses that called their carrier in March were quoted June install dates. Businesses that waited until April are now looking at September, past the cutoff. Lead times for replacement hardware have stretched to twelve weeks.
Meta signed a $6 billion fiber deal with Corning, and the fiber supply chain shifted overnight. Small Ohio ISPs that won BEAD awards had fiber orders canceled after Corning stopped selling them glass. Loose tube fiber, the kind rural fiber-to-the-home needs, now has a 52-week lead time. Ribbon fiber is over 60. Smaller providers report cost increases of 70 to 80 percent.
If you operate in rural Ohio - manufacturers in Wayne County, healthcare networks in the southeast, distribution out of Findlay or Mansfield - that supply squeeze hits directly. Buildouts slip a year. ISP partners walk away when the economics no longer work. The honest answer right now is fixed wireless, hybrid topologies, microtrenching, and leased dark fiber from cooperatives that planned ahead - not a build date nobody can hit.
The second category of concentration risk looks like a project plan, not a fiber cut. A twelve-week cloud phone cutover across a few sites turns into month seven. Porting dates slip. E911 records carry addresses that haven't been accurate in years, so a 911 call from a back warehouse gets routed to the wrong dispatcher. Nobody tested the handsets on the real network under real traffic until cutover day. The platforms work fine when someone who knows what they're doing runs the project - the failure is a single national provider running a shared queue of project managers across dozens of accounts, none of whom has seen your network.
The same pattern shows up in hosting. In January, a Columbus hosting provider went dark for 76 minutes and took several unrelated downstream companies down with it. When you sign with a large carrier or national MSP, you're really signing with a chain: an ISP, a hosting platform, hardware suppliers, cloud platforms - any one of which can take you down without warning. The question worth asking isn't how big your provider is. It's whether there's one number to call when something breaks, and whether the person who answers has the authority to fix it.
Pull bills for every site. Flag every line under $50 a month, identify what it actually powers - fire panel, elevator, security panel, fax, alarm - and put a replacement on the calendar with a code-compliant solution and a real install date.
Ask your primary carrier, in writing, for the physical path of your primary and backup circuits. If the answer is 'we'll get back to you,' start shopping for a true secondary on different infrastructure.
List every SaaS tool the business depends on and the cloud region it runs in. For each must-keep-working application, decide whether multi-region failover or a local fallback is the right answer, and budget for it.
Who is the carrier? Who is the hosting provider? Who is the hardware supplier? Who do you call at 2 a.m.? If any answer is 'I'm not sure,' fix that this quarter.
A free telecom and IT cost and risk audit shows where you're concentrated, overpaying, or exposed - no obligation.