11–20 of 94 posts
Can they somehow tell exactly where the cable was cut?
Yeah there's special tech for that! Has something to do with sending some frequency over the line and measuring how long it takes to "reflect" off of the breakage and back to the shore.
Earlier quoted context omitted.
Yeah there's special tech for that! Has something to do with sending some frequency over the line and measuring how long it takes to "reflect" off of the breakage and back to the shore.
The term is time domain reflectometry, TDR. It used to be really expensive, and now it's filtered down into medium-cost optical adapters.
I had the pleasure of using one of the devices that had that when I wired my old house. Borrowed the kit from ... an institution that allowed me to get their gear for a weekend. (Yes, I knew people in there.) Having the device tell me that a given strand in a CAT5e cable was faulty at from my location made it surprisingly easy to detect where I'd messed up.
Earlier quoted context omitted.
Yeah there's special tech for that! Has something to do with sending some frequency over the line and measuring how long it takes to "reflect" off of the breakage and back to the shore.
The term is time domain reflectometry, TDR. It used to be really expensive, and now it's filtered down into medium-cost optical adapters.
Bitten by a shark, or snagged on a russian submarine? Whichever the case, I just ran an ansible deployment over our cluster that's spread over their Frankfurt and Helsinki datacenters, and I didn't notice any difference. I guess that's to be expected, their line between those datacenters is just an optimization, the internet is still functioning as it always is and maybe Hetzner gets a slightly larger egress bill fro…
In all likelihood much less interesting, probably snagged in a fishing net or hit by an anchor.
Break detected
Ship has been commissioned
Ship is at harbor
Ship has sailed out to the cut
Fusing the ends
Service restored
Can they somehow tell exactly where the cable was cut?