On October 22, one of Ohio's largest hospital systems detected unusual activity on its servers and made a decision most organizations never get around to making: it disconnected itself from the internet. University Hospitals, a 21-hospital system headquartered in Cleveland, pulled its websites and its patient portal, MyChart, offline while it investigated.
Patients noticed right away. Test results, messages to doctors, prescription renewals, appointment scheduling, bill pay: all of it behind a login screen that would not open. For many patients in northeast Ohio, that portal is how they reach the hospital system at all. It stayed dark through the first week of November and came back only on November 7. That is sixteen days with the front door closed.
Here is what makes the story worth a business owner's time. In those sixteen days, the hospitals, emergency departments, and physician offices stayed open, and the system says most appointments and procedures continued. Damage was real, but it landed where the work could limp instead of where the care happens.
What happened, and what did not
The health system says it detected unusual activity on October 22 and activated its response protocols, then disconnected its systems from the internet as a precaution while it investigated. That kind of quick disconnection is aggressive: it takes services customers depend on off the market immediately. It also stops a problem from spreading deeper into the network. University Hospitals has not said what kind of activity it detected.
Two weeks in, the system still had no estimate for when its digital services would return. The HIPAA Journal reported on November 4 that while the hospitals and clinics stayed open, the outage had slowed work like insurance pre-authorizations and some appointments. A proposed class action filed in federal court alleges patient information was compromised and that the system's safeguards were inadequate. Those are allegations at this stage; University Hospitals has not confirmed that any patient data was accessed.
Why care never stopped
Cleveland's public media outlet, Ideastream, reported on November 6 that doctors and staffers kept working through the outage in ways that would sound familiar to anyone who has run a business by hand: virtual visits moved to the phone, video, or an exam room; prescriptions got called into pharmacies or written on paper; lab results and appointment reminders went out as phone calls instead of app notifications. The system's internal record network, the one its own clinicians use, stayed up.
Healthcare is one of the few industries that treats downtime as a scheduled event. Hospitals keep manual fallback routines on the shelf because regulators and plain reality demand them, and staff practice them while the computers are still healthy. When the portal died, nobody had to invent a workaround on day three.
Sixteen days is normal now
A business owner looking at this story should set aside the question of how it happened. The useful question is how long.
A professor who studies this field put a number on it. Cory Scott of Cleveland State University's College of Law pointed to a study of ransomware attacks on American hospitals and health systems, which found recovery takes sixteen and a half days on average. His comment on the University Hospitals timeline, in Ideastream's November 6 report: this is not, unfortunately, an unusual amount of time yet.
Sit with that. A system with 21 hospitals, thousands of employees, and the money to hire outside help took more than two weeks to bring back one website and a portal. The planning assumption for a smaller operation should be somewhere between a bad day and a bad month. Nobody budgets for an afternoon.
The list you write before the outage
The transferable part of this story is not the attack. It is that the organization kept functioning while its front door was shut, because the fallbacks existed before the morning they were needed. Around here, plenty of clinics and small practices run a great deal thinner than a 21-hospital system. The same logic applies doubly to any small business that serves customers through a login, an app, or a booking site.
The exercise is short enough to do over a lunch hour, and it is most valuable done while systems are healthy:
Name what you would lose. Walk through the systems you touch daily and mark which ones the business can survive without, and for how long. A week without your website is a problem. A week without the thing that holds your customer list is a different kind of problem.
Write the by-hand version. For each critical system, sketch the manual fallback: who calls whom, what gets written on paper, where the paper lives afterward so it can be typed back in. If the answer is "we would figure it out," that is the finding.
Decide the disconnection question in advance. University Hospitals chose speed: cut everything off, sort it out, bring it back carefully. That call is easier in advance, when you know which systems have to keep running and which you would rather take offline than risk.
Plan for the second wave. Cleveland television stations were warning patients to watch out for scams while the restoration unfolded. Outages and breaches attract impersonators, and the people trying to exploit the confusion are counting on you being too busy to notice. Your customers' filter should be set before any incident, not during.
The Bottom Line
A 21-hospital system spent sixteen days without its public digital services and came out of it with every hospital still treating patients, because the manual versions of its work already existed on paper and in habit. The systems you rely on will fail eventually, and the recovery clock will run in days, not hours. The difference between an outage and a disaster is the plan that was written before the morning somebody needed it. If nobody has written yours, now is the inexpensive time to have that conversation with someone who does this for a living.
Story reporting: University Hospitals statements of October 22 and November 5; The HIPAA Journal, November 4, 2026; Ideastream Public Media, November 6, 2026; News 5 Cleveland, WKYC, and Cleveland 19, November 7, 2026.