single point of failure: what businesses should know

single point of failure is an important part of keeping business technology practical, secure and reliable. This article explains the issue in plain language, with related context on business continuity and useful external guidance on business continuity.

Most IT decisions are not made during disasters. They are made on calm Tuesday mornings when everything is working fine. And that is exactly the problem. “We’ve never had a problem before.” It sounds logical. Sensible. Comforting. It is also one of the most expensive sentences a business can say. Because uptime history is not a strategy. It is a coincidence. Just because your internet has not gone down in two years does not mean it will not go down tomorrow. It means you have been lucky, or your provider has been competent, or no one has dug up the wrong trench yet. Luck is not architecture. Most real-world outages are not dramatic cyberattacks with hooded hackers typing aggressively in dark rooms. They are boring. A fibre line gets cut. A switch firmware crashes. A power surge trips a firewall. A cloud service has a regional hiccup. An ageing server finally decides it has done enough. None of those are cinematic. All of them stop business. The uncomfortable truth is that most small and mid-sized businesses are running with at least one hidden single point of failure. Often more. One internet line. One firewall. One server. One domain controller. One person who “knows how it all works.” And because nothing has broken yet, it feels safe. It is not safe. It is untested. There is a difference. When we talk about redundancy, people often hear “overspending.” They imagine duplicate everything and enterprise-level budgets. That is not what this is about. Redundancy is not paranoia. It is accepting that things fail. If your business cannot operate without internet, why is there only one connection? If your core systems run on a single device, what is the recovery plan when that device fails at 14:17 on a Wednesday? If your authentication relies on one server, what happens when it does not boot? These are not dramatic questions. They are operational questions. The irony is that the businesses who say “we’ve never had a problem before” are usually the ones most shocked when they finally do. Because when everything is built on a single thread, the first break is not an inconvenience. It is an interruption. Redundancy does not mean gold-plating your environment. It means identifying what would genuinely hurt if it stopped, and ensuring there is a second path. A second internet line. Failover hardware. Redundant power where it matters. Properly replicated systems. Not everywhere. Only where it counts. The goal is not zero failure. That is fantasy. The goal is graceful failure. When something breaks, the business keeps moving. That is the difference between “we’ve never had a problem” and “we’re prepared when we do.” The first is hope. The second is design. And in IT, hope has a terrible track record. If you are reading this and quietly realising your entire operation runs on one fibre line and a prayer, it might be time to rethink that. Need a UPS or inverter so load shedding does not take your firewall with it? Need a backup internet connection so one trench does not shut down your day? Not sure where your single points of failure are hiding? Let’s talk.