What a Submarine Cable Cut Actually Looks Like From the Outside

Somewhere in the ocean right now, a fishing trawler is probably dragging its gear across a length of fiber optic cable without anyone on board knowing it. I spent years around network operators, the people who peer traffic between networks and worry about the physical layer nobody else thinks about, and one of the first things that surprised me was how casually that world treats cable damage. Faults happen constantly. The reaction to them is almost bureaucratic.

Nobody outside the industry tracks this closely, but people who do estimate that cable faults happen year-round, spread across every ocean, far more often than the general public assumes. Most never reach a headline. Set that against how rarely an average person notices their connection falter because of something happening on the seabed, and you get the real subject of this post: the gap between how often the ocean damages our infrastructure and how little anyone ever feels it.

Why cables get cut

The boring truth is that almost none of it is sabotage. An anchor dragged in the wrong spot during a storm accounts for a lot of it. Fishing trawls scraping bottom in shallow coastal waters, where most damage actually concentrates rather than out in deep water, account for more. Underwater landslides and years of slow abrasion against rock in a current explain most of the rest. Cables occasionally get bitten by fish or crustaceans too, though that's rarer than the old stories suggest now that armoring has improved.

Deliberate cuts do occur. When they do, they get attention precisely because they're rare, not because they're typical, and that scarcity is exactly why they make headlines while the routine ones don't. Statistically, an anchor remains a far better first guess than a saboteur, and I'd push back on any framing that assumes otherwise before an investigation says so.

Fixing it takes longer than people expect

Repairing a cable is nothing like patching a pothole. It requires a specialized cable-repair ship, and there are only so many of those relative to the amount of cable sitting on ocean floors worldwide, so one ship often covers a wide region rather than sitting near any single route. Once a ship reaches the fault, the process is fairly mechanical: locate the break, grapple the cable up from the seabed, haul both damaged ends aboard, splice in a new section, test the splice, then lower everything back down.

Weather controls most of the timeline. In calm conditions the whole job can look almost routine, wrapped up within days. Storm season, deep water, or a permitting delay in someone's territorial waters can stretch that same job into weeks.

Why you never notice

Redundancy is the entire reason most cuts are invisible. Major routes are rarely carried by a single cable. Traffic gets engineered to reroute automatically the moment something drops, often within seconds, long before a human operator has finished reading the alert. From where you're sitting, that shows up as nothing. Maybe a slightly higher ping, if you happen to be watching for it, which almost nobody is.

The places that do feel a cut are the ones without that redundancy built in. Islands and countries served by one or two cables total, sitting at the end of a route instead of inside a dense mesh of them, have nowhere for traffic to go when the cable that matters goes down. Backup satellite capacity gets expensive fast, video calls degrade, and connections can stay unreliable for as long as the repair ship takes to arrive.

What strikes me, having spent years adjacent to this world, is how little of the outcome depends on the cut itself. A trawler dragging a net has no idea whether it's about to knock a country offline for a month or cause a blip nobody measures. That gets decided years earlier, by whoever did or didn't pay for a second cable and a third path around the obvious one. Most of the time, nobody thinks about any of this until a video call freezes. They glance at a status page and move on with their day.