/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

WP.com Downtime Summary

Today WordPress.com was down for approximately 110 minutes, our worst downtime in four years.  The outage affected 10.2 million blogs, including our VIPs, and appears to have deprived those blogs of about 5.5 million pageviews.  —  What Happened …

WordPress.com News Matt

Context & Ripple Effects

Automattic is treating this as a public postmortem rather than a quiet fix: 110 minutes of downtime across 10.2 million blogs, including its paying VIP accounts, with an estimated 5.5 million pageviews lost. The company had a comparable platform-wide incident back in August 2006, so 'worst in four years' frames today against a mostly clean record since.

The scale of the blast radius is what makes this a story: when Google's Blogger went down hard in January 2008, bloggers' unhappiness made the rounds, and today GigaOM counted itself among the 10.2 million blogs taken offline. Multi-tenant blogging means one infrastructure failure is now a mass media event.

First-order effects

  • 10.2 million blogs — including paying VIP publishers like GigaOM's network — were unreachable for roughly two hours, directly forfeiting an estimated 5.5 million pageviews.
  • Automattic must now defend its VIP contracts and uptime commitments, since the outage touched exactly the commercial tier that pays for reliability guarantees.

Second-order effects

  • Prospective VIP and enterprise buyers gain fresh ammunition to demand SLAs, redundancy detail, or self-hosted alternatives before committing their publishing to a shared WordPress.com infrastructure.
  • Rival hosted platforms such as Blogger get a talking point on reliability — even though Blogger's own 2008 outage shows nobody in this category has an unblemished record.

Third-order effects

  • As independent publishing consolidates onto a handful of multi-tenant platforms, each platform's failure mode becomes systemic: one bad deploy or hardware fault takes millions of voices offline simultaneously, making published uptime records and postmortems a structural competitive requirement rather than optional transparency.

The trend: Hosted blogging platforms are scaling into critical publishing infrastructure, where single-platform outages now register as industry-wide events and uptime transparency becomes a baseline expectation.