Thread

1. cube00 · 1790017251 · focus · HN ↗

   > When it went to flip into the backup, we discovered that the backup fiber had a break

   Pretty grim that a life critical system wasn't designed to report that the backup fibre was unserviceable until they attempted to switch over to it.

   I wonder how long it was down? Days, weeks, months?

   1. toast0 · 1790018021 · focus · HN ↗

      Sometimes your multiple fiber paths end up in the same bundle, severed by the same backhoe. It's always a fun day when that becomes apparent.

      1. unethical_ban · 1790020443 · focus · HN ↗

         That is negligence, practical if not contractual.

         Over ten years ago, my employer was spinning up a new DC across the state and had three links between it and the primary DC. Two were pretty direct, but we needed a third because at one point in the 300 mile path, the two main links went within 400 meters of each other.

         So how national-security-adjacent critical systems like an airport system doesn't have a larger set of backup links, and validates that they are geographically separate up until the connections, and have realtime alerting on the connection status, is surprising to me.

         1. mikeweiss · 1790026991 · focus · HN ↗

            For all we know the contract says the FAA is responsible to notify Verizon if the line becomes dead. We don't know what the agreement is.

Unofficial Hacker News client; not affiliated with Y Combinator.