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] Location of probe controllers
- Previous message (by thread): [atlas] Location of probe controllers
- Next message (by thread): [atlas] Location of probe controllers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Mon Jan 31 09:44:00 CET 2022
Hello, On 2022-01-28 09:55, Malte Appel 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. Cheers, Robert
- Previous message (by thread): [atlas] Location of probe controllers
- Next message (by thread): [atlas] Location of probe controllers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]