TechCrunch And Millions Of WordPress.com Blogs On Pause Due To Back-End Outage [Update: We're Back!]
Notice anything different about this post? How about that the links are orange? Yes, that's right, I'm blogging off of CrunchGear because it's been impossible to access our WordPress.com back-end for a little over two hours.
Context & Ripple Effects
WordPress.com's back-end has gone dark before: Automattic published a WP.com downtime summary just over a year ago acknowledging the platform's reliability record, and the 2005 debate over interop between blogging tools already flagged what happens when writers depend on one host's infrastructure. The 2008 Blogger outage showed Google's rival service failing the same way.
First-order effects
- Millions of WordPress.com blogs, including TechCrunch's own publishing stack, were locked out of their back-ends for over two hours on March 22, 2011 — TechCrunch resorted to posting through sister site CrunchGear to keep publishing.
- Access was restored the same day per the article's update, but every affected blogger spent those two hours with no editorial control and no workaround except cross-posting elsewhere.
Second-order effects
- The episode hands competitors like Blogger a reliability talking point, though its own 2008 outage undercuts any claim that self-hosted alternatives or rival hosts fail less often at scale.
- High-profile publishers like TechCrunch face renewed pressure to maintain fallback publishing paths — separate domains, mirror sites, or exportable content — rather than betting their output on a single hosted back-end.
Third-order effects
- If outages keep hitting major hosted platforms, the old interoperability argument from 2005 returns: open APIs and portable content stop being developer conveniences and become publisher insurance against platform-wide failure.
The trend: Hosted blogging platforms are consolidating millions of publishers onto shared infrastructure whose single points of failure periodically take entire ecosystems offline at once.