Location of probe controllers
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
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
More specifically, Fremont is in the San Francisco Bay Area, California. On 1/31/2022 0:44 AM, Robert Kisteleki wrote:
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
-- Paul Theodoropoulos www.anastrophe.com
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... , when Fremont has FET or CNE, respectively, as an IATA airport code: https://www.iata.org/en/publications/directories/code-search/?airport.search... Best, -C.
On 01/02/2022 12:39, Carsten Schiefner wrote: Hi Carsten,
On 31.01.2022 09:44, Robert Kisteleki wrote:
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...
, when Fremont has FET or CNE, respectively, as an IATA airport code:
Our apologies for this confusion. Controller names were initially characters from TV shows. Later, we began embedding location into them, using IATA codes. But IATA codes can be problematic in some cases. So we decided to use UN Locodes, as we do with RIPE Atlas anchors. The UN Locode for Fremont is "us-fnc". Unfortunately, we used just the location part of it, and did not include the country code, so the bare "FNC" looks like an IATA code. Regards, Anand Buddhdev RIPE NCC
Alright, understood - sort of… 😵💫
Am 01.02.2022 um 13:44 schrieb Anand Buddhdev <anandb@ripe.net>:
On 01/02/2022 12:39, Carsten Schiefner wrote:
Hi Carsten,
On 31.01.2022 09:44, Robert Kisteleki wrote:
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... , when Fremont has FET or CNE, respectively, as an IATA airport code:
Our apologies for this confusion. Controller names were initially characters from TV shows. Later, we began embedding location into them, using IATA codes. But IATA codes can be problematic in some cases. So we decided to use UN Locodes, as we do with RIPE Atlas anchors. The UN Locode for Fremont is "us-fnc". Unfortunately, we used just the location part of it, and did not include the country code, so the bare "FNC" looks like an IATA code.
Regards, Anand Buddhdev RIPE NCC
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
Anand Buddhdev writes:
<SNIP>... So we decided to use UN Locodes, as we do with RIPE Atlas anchors. The UN Locode for Fremont is "us-fnc". Unfortunately, we used just the location part of it, and did not include the country code, so the bare "FNC" looks like an IATA code.
For details about UN/LOCOD see the site <https://unece.org/trade/uncefact/unlocode>. jaap
Thanks, Jaap - On 01.02.2022 20:22, Jaap Akkerhuis wrote:
Anand Buddhdev writes:
<SNIP>... So we decided to use UN Locodes, as we do with RIPE Atlas anchors. The UN Locode for Fremont is "us-fnc". Unfortunately, we used just the location part of it, and did not include the country code, so the bare "FNC" looks like an IATA code.
For details about UN/LOCOD see the site <https://unece.org/trade/uncefact/unlocode>.
there is more stuff out there than one could possibly imagine... ;-) Best, -C.
participants (6)
-
Anand Buddhdev -
Carsten Schiefner -
Jaap Akkerhuis -
Malte Appel -
Paul Theodoropoulos -
Robert Kisteleki