This post is from the Blog Herald archive, originally authored by Duncan Riley.
In October 2008, something happened that should have sent tremors through every newsroom running their digital presence on a hosted platform.
TypePad, the Six Apart blogging service trusted by The Chicago Tribune, The Bakersfield Californian, and The Toronto Star, experienced repeated service outages that left enterprise publishers watching their digital properties vanish from the web.
These weren’t hobby blogs going offline. These were revenue-generating news operations, publications that had made strategic decisions to outsource their blogging infrastructure to a commercial platform.
When TypePad’s core router failed due to a bad power supply, those decisions suddenly looked catastrophic.
Blog Herald first covered these enterprise users and their frustrations as the outages mounted.
The outages weren’t isolated incidents. Throughout 2008 and into 2009, TypePad users reported multiple disruptions, each one eroding confidence in the platform’s ability to support mission-critical publishing.
Six Apart’s Anil Dash provided explanations and apologies, but the damage was done.
Major news organizations began exploring exit strategies, realizing they’d built their digital presence on infrastructure they couldn’t control.
What makes this story worth revisiting today isn’t just the nostalgia for a platform that eventually shut down in 2025.
It’s what those outages revealed about a tension that still defines digital publishing: the tradeoff between convenience and control, between managed simplicity and operational sovereignty.
The promise and peril of managed platforms
Six Apart positioned TypePad as liberation for publishers. No servers to maintain, no databases to optimize, no security patches to apply. Just write, publish, and let the platform handle the technical complexity. For newsrooms already stretched thin, it was an attractive proposition.
The platform attracted serious users because it offered serious features: custom domain mapping, professional design templates, enterprise support. When TypePad launched its advertising network in 2008, Six Apart was explicitly positioning itself as a full-service infrastructure for digital publishing, not just a blogging tool.
But that promise contained an inherent contradiction. The more crucial TypePad became to a publisher’s operations, the more catastrophic any service disruption became. A one-hour outage for a personal blog is an annoyance. A one-hour outage for a news organization is lost revenue, broken reader trust, and potentially damaged relationships with advertisers.
The enterprise publishers using TypePad discovered they’d traded operational complexity for operational helplessness. When the platform went down, they couldn’t fix it. They couldn’t even see what was broken. They could only wait and hope, watching their digital presence disappear while Six Apart’s engineers worked on problems the publishers couldn’t access or understand.
The migration trap that still catches publishers
What happened next illustrates a problem that remains urgent in 2026: the platform exit is always harder than the platform entrance.
When TypePad launched its “Journalist Bailout Program” in late 2008, offering free accounts to laid-off journalists, it was simultaneously positioning itself as both savior and symptom of journalism’s digital transformation. But for enterprise users already questioning the platform’s reliability, the program highlighted a different concern: if TypePad was courting individual journalists, was it still prioritizing enterprise stability?
The publications that left TypePad faced choices that mirror decisions publishers still confront today. Move to WordPress and accept the operational overhead of managing your own infrastructure. Migrate to another hosted platform and hope it proves more reliable. Or stay put and pray the outages don’t happen during crucial news cycles.
According to analysis of enterprise software reviews, roughly 73% of data migration projects struggle due to poor planning and governance gaps. Migration timelines typically overrun by 150% when organizations lack platform-specific expertise. The average enterprise cloud migration costs around $1.2 million and takes eight months to complete.
Those numbers explain why some TypePad users stayed even after reliability concerns became undeniable. The cost of leaving, both financial and operational, can exceed the cost of enduring periodic outages. Until it doesn’t. Until one outage happens at exactly the wrong moment, and suddenly the migration you’ve been postponing becomes urgent.
What platform independence actually costs
The hosted platform model that TypePad represented hasn’t disappeared. It’s evolved. WordPress.com, Medium, Substack, Ghost, and dozens of other platforms offer the same essential bargain: we’ll handle the infrastructure, you focus on content.
But the underlying tension remains unchanged. Current industry standards suggest that uptime of 99.9% is the baseline expectation, meaning your site should be down no more than 8.76 hours per year. Many modern platforms, particularly those backed by major cloud infrastructure, now deliver 99.99% uptime or better.
That’s a meaningful improvement over TypePad’s 2008 performance, but it doesn’t eliminate the fundamental problem. Even 99.99% uptime means potential downtime of 52 minutes per year. For a news organization publishing breaking stories, 52 minutes of unavailability at the wrong moment can be catastrophic. And unlike platform operators measuring uptime in annual percentages, publishers experience outages in real time, during specific events that may never recur.
The alternative, self-hosted infrastructure, comes with its own cost structure. You gain control but accept responsibility. Server management, security updates, scaling for traffic spikes, database optimization, backup strategies, all of this becomes your problem. Recent data suggests that organizations moving to cloud infrastructure can expect 20-30% reduction in IT costs compared to traditional on-premises setups, but those savings assume you have the expertise to manage cloud infrastructure efficiently.
The TypePad users who migrated to self-hosted WordPress discovered that operational independence requires operational competence. You can’t call TypePad support when your server crashes. You’re the support.
The questions publishers still aren’t asking
What makes the TypePad story instructive isn’t just what happened. It’s what publishers should have asked before committing their infrastructure to a commercial platform, and what many publishers still aren’t asking today.
Where does your content live when the platform is down? If you can’t access your own content during an outage, you don’t own your platform, you’re renting access to it. How quickly can you migrate away if the platform becomes unreliable or unviable? If the answer is measured in months rather than days, you’ve accepted vendor lock-in whether you intended to or not.
What’s your plan when the platform makes strategic decisions that conflict with your needs? Six Apart’s eventual sale to SAY Media and the shutdown of Vox showed that platform operators prioritize their business model over any individual publisher’s needs. Does your platform architecture assume reliability, or does it plan for failure? The difference matters. Systems designed to fail gracefully survive outages better than systems that assume outages won’t happen.
These aren’t abstract concerns. They’re the operational realities that determine whether a platform becomes infrastructure or liability.
What we learned, and what we keep forgetting
The TypePad outages revealed something many publishers preferred not to acknowledge: convenience and control exist in tension. Every time you outsource operational complexity, you accept operational dependence.
That doesn’t make hosted platforms wrong. It makes blind trust in them dangerous. The news organizations using TypePad in 2008 weren’t foolish for choosing a managed platform. They were foolish for not preparing for what would happen when that platform failed.
The publishers who survived TypePad’s decline were the ones who treated it as infrastructure rather than solution. They maintained export capabilities, documented migration procedures, and never fully surrendered the ability to move. When reliability concerns became acute, they could act rather than simply endure.
Today’s publishing landscape offers more platform choices than 2008, but the fundamental calculation remains the same. Managed platforms work until they don’t. The question isn’t whether you should use them. It’s whether you’re prepared for the moment they stop working as promised.
The TypePad users who found themselves locked into an unreliable platform learned this lesson the hard way. Their digital presence vanished because they’d built it on infrastructure they couldn’t control and couldn’t quickly abandon.
That’s not a problem that better uptime statistics solve. It’s a problem that requires different thinking about what it means to own your publishing platform versus merely using one.
