Earlier quoted context omitted.
> 1.4 million km Strange way of writing 1.4gm.
Gram-metres?
Hahaha.
Hosted by my own petard. :)
Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
51–60 of 61 posts
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#52Earlier quoted context omitted.
They can but it's an involved process. Modern cables manage their slack very precisely - a complicated job in and of itself - and usually cannot be hauled to the surface without snapping them. So if the cable is not already cut (an anchor can damage a cable in a variety of ways short of physically snapping it) it will be cut while still on the bottom. The ends are then winched up and a splice is patched in but now th…
So then you have extra latency for each repair.
And extra attenuation / reflections.
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#53Earlier quoted context omitted.
https://www.bbc.com/future/article/20241014-the-deep-sea-eme... An article about people who fix this Also, the teams are quite busy: > "There are 150 to 200 instances of damage to the global network each year. So if we look at that against 1.4 million km, that's not very many, and for the most part, when this damage happens, it can be repaired relatively quickly." ... > If a fault is found, a repair ship is dispatche…
> 1.4 million km Strange way of writing 1.4gm.
Should be 1.4Gm
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#54Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#55Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#56Earlier quoted context omitted.
> Cables in Red Sea got cut frequently On land, we’ve call before you dig . I wish they could do something like call before you drop (anchor) training or just get the word out.
They are usually marked on nautical charts.
Couldn't that be a security concern?
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#57Were they cut on purpose or accident?
Cables in Red Sea got cut frequently. All the time it's the same story - anchor dropped where it should not. Similar stories happen near Singapore.
You mean no Russian or Chinese ships deliberating cutting cables on land like in EU ? That can't be /s
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#58Earlier quoted context omitted.
They are usually marked on nautical charts.
Couldn't that be a security concern?
Security concern is the more unlikely scenario of accidental cutting. There is enough redundancy that it is very difficult to cut them all for a single ship and if there are hypothetically multiple ships all cutting at the same time, then it is likely to be traceable. The cost of cutting these cables by sending someone out there is significant enough in addition to how unlikely they are to succeed.
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#59Earlier quoted context omitted.
(It’s not actually anchors.)
Why do you say that? I can't say I'm an expert on the matter, but my understanding from industry reporting on some likely intentional ones in the Baltic where that they were still unambiguously done with anchors. Just by someone intentionally causing the anchor to drop and drag along.
I meant they are intentional, as opposed to being a side-effect of ‘anchoring’ the boat to keep it from moving.
Re: Microsoft Azure: "Multiple international subsea cables were cut in the Red Sea"
#60Earlier quoted context omitted.
(It’s not actually anchors.)
It very often _is_ an anchor, and they are usually dropped and dragged on purpose for the effect of cutting the cables which are clearly marked on charts as places to not drop anchor
The chances of it being due to accident seems astronomically low, but I didn’t realize the intentional cutting was by an actual anchor. That makes sense though, as it would be an easy, discreet method.