[atlas] Location of probe controllers
- Previous message (by thread): [atlas] Can't access the serial in SOA records from the API
- Next message (by thread): [atlas] Location of probe controllers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Malte Appel
malte at iij-ii.co.jp
Fri Jan 28 09:55:08 CET 2022
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 information about that. My guesses from the DNS names are based on IATA airport codes: ctr-ams02.atlas.ripe.net (Amsterdam, NL) ctr-ams03.atlas.ripe.net (Amsterdam, NL) ctr-ewr01.atlas.ripe.net (Newark, NJ, US) ctr-fnc01.atlas.ripe.net (Funchal, PT) ctr-nue13.atlas.ripe.net (Nürnberg, DE) ctr-nue17.atlas.ripe.net (Nürnberg, DE) ctr-sin02.atlas.ripe.net (Singapore, SG) Can anyone confirm or correct these locations? Best, Malte -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x877CEAFF9EA25E92.asc Type: application/pgp-keys Size: 3139 bytes Desc: OpenPGP public key URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20220128/3d75c47e/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20220128/3d75c47e/attachment.sig>
- Previous message (by thread): [atlas] Can't access the serial in SOA records from the API
- Next message (by thread): [atlas] Location of probe controllers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]