11/25/2025
Three Outages, Zero Excuses
AWS. Azure. Cloudflare.
Three outages in thirty days.
Three giants went dark, dragging down businesses like ours in the process.
Each of these companies can individually knock the web off its axis—and take your business with it.
Here’s how it hit us:
When AWS stumbled, our Frontend—deployed via Netlify, which runs on AWS—fell with it.
When Azure collapsed, our Backend—hosted on Azure—went down too.
When Cloudflare imploded, it cut off access to our EMR altogether, since we sit behind their security layer.
Every outage meant real-world disruption. Our customers couldn’t see patients. Couldn’t take notes. Couldn’t use Ambient Scribing. Front desks couldn’t send patients to the Populate Kiosk. Reminder calls didn’t go out, meaning late arrivals and lost revenue. Billers couldn’t submit claims—the lifeline of any private practice.
It would’ve been easy to shrug and say, “Not our outage, not our problem.”
But every minute down was a minute our customers were suffering. That was unacceptable.
So we went to work.
We rerouted our Frontend build system to DigitalOcean while Netlify dug itself out of the AWS crater.
We bypassed Azure Front Door and connected directly to our app servers before Azure even published what caused their outage.
We prepped a GoDaddy DNS fallback for Cloudflare—thankfully never needed, because GoDaddy’s propagation moves at glacial speed.
Was it messy? Yes.
Was it stressful? Absolutely.
Did we choose action over excuses? Every time.
We're proud we didn’t sit back when it was easy to justify inaction.
We're proud of our Engineering team for jumping into motion the moment the ground shook.
And, most of all, we're proud of our customers, who were patient and forgiving when they had every reason not to be.
