Notices by RIPE NCC (ripencc@mastodon.social)

@acontios I will pass this on to my boss 😉

Sweden-Latvia Internet cable was reportedly cut on 26 January. @meileaben reports that packet delays between selected #RIPEAtlas anchors increased by 5-20ms at around 00:45 UTC.

However, no packet loss was observed, suggesting that the Internet successfully routed around the damage.

Interested? Read a deep-dive into a previous cable cut in the Baltic Sea by our researcher Emile Aben: https://labs.ripe.net/author/emileaben/a-deep-dive-into-the-baltic-sea-cable-cuts/

42 people worked together intensively for two days and completed 10 projects during the #Greentech hackathon. Read about the outcomes on #RIPElabs 🌳

https://labs.ripe.net/author/becha/celebrating-green-tech-hackathon-results/

"In November, we shared our preliminary analysis of the analysis of the Baltic Sea cable cuts. Digging into the results of ping mesh measurements routinely performed by RIPE Atlas anchors, we were able to provide an initial sketch of how this affected connectivity between the countries at both ends of both cables."

Emile Aben, Jim Cowie and Alun Davies delve further into the Baltic Sea cable cuts on #RIPELabs #RIPEAtlas

https://labs.ripe.net/author/emileaben/a-deep-dive-into-the-baltic-sea-cable-cuts/

@meileaben @jimcowie

The double undersea cable cuts in the Baltic sea have been in the news over the weekend. But what was the impact on the Internet?
Emile Aben (@meileaben) and Alun Davies take a look at what #RIPEAtlas can tell us about this incident:

https://labs.ripe.net/author/emileaben/does-the-internet-route-around-damage-baltic-sea-cable-cuts/

#routing