Identify RIPE Atlas Measurements which would benefit us

[Firefishy]

RIPE Atlas measurements are a useful way probe for connectivity issues from the greater Internet.

RIPE Atlas allows user defined measuring / monitoring using Ping, Traceroute, DNS and NTP endpoint connectivity tests from 1000s of probes distributed across the internet. HTTP/HTTPS is additionally available only if the endpoint is an "anchor" device, which is currently not in scope for us.

The probes used for monitoring can be selected based on Area, Country, IP Prefix, ASN, or any combination of these. The endpoint can be any IPv4 or IPv6 address we specify. Using more probes uses up more RIPE Atlas probe credits

Measurements can be run one-off or a recurring interval.

There is an existing Prometheus RIPE Atlas exporter.

Both @Firefishy and @pnorman have more than sufficient RIPE Atlas monitoring credits for running a Proof of Concept. Credits can be transferred between accounts. Credits are generally acquired by hosting a probe or anchor.

The goal would likely be to create something like the current Ping Time and Packet Loss monitoring, but from the greater Internet.

[mmd-osm]

I remember some reports from mappers (presumably) located in the Philippines who were complaining about high latency times and laggy UIs in iD/Rapid. It would be good to include our API endpoints in the measurements and maybe share any findings with maintainers of editor apps.