/
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
Handles
Browse by social media handle
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

Hurricane Sandy Proved How Hard It Is to Break the Internet

All the damage to the communications infrastructure brought on by Hurricane Sandy is sure giving the people who keep track of the technical underpinnings of the Internet a lot of fodder to see how well things do and don't work in real-world situations.

AllThingsD Arik Hesseldahl

Context & Ripple Effects

Hurricane Sandy gave network researchers an unplanned stress test of the Internet's physical layer in the New York metro area, and the story traveled unusually far for a technical post — picked up by Betabeat, Renesys, CircleID and Peter O'Kelly's Reality Check within a day. The measurement angle matters because Renesys-style routing data is one of the few ways to see how the network actually behaved under regional power and fiber loss.

The piece lands mid-arc in a week of Sandy coverage: wireless carriers' backup plans were already exposed by outages days earlier, Gawker had been pushed onto a State Farm-sponsored backup Tumblr after losing its own infrastructure, and Google folded power-outage data into its Sandy crisis map. It also revives the question The Atlantic posed in February 2011 about how close the Internet has come to fracturing — this time answered by a storm rather than a policy fight.

First-order effects

  • Carriers and data-center operators in the flooded zone are being graded in public on their generator and failover performance, with the WSJ's outage reporting turning backup architecture into a reputational issue.
  • Publishers that lost their own hosting, Gawker most visibly, are running on borrowed infrastructure — sponsored fallbacks that keep sites alive but break features like comments.

Second-order effects

  • Infrastructure-monitoring firms such as Renesys gain a rare real-world dataset on regional routing behavior, which becomes reference material for carriers and regulators weighing redundancy investments.
  • Crisis-information tools like Google's outage map get validated as emergency-response channels, pushing agencies and utilities to treat consumer platforms as part of disaster communications rather than optional add-ons.

Third-order effects

  • If the pattern holds, the durable lesson is asymmetric resilience: the Internet's distributed routing survived a major metropolitan hit while its dependence on local power and last-mile plant became the binding constraint — sharpening the fracture-resilience debate The Atlantic framed in 2011.
  • Expect backup capacity to shift from an engineering afterthought to a marketed feature, as carriers and publishers alike discovered that failover plans are now judged in public within days of a disaster.

The trend: Disasters are becoming the de facto benchmark tests for Internet resilience, exposing that the network's weak point is physical infrastructure rather than its routing fabric.