By Berend Booms, Associate Editor | Future of Assets
A few weekends ago, on one of the hottest days we have had this summer, a large part of the Netherlands lost the ability to control its own bridges and locks. Rijkswaterstaat, the national agency responsible for our major roads and waterways, had been carrying out planned maintenance on a fiber-optic cable that morning. Something in that work went wrong, and the agency lost its internet connection for the better part of the day. Centralized control of bridges and locks went down, the traffic center stopped receiving camera feeds from the motorways, the digital signs that place warning crosses over closed lanes stopped working, and the agency's own websites went dark. It took until roughly five in the afternoon for the connection to start coming back, and until around nine that evening before everything was running normally again.
Nothing collapsed, and as far as I have been able to find, no one was seriously hurt. Bridges and locks were operated locally where possible, many bridges were already locked shut as a precaution against the heat, and warnings went out to boaters and motorists to plan around the disruption. Looked at in isolation, this was a well-managed incident that resolved itself within a single day. That is exactly why it stayed with me longer than the news cycle did. The infrastructure failures that matter most rarely make headlines for a week. The one that should worry you barely makes the news at all.
A Single Cable, A National Nervous System
What stays with me about this incident is the gap between its cause and its consequence. The trigger was about as mundane as it gets: scheduled work on a fiber-optic connection, the kind of maintenance that happens constantly across telecom and utility networks without anyone outside the contractor ever noticing. The consequence was a temporary loss of centralized control over a meaningful share of the country's transport backbone, at the exact moment a severe thunderstorm warning was in effect across four provinces.
This is the part of the story that matters most to me. Rijkswaterstaat's bridges, locks, and tunnels have been progressively digitized and centralized, and for good reasons. It is much more efficient to monitor and operate hundreds of structures from a coordinated network than to staff every single site around the clock, and centralized camera coverage allows a relatively small traffic center to watch a far larger road network than any number of patrol vehicles ever could. But every layer of centralization we add is also a layer of common-mode failure waiting to be discovered. It took a single maintenance moment on a fiber-optic cable to take a meaningful share of the network out of automated reach all at once. Local manual fallback worked where possible, but the gap between possible and impossible is precisely where high-stakes downtime has its biggest impact.
Dependency That Doesn't Announce Itself
An increased reliance on digital, centralized governance also means that consequences compound more easily once failure sets in. Boaters were told to plan around bridges and locks that might not respond promptly. Motorists lost the digital lane-closure warnings that exist specifically to keep someone broken down on the hard shoulder from being hit by passing traffic. Reduced camera coverage meant stranded drivers might take longer to be spotted at all. On their own, these instances are manageable; stack them together during a period when severe weather is also bearing down on the same road and water network, and there is very little margin left for anything else to go wrong.
That is the pattern I think is worth carrying into how any of us think about the critical systems we are responsible for, whether the asset in question is a highway bridge, a production line, an 18-wheeler, or an MRI scanner. The challenge in all of this isn’t 'how reliable is this system on a normal day.’ It is ‘what does this system's blind spot actually look like, and what else has to go right while it is blind.’ Dutch oversight bodies have been making a similar point in recent assessments of national digital resilience: critical-sector operators often do not have a clear picture of which processes depend on which IT and telecom links until something forces the issue, and water authorities and Rijkswaterstaat have themselves been increasing investment in securing the operational technology behind locks, weirs, and pumping stations, precisely because that dependency has grown faster than the oversight of it.
The Lessons That Gets No Applause
The appeal of this story is precisely its lack of drama: there’s no big explosion, no negligence, no damage or injuries, just routine maintenance that exposed how much sits behind a single network connection. It’s something we ought to take seriously rather than dismiss as a one-off. There’s no point in promising or pretending it won’t happen again; the point is knowing exactly where it will hurt most when it does, and how fast you can respond. That’s the lesson here: identifying what breaks first when things come to a halt, what the fallback looks like, who is authorized to take over manually, and how long that handover actually takes under pressure, not just on paper. A few hours without bridges and traffic cameras on a hot, stormy Saturday turned out to be perfectly manageable. That wasn't luck; it was the manual fallback, the local override, the protocol someone wrote down long before anyone needed it. That's the version of this story worth remembering, not the outage itself.