The Week Every Website Became Critical Infrastructure

There was no playbook for the second week of March, and this post will not pretend one existed. So let it be what it can honestly be: a field report from inside the ten days when the websites we build stopped being channels. Without ceremony or warning, they became primary infrastructure. Nobody rehearses for a pandemic. You rehearse for a bad Tuesday, and it turns out to cover pandemics.

The universities moved instruction online mid-semester, announced through sites whose traffic surged past every modeled peak while the campuses they described emptied. The health systems stood up screening guidance, visitor policies, and testing information under public-health direction that changed daily and sometimes hourly. The nonprofits moved services, counseling, and community programs to whatever virtual form could exist by Friday. Town and school sites carried closure decisions to entire regions at dinnertime.

And all of it ran on websites operated, as of roughly March 12, by teams newly scattered to kitchen tables. On home broadband. With children home, and the office VPN under loads its procurement never imagined. The industry’s traffic observers documented the surge in aggregate. The CDN and backbone reports show step-changes that normally take years arriving in days. This post documents it from the operator’s chair because what held, what mattered, and what predicted who coped are findings our readers will need again. The middle of the event is when the notes are honest.

What held: the boring architecture, again

The infrastructure findings first, because they are the shortest and the most cleanly earned. Cache-first setups held. The sites fronted by CDNs with real cache coverage absorbed traffic multiples without drama. Surging info pages are exactly the read-heavy load the edge exists for, and the March surge was overwhelmingly that kind.

Static fallbacks earned their keep. The emergency pages built as static documents (no database, no app layer, promotable by DNS or CDN rule) served as designed at the moments origin systems strained. Several clients ran their highest-traffic hours of all time on pages with no moving parts. That is the entire argument for them compressed into a fact.

The launch-calendar instrument worked in reverse. The send-in-waves habit, announcement emails staged rather than detonated, kept self-made spikes off systems already carrying real ones. None of this is novel. All of it is the oldest advice performing under the least novel conditions imaginable. The sites that had spent years finding it boring spent March depending on it. Dull setups, thrilling returns.

What mattered more than technology

• Message hierarchy, ruthlessly enforced: the crisis pattern that separated usable sites from well-meaning ones. What changed, what to do, where to check back. In that order, at the top of the page. No scrolling. No institutional throat-clearing. The visitor at 10 p.m. deciding whether to travel, attend, or bring a parent to a facility is not reading your mission statement. The sites that understood this looked sparse and served magnificently.

• Update workflows faster than the facts’ half-life: guidance changing by the hour exposed every publishing bottleneck. The approval chain built for brochure content. The single trained editor. The deploy path requiring a developer. Sites with rehearsed, distributed publishing updated in minutes. Sites without it published yesterday’s guidance all week.

• A single source of truth, linked relentlessly: one canonical emergency page, updated in place, timestamped visibly. Every email, social post, and subsidiary page pointing at it rather than duplicating it. The pattern prevented the version-skew that turned some institutions’ own channels against them.

• Timestamps as trust infrastructure: ‘Updated March 19, 4:30 p.m.’ did more work this month than any design element on any page we have shipped. In a moving situation, content without a timestamp is rumor with a logo.

What predicted who coped

The finding this post exists to record, because it will outlive the crisis and deserves to. The variable that best predicted institutional coping was not budget, sector, or team size. It was governance, held in ordinary times.

Current platforms: the sites that had kept the maintenance calendar could deploy changes without fearing their own systems. Clear content ownership: the organizations that knew who owned each page updated them, while the ones that didn’t convened meetings while the facts changed. Rehearsed deployment paths: the teams that had practiced publishing under time pressure, even once, in a tabletop, moved without improvising their own process. Complete inventories: knowing what you run meant knowing what needed a banner, a fallback, a freeze.

Every one of these is a practice taught in calm months to audiences who sometimes heard them as consultant hygiene. March priced them. Governance, it turns out, is an emergency capability. It is purchased only in advance, and invisible until the week it is the difference between an institution that can speak and one that cannot. The sites that coped were not the ones that predicted a pandemic. They were the ones that had, for unrelated and mundane reasons, kept their houses in order. The order was always the asset. The emergency merely audited it.

Written mid-event

Honesty about the moment, written down while it is true. Everyone is improvising, ourselves included. We have made judgment calls this month with incomplete information. We have shipped things in days that would normally take weeks and reviewed them after rather than before. We have watched our own assumptions about capacity, availability, and what ‘urgent’ means get repriced in real time.

Improvisation, though, runs on preparation. Every fast decision this month drew on something slow, built when nothing was burning. A rehearsal, an inventory, a relationship, a document. And the preparation was purchasable years ago, by anyone, at calm-month prices.

That is the lesson this post wants to outlive the crisis, put plainly for the after-action reviews to come. Fund the boring capabilities as the emergency infrastructure they just proved to be. The caching, the fallbacks, the ownership, the rehearsals. Hold the after-action honestly when the time comes, because the institutions that learn from this month will be the ones that wrote things down during it. We will return to the subject. The event is not over, and neither are the notes. To the client teams publishing guidance at midnight from kitchen tables, and to the readers doing the same: the infrastructure held because people held it. That, too, is worth writing down.