The call came in mid-morning. The internet was down. Nobody could work.
That second part was the problem. Not just that the internet was out, but that everything in the business required it. Email, phone system, file storage, the project management tool, the CRM. All of it cloud-hosted. All of it unreachable.
What we found
The client was a twelve-person professional services firm that had moved aggressively to cloud tools over the previous few years. In most ways that was the right call. Cloud tools are easier to manage, accessible from anywhere, and do not require maintaining servers on premises.
What they had not planned for was the internet connection itself. Everything was in the cloud, which meant everything required connectivity. When their ISP went down for unscheduled maintenance with no advance notice, the business stopped completely.
The outage lasted about five hours. In that time, the team could not access files, send email, take calls, or reach any of the tools they used daily. A few people drove to a coffee shop. Most just waited.
The dependency that comes with going cloud-first
This pattern has become more common as businesses move to cloud-first setups. Moving to the cloud genuinely reduces a lot of complexity. You do not need a file server. You do not need to manage email infrastructure. Most software just works, accessible from any device with a connection.
What does not change is the need for a reliable internet connection. In some ways the dependency becomes more acute as you move more to the cloud, because there is no local fallback. If the connection goes down, access goes with it.
Most businesses have a single ISP connection. If that connection fails – due to a provider outage, a cut cable, router hardware failure, or any number of other causes – there is no backup. Work stops until the problem is fixed, and fixing it is entirely outside your control.
What redundancy looks like for a small business
Internet redundancy does not have to be complicated or expensive. The two common approaches are a second wired ISP connection from a different provider, or a cellular failover connection.
A second ISP connection uses a different provider on a different physical path. If the primary goes down, traffic automatically switches to the secondary. The second connection does not need to match the speed of the primary – it just needs to keep the business functional during an outage.
A cellular failover uses a router that connects through the 4G or 5G network when the wired connection is unavailable. The physical path is completely independent of the ISP that serves the building. Bandwidth is lower than a wired connection, but it is sufficient for most business tools: email, phone, and the browser-based apps most teams depend on.
The right setup depends on how many people are in the office, what tools they depend on, and how long an outage would need to last before it caused real financial damage. For some businesses, a few hours of downtime is an inconvenience. For others, it is significant.
What we set up
For this client, we added a cellular failover router configured to activate automatically when the primary connection goes down. The switch happens within a couple of minutes without anyone needing to do anything. The cellular connection is not fast enough for large file transfers, but it handles email, phone, and the business tools the team depends on most.
The setup cost was modest – hardware plus a monthly cellular plan – and it has already been useful more than once in the months since it went in.
The broader conversation this situation prompted was worth having separately: which tools and services does the business actually depend on, and what happens to each of them if connectivity is lost? That exercise is useful even if you never add a backup connection. Knowing your dependencies is the first step to managing them.
If any of this feels familiar, we can take a quick look at your setup and tell you what is actually worth fixing.