This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Facebook in Russia and a diagnostic problem
- Previous message (by thread): [atlas] How to run the RIPE Atlas software probe on FreeBSD
- Next message (by thread): [atlas] Facebook in Russia and a diagnostic problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Mon Mar 14 10:09:35 CET 2022
Around half of the RIPE Atlas probes in Russia cannot complete a TLS session with facebook.com <https://atlas.ripe.net/measurements/39387725/>. (All the remaining tests have been done with the same set of probes, 'type': 'msm', 'value': '39387725'.) They have no problem with YouTube <https://atlas.ripe.net/measurements/39387839>. I also did TLS tests with IP addresses instead of names, same result <https://atlas.ripe.net/measurements/39387985> <https://atlas.ripe.net/measurements/39388031>. There is no lying DNS resolver <https://atlas.ripe.net/measurements/39387902>. But traceroute show no connectivity problem either, we can go to the Facebook AS from Russia <https://atlas.ripe.net/measurements/39388122> <https://atlas.ripe.net/measurements/39388176>. So, I'm a bit lost: what do we observe? It does not look like censorship but not like a connectivy issue (because of depeering by Cogent and Lumen) either.
- Previous message (by thread): [atlas] How to run the RIPE Atlas software probe on FreeBSD
- Next message (by thread): [atlas] Facebook in Russia and a diagnostic problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]