If your team lost access to email, phones, or a line-of-business app for a stretch this year, you were not alone and it was not your fault. 2026 has been a rough year for the handful of cloud providers most of the internet quietly depends on: a lengthy outage hit AWS's US-East-1 region in May, Microsoft Azure had a widely felt disruption in February and another in July, and Cloudflare logged a run of instability in August. None of those companies are careless. The outages happened anyway, and they will happen again.
For a small or mid-sized business, that is not really news about AWS or Cloudflare. It is news about you, because your phone system, your practice management software, your file storage, and your card processor are probably all sitting on top of the same small set of providers.
Why one company's bad day becomes your bad day
Most of the software you rely on is built on a handful of large cloud platforms, and a lot of those platforms concentrate traffic in a small number of regions. When one region has a bad afternoon, it doesn't just take down the provider's own site. It takes down every application built on top of it, which in practice means a single vendor's failure can silently knock out your email, your phones, your scheduling software, and your payment processor all at once, even though you never signed a contract with that vendor directly.
This is the part worth sitting with: you did not choose to depend on that specific data center. Your software vendor did, several layers removed from you, and you found out when the outage hit.
What it actually costs a business your size
Analysts throw around eye-watering downtime numbers for large enterprises, but the number that matters is your own. What does an hour without email cost you? What happens if you can't take a card payment for half a day? Can your team keep working with pen and paper, or does everything stop? Most businesses have never actually answered these questions, which means the first time anyone thinks about it is during the outage itself, which is the worst possible time to make decisions.
What to do about it this month
- List what you'd actually lose. Walk through a normal business day and note which tools, if they went dark for four hours, would stop you from serving a customer. That short list is your real priority, not a full inventory of every app you use.
- Ask your vendors where they run. Your practice management software, phone system, and payment processor probably each depend on one of a few big cloud providers. Knowing which one tells you whether an AWS outage and an Azure outage both hit you, or just one.
- Write down the manual fallback. For your top two or three tools, decide now how the business keeps functioning without them for a few hours: a paper appointment log, a backup phone number forwarded to a cell, an offline copy of critical records. Decide this on a calm Tuesday, not during the outage.
- Don't let identity be the single point of failure. If one login (say, your Microsoft 365 account) controls access to everything else, an outage or lockout there takes down more than it should. Make sure at least one person can reach critical systems another way.
- Ask your IT provider what their outage plan actually says. Not whether they have one, what it actually says happens in the first thirty minutes, and who calls you.
Takeaway for IT decision-makers
Assume your cloud provider will have another bad day, and build a plan for the four hours after it starts, not just hope that it won't happen to you.
You cannot prevent an AWS or Azure outage, and you shouldn't try to. What you can control is how long it takes your business to notice, adapt, and keep serving customers while the provider fixes its own problem. That is a business continuity conversation, not a technical one, and it is worth having before the next outage rather than during it.
Brotherly Technology helps small and mid-sized businesses across Northwest Georgia map their actual dependencies, plan for the outages they cannot prevent, and build backups that get tested rather than just installed. Talk to us about your setup if you have never actually mapped what a cloud outage would cost you.
Sources: public incident reports and coverage of the 2026 AWS US-East-1, Microsoft Azure, and Cloudflare outages. Not legal or insurance advice.