Hi Jacques,
seems about right: https://atlas.ripe.net/api/v2/probes?asn_v4=34659
The two disconnected probes seem abandoned and are disconnected since
several years, so I would not count on them coming online again.
Best,
Malte
On 2022-05-29 04:30, Jacques Lavignotte wrote:
Hi,
I may be wr
Hi,
I was looking at the built-in traceroute measurements and noticed additional
targets (ctr-*.atlas.ripe.net) apart from the DNS root servers. As I understand
it, these are the controllers for the probes. However, I was wondering where
they are physically located and could not find any clear in
Hi Johan,
thank you very much for the detailed response!
On 11/17/21 20:30, Johan ter Beest wrote:
[huge snip]
Thank you again for bringing this to our attention. We're working hard to fix
the issues. If you feel I have not addressed some of your issues, please let me
know.
I believe you h
Hi everyone,
sorry in advance for the long mail.
tl;dr: Anchor API and UI give inconsistent results. Some anchor mesh
measurements could be fixed, some might target non-anchors. Not sure what to do
about it.
I am currently working a lot with RIPE Atlas and recently wanted to use the
anchors and
Hi Ray,
On 23/04/2021 17:44, Ray Bellis wrote:
Can you please elaborate on this?
I have a separate need (relating to an ICANN RSSAC WG) to be able to
detect high latency last mile hops but I could not identify the specific
"built-in ping tests for 1st and 2nd hop" that you described.
You can
