The repair hour: what a fibre cut really costs a regional operator, and how to shorten it

European FTTH has crossed into its mature phase. Networks now pass some 295 million homes, about 79% of households across the EU39, and the build curve is flattening (Fibre Systems, on the FTTH Council's 2026 Market Panorama). When coverage stops being the story, keeping the customers you connected becomes the story. And nothing loses a business customer faster than a link that's down while nobody can say when it's back.

For a regional operator, that risk has a price. The industry figures for enterprise telecom downtime run to $5,600 to $9,000 a minute (Socium), but your number is smaller and more specific than a headline: the SLA credits you owe on business lines, the crews you dispatch, and the customers who quietly don't renew after a bad week. Business SLA breaches typically cost 5% to 25% of the monthly contract value per incident. That's the bill worth managing.

The slow part is finding the fault

The surprise, for anyone who hasn't run a NOC, is that the fix is rarely the slow bit. Finding the fault is.

The traditional route sends four or five technicians out over four or five hours to locate the break before anyone can repair it (EXFO). Every one of those hours is a truck on the road, a crew off other work, and a customer watching the clock. The repair itself, once you're standing at the right manhole, is the easy part.

So the way to move that bill is to shorten the hunt.

Two levers a regional operator can actually pull

Remote fibre monitoring. A remote fibre test system watches your links from a central point and pinpoints a fault to a location in minutes instead of hours, automatically, before a single truck rolls (VIAVI). The crew leaves the depot knowing which span and roughly which pole, instead of hunting a dark route in the rain. Fewer trucks, shorter mean-time-to-repair, lower maintenance cost on the same network.

Protection switching. For the routes that carry your business customers, an optical line protection unit or bypass switch fails traffic over to a diverse path the moment the primary drops. The customer's link stays up while you repair the broken one on your own schedule. The SLA clock never starts.

Neither is free. Monitoring is capital on test heads and access to the fibre; protection needs a diverse second route to switch to. So you don't blanket the network with either. You put them where an hour of outage hurts most: the aggregation rings and the business-customer feeds. Rank your routes by what a cut costs, and let that decide.

Where I stand in this

I should be plain about my interest. Jupiter Enterprises, our agency in Amsterdam, represents fibre manufacturers commercially in Europe. One of them, PDR World, carries an operator resilience line in its catalogue: optical line protection, optical bypass switching, a remote fibre test system, and CWDM/DWDM to get more out of the fibre you already have. It's the same manufacturer whose gear runs behind India's tier-1 carriers at deployment scale and India's national grid operator, where a fault on a transmission line is a safety matter.

I'm not going to tell you a monitoring box prevents cuts. It doesn't. It shortens the part of the outage you're paying technicians to spend hunting, and it moves the fault from "somewhere on the route" to "here" before the crew leaves. On the routes where that hour is expensive, that's the whole argument.

Run it on one route

Take a single aggregation ring or business feed and count: how many faults last year, how long each one took to locate before the fix, how many trucks that took, and what you paid or credited when a business line went dark. Set that against the cost of monitoring the route. On a critical span the maths usually makes itself; on a quiet residential branch it won't, and you'll know to leave it alone.