A couple of weeks ago, YouTube went down for a few hours. Over 240,000 users in the US hit Downdetector to confirm they were not alone in their suffering. For a brief, beautiful moment, the internet collectively remembered that it has no idea how to do anything without a tutorial video.
It came back up. Everyone went back to what they were doing. Lesson not learned.
I get it. YouTube being down is a minor inconvenience for most people, and I am not here to catastrophize a few hours of buffering frustration. However, there is a useful conversation buried inside that outage, and since we are all apparently still here and operational, now seems like a good time to have it.
When “Down” Becomes an Actual Problem
Here is the question I ask clients before something goes wrong, which is the only useful time to ask it: What would actually stop your business if it went offline today?
Maybe not YouTube. But let’s work through the real list.
Your email. If Microsoft 365 or Google Workspace has an outage, and both have had them, what happens to your team for the next four hours? Do you have a backup communication method, or does everyone sit and wait?
Your practice management or billing software. For accounting and law firms, especially, these are the operational spine of the business. If your cloud-based platform goes down on a filing deadline day, what is your plan? If the answer is “we would figure it out,” that is not a plan.
Your VoIP phone system. Most modern phone setups run over the internet. No internet, no phones. If a client is trying to reach you during a crisis and your phones are tied to the same connection that is down, you have compounded the problem.
Your client portal. If your clients cannot access shared documents or submit information through your portal, and that is how you have set up your workflow, a platform outage becomes your problem even when the fault is entirely upstream.
The Thing Nobody Talks About Until It Is Too Late
There is a concept in IT called a single point of failure. It means any component in a system that, if it fails, takes everything else with it. Good business continuity planning means identifying chokepoints and either building redundancy around them or making a deliberate, eyes-open decision to accept the risk.
The problem is that most businesses have never done that exercise. They built workflows around tools that worked, and never asked what would happen when those tools stopped working. Which they will. If there is anything technology is reliably good at, it is failing at the absolute worst possible time.
I am not saying you need a redundant system for everything. That would be expensive and largely unnecessary. I am saying you should be able to answer the question: if this goes down for four hours on a Tuesday, what do we do? For some tools, the answer is “nothing critical, we wait.” For others, the answer should never be “we have not thought about it.”
A Starting Point That Does Not Require a Consultant
You can do this yourself in an afternoon.
List the five tools your business genuinely cannot operate without. Not the ones that would be annoying to lose. The ones that would actually stop work.
For each one, look up the vendor’s status page. Every major platform has one. Bookmark them. This is where you check during an outage instead of refreshing your own screen for twenty minutes.
Then ask, for each tool: if this were unavailable for four hours on a deadline day, what would we do? If you do not have an answer, that is the gap. It does not have to be a complex solution. Sometimes the answer is a shared cell phone number and clear instructions for staff on how to communicate.
Test your backup communication method before you need it. If your email goes down, does your team know how to reach each other? Do they have each other’s phone numbers? Does anyone know where the physical contact list is, if one exists?
The Real Lesson from YouTube Being Down
The reason the YouTube outage got attention is that it hit something people use constantly and rely on emotionally, not operationally. The outages that actually cost businesses money are quieter, less covered, and affect platforms most people outside your industry have never heard of.
Microsoft had a significant outage in January 2025 that affected Teams and Outlook. The coverage was minimal compared to the YouTube story. The operational impact for businesses that rely on those tools daily was considerably worse.
The platforms you depend on to run your business will go down at some point. Planning for that is not paranoia. It is the same logic as keeping a spare tire in your trunk. You are not expecting to use it. You do not want to find out you need one when you are already on the side of the road.
If you would like help mapping out your firm’s actual operational dependencies, that is a conversation worth having before the next outage, not after.
Quick and Easy: YouTube’s February outage was mostly harmless, but it is a useful reminder that every platform your business depends on will go down eventually. The consequential ones are not the entertainment platforms. Taking an afternoon to map your five most critical tools and ask “what do we do if this is unavailable?” is more valuable than any uptime guarantee a vendor has ever offered you.
I can’t tie a knot that would safely secure a boat, nor can I carve a race-winning pinewood racer, but I’m pretty sure my time as a Boy Scout primed me for a career in technology. Their motto, “be prepared” made a deep and lasting impression on me, and I try to exemplify that attitude in how I conduct my business, and encourage my clients to do the same. This can take all forms – planning for the safety and security of your loved ones is something everyone should take very seriously – but many businesses are less than ideally prepared for adverse events. Though most folks think in terms of actual disasters – fires, floods, earthquakes and so on (welcome to Southern California!) – you should also consider smaller-scale catastrophes such as data loss, security breaches, employee malfeasance, theft, vandalism, and virus infections. Every business should have a Disaster Recovery and Business Continuity Plan, and if that business or organization relies on technology, those plans should include technology recovery and continuity as well. Don’t have a plan? Here are five important items to get you started on writing one:
- Back up your data – most folks have learned the hard lesson of data loss and at a minimum try to back up their most important data to a separate drive. But if that backup is stored on premise, it is just as susceptible to whatever might damage your source data. At minimum, a copy of your backups should be stored offsite in a secure location, and the best solution is a combination of cloud-based backups and regular rotation of local backups to an offsite location.
- Keep track of critical logins and passwords – most organizations that can’t afford to maintain a full-time IT person on staff often suffer from a blind spot in their operation manuals and documentation: logins and passwords for important technology services, as well as contact numbers or email addresses for critical vendor services. Keeping these small bits of information current and stored offsite can mean the difference between hours and days in recovering from a disastrous event.
- Identify your technology weak spots – if your business relies on physical technology to conduct business, consider how hard it would be to operate without that technology for days, or even weeks. Email or web server on premise? Payroll checks printed on special printers? Even if you don’t use any specialized hardware, can your business operate without internet or electricity? Identifying these potential vulnerabilities will go a long way to helping you minimize or eliminate them before they can cripple your business during adverse circumstances.
- Evaluate vendor preparedness – if you rely on service providers for crucial technology services, you should have at least a basic understanding of how prepared they are for disasters. Though you have less to worry about with large, experienced providers (even Gmail goes down from time to time), if one of your “weak spots” is a service provided by someone else, you should know if they are prepared to handle a disaster, and how the loss of this service would affect your own operations.
- Train your people – if you or someone in a leadership position is incapacitated or isolated from the organization, others need to be prepared to fill those shoes. This means training them or at least preparing documentation for them on all of the above. Nothing is worse than watching an organization flounder while everyone stands around staring at each other not knowing what to do.
These are only a few aspects of a well-formed DR/BC Plan. The larger the business, the more detailed and complex it will become, but every organization large or small, should have one. It may seem expensive or a waste of time, but putting the effort into a DR/BCP will be the difference between your organization overcoming a challenge or succumbing to a disaster. Be prepared!
Image courtesy of winnond at FreeDigitalPhotos.net
Normally, New Jersey and Manhattan datacenters don’t have to worry about floods, but Hurricane Sandy quickly overwhelmed many major providers like Internap and Peer 1 who provide service across the country. While most of their electronics were relatively safe from the torrential rains and high winds, water will – given time and opportunity – get into everything, and thousands of buildings in the area experienced severe flooding in basements and even ground-floor spaces. “Surely they don’t keep their electronics down in the basement!” I can hear you exclaim, and they don’t, but what is down there are generators and fuel pumps for those generators, because that’s where most buildings put their big, noisy mechanical equipment. Power outages don’t stop big datacenters – they’re designed to last for hours, even days without power – but those generators need fuel and air. When they are under 5 feet of water, both are going to be in short supply.
What this means for you:
When doing your disaster preparedness and continuity planning (you do have a DR/BC Plan, right?) you need to assess all vendors that provide services you would consider critical to your core business processes, particularly the ones that service your customers, such as website or application hosts, or even your own employees such as outsourced payroll services. If you are using providers that have weak, or even incomplete DR/BC plans of their own, you may want to change providers, or, at minimum, compartmentalize your own business processes so that your company isn’t completely crippled by a weak point in your service supply chain.
Image courtesy of “winnond” / FreeDigitalPhotos.net