Tracerout gives me a path like this spine5.cloud2.fsn1.hetzner.com -> core22.fsn1.hetzner.com -> core5.fra.hetzner.com -> core53.sto.hetzner.com -> core31.hel1.hetzner.com
Which is worse than before, but still works for me.
Tracerout gives me a path like this spine5.cloud2.fsn1.hetzner.com -> core22.fsn1.hetzner.com -> core5.fra.hetzner.com -> core53.sto.hetzner.com -> core31.hel1.hetzner.com
Which is worse than before, but still works for me.
I suspect that the costs of moving extra bits through other cables is not large. I would assume that Hetzner (and the other companies that own parts of these cables) have peering agreements with other companies and that most of them will not try and take advantage of the cut cables to renegotiate their peering agreements (2). So whatever rates they paid before will still be paid.
1: Because a war creates a problem for the risk pool, it is one of the things that actually can destroy huge amounts of property simultaneously, so it is a risk explicitly separated out and basically impossible to insure against, at least in the US commercial market.
2: Too risky to start renegotiating when your cable can be cut just as easily the next time.
Russia/China/US would I’m sure like to keep plausible deniability here, as it minimizes outright repercussions (for everyone), while still keeping the option on the table for them to tit-for-tat.
It wouldn’t surprise me if any insurance involved (which surely wouldn’t pay out in event of war) would want to claim it was an act of war.
Anyone trying to claim against such insurance would want to claim it wasn’t an act of war (just a mistake), so they could get the payout.