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/[email protected]/
[atlas] Location of probe controllers
- Previous message (by thread): [atlas] How to measure ISP speed/uptime via Atlas Probes
- Next message (by thread): [atlas] Location of probe controllers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carsten Schiefner
carsten at schiefner.de
Tue Feb 1 12:39:04 CET 2022
Hi Robert, On 31.01.2022 09:44, Robert Kisteleki wrote: >> 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? > > It is mostly correct: fnc is Fremont, US west coast. is this the proverbial exception to the rule? As FNC indeed stands for Funchal: https://www.iata.org/en/publications/directories/code-search/?airport.search=FNC#searchForm , when Fremont has FET or CNE, respectively, as an IATA airport code: https://www.iata.org/en/publications/directories/code-search/?airport.search=fremont#searchForm Best, -C.
- Previous message (by thread): [atlas] How to measure ISP speed/uptime via Atlas Probes
- Next message (by thread): [atlas] Location of probe controllers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]