On January 30, 2008, the internet didn’t crash because of a cyberattack or a software bug. It crashed because of an anchor.
Somewhere off the coast of Alexandria, Egypt, a ship dragged its anchor across the seabed and severed two of the most critical submarine cables in the world — FLAG Telecom’s FLAG Europe-Asia (FEA) and SEA-ME-WE 4. Within hours, a third cable was cut. Then a fourth. Then a fifth.
By the time the damage was tallied, five submarine cables had been severed in the span of a week. The digital equivalent of cutting a continent’s jugular.
The Domino Effect
The impact was immediate and devastating:
- Egypt lost 70% of its internet capacity overnight.
- India saw bandwidth drop by 50-60%, with major IT hubs in Bangalore and Mumbai grinding to a halt.
- Pakistan lost nearly all international connectivity.
- Saudi Arabia, UAE, Kuwait — business hubs that run on real-time global communication — went dark.
This wasn’t just about not being able to browse YouTube. Stock exchanges slowed. Outsourcing firms couldn’t reach clients. VoIP calls dropped. Banks couldn’t process international transactions.
The Damage at a Glance
| Country/Region | Internet Capacity Lost |
|---|---|
| Egypt | 70% |
| India | 50–60% |
| Pakistan | ~70% |
| Saudi Arabia | ~50% |
| UAE | ~40% |
| Bangladesh | ~80% |
How Did This Happen?
The uncomfortable truth is that most of the internet between Europe and Asia flows through a single chokepoint — the Strait of Hormuz, the Red Sea, and the narrow waters off Alexandria.
These cables are buried in the seabed, typically about 1 meter deep in shallow coastal waters. But in busy shipping lanes, anchors, fishing trawlers, and even earthquakes can reach them. The 2008 cuts likely involved a combination of anchor drags and seabed disturbances.
The cables themselves are remarkably thin — about the diameter of a garden hose in deep water, with added armoring near the coast. For all the billions of dollars of data they carry, they’re physically fragile.
The Conspiracy Theories
The timing of five cuts in one week was suspicious enough to spawn conspiracy theories. Were they deliberate? Was it sabotage? The Egyptian government initially denied that any ships were in the area — adding fuel to the fire.
Subsequent investigations pointed to natural seabed movement and accidental anchor drags as the most likely causes. But the incident highlighted an uncomfortable question: what if someone did this on purpose?
In the years since, military strategists have increasingly recognized submarine cables as critical infrastructure. Russia’s increased submarine activity near cable routes has been a consistent concern for NATO.
The Repair Mission
Fixing a submarine cable isn’t like splicing a wire in your house. It requires:
- Locating the break — using optical time-domain reflectometry (OTDR) to pinpoint the fault to within meters.
- Deploying a cable ship — specialized vessels like the ones operated by SubCom or Alcatel Submarine Networks.
- Grappling the cable from the seabed, which can be thousands of meters deep.
- Cutting and splicing — the damaged section is cut out and a new segment is spliced in, a process that takes hours of precision work.
- Re-laying the cable and burying it back into the seabed.
Each repair took 1–2 weeks per cable. During that time, traffic was rerouted through whatever capacity remained — creating bottlenecks that slowed the internet across half the planet.
The Lessons Learned
The 2008 cable cuts were a wake-up call for the telecommunications industry:
- Redundancy matters. Countries that depended on only two or three cables were devastated. Those with diverse routing — like Singapore — barely noticed.
- Geographic diversification is critical. Running all cables through the same narrow strait is a single point of failure.
- Cable protection zones in shallow waters need stricter enforcement — anchoring bans, patrol boats, and real-time monitoring.
- Terrestrial backups (satellite, overland fiber) can absorb some load, but they can’t replace submarine cable capacity.
The World Since 2008
Since the cuts, the industry has invested heavily in new routes. Google, Meta, Microsoft, and Amazon now fund their own private submarine cables, choosing routes that avoid traditional chokepoints.
But the fundamental vulnerability remains. In 2024, the Red Sea cable damage — caused by a Houthi-attacked cargo ship dragging its anchor — proved that the same scenario can repeat. Three cables were damaged, and the repair ships couldn’t even access the area due to the conflict.
Why This Matters to You
Every time you load a webpage, stream a video, or make a video call, your data likely travels through at least one submarine cable. If you’re in India, your international internet traffic almost certainly passes through the same waters off Egypt where those five cables were cut.
The internet feels invisible, wireless, omnipresent. But it’s not. It’s a physical thing — glass fibers, thinner than a human hair, carrying the light pulses that connect 5 billion people. And sometimes, all it takes is one misplaced anchor to remind us how fragile that connection really is.