- ripe-atlas - mailman.ripe.net

high volume IPs/anycasted?
by Jared Mauch 19 May '14

19 May '14

I have a few IPs on our network that are anycasted that I'd like to see the "9 limit" increased for, is there a proper way to do this? - Jared

1 0

Some UDM comments
by Jared Mauch 19 May '14

19 May '14

I'm working on creating some measurements and haven't quite moved into using the API yet and wanted to provide some feedback: 1) When creating a UDM, when it's scheduled but not yet assigned to probe(s), it would be nice to be able to increase the # of probes. 2) When creating a UDM and specifying source ASN, you can't type in that box and must use the pull-down. Related to #1, if you increase probes to (eg: 5) it resets to 1 after you select the ASN. 3) When stopping a UDM that is set for ongoing/no-end, it would be nice to have a 'stop now' vs having to pick the next 15 minute interval. In theory the system could auto-populate this. 4) I do like the probes/map/seismograph view, is it possible to provide a direct-link to these public UDMs without logging-in? (I haven't looked closely so there may be a way to do this). Trying to not need to fetch the data and generate my own graphs... 5) If I see a probe that is behaving poorly, eg: UDM 1665566 Probe# 3925, should I be providing feedback on this to others? I'm working on a Nx(N-1) measurement of these ASNs to determine which have persistent congestion that can be measured via RIPE Atlas if that is of interest to others. 174 209 701 1239 1299 2828 2914 3320 3257 3356 3491 3561 5511 6453 6461 7018 Those interested in this, I will be able to send you a list of UDMs to look at which are public. - Jared

4 4

NTT Communications (US) joined RIPE Atlas anchors
by Michela Galante 19 May '14

19 May '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called us-dal-as2914 and it is hosted by NTT Communications in Dallas, United States. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Taking the fuzz our of client cache results
by Mark Delany 17 May '14

17 May '14

Hi. I've been running some DNS queries using the probe caches with a view to understanding the latency between the probe cache and the authoritative that I'm interested in. The problem is that there is a fair degree of uncertainty in these measurements because the cache may have to first resolve higher level names in the hierarchy and there is no way of knowing whether the cache had to do this or not. If my query is for www.example.com, it's quite possible that the cache has to first resolve example.com prior to sending the final query for www. This means the measurement may include the cost of getting an answer from .com *and* getting the answer from example.com... sometimes. Depending on how popular example.com is and what other clients are doing with the cache. I'm wondering if there is a way in which we can eliminate this fuzziness? The most obvious way to do this is to ensure the cache is pre-primed with every answer up to, but not including the target name. If we assume the measurement request includes a new "prime cache" flag, then in the presence of that flag the probe could first run a query for something like: cacheprime.example.com substituting the first label with some other value. Alternatively it could first run an NS query for example.com A third alternative is that the creator of the measurement could nominate the priming query as they will have the knowledge needed to get it right. A forth alternative is that the probe could run the query twice - with a nominated delay that is known to exceed the TTL of the target query. In all cases, as soon as the priming query is complete, the probe then runs the target query with a high degree of confidence that the cache only needs to make one round trip to the authoritative server. There is still a small probability that the results will be fuzzy for a variety of reasons, multiple cache choices, anycast caches, super-busy caches, multiple probes using the same cache, but that probability will be very low. Also, a pre-primed query would presumably cost twice as many credits since it's really running two queries. Do others think a primed cache query is of use? And, are there ways of achieving this already? Mark.

2 2

Atlas API and IPv6
by Daniel Gomez 14 May '14

14 May '14

Hi All, Could it be that the API at atlas-ui.ripe.net is since last night not ipv6 reachable? We are not sure if it was before, but we had to change today the DNS Name to the ipv4, in order for the requests to work. Thanks in advance, Daniel El 14/05/2014 11:45, "Vesna Manojlovic" <BECHA(a)ripe.net> escribió: > Dear colleagues, > > There have been a lot of great examples recently of how RIPE Atlas can be > used to investigate network events, troubleshoot problems, explore how the > Internet behaves, and more. Some of the topics include: > > - Investigating customer complaints about slow servers > - Comparing TCP and UDP Response Times of DNS Root Servers > - Discovering Path MTU black holes on the Internet > > We’ve collected all of these user experiences, analyses, papers and > presentations in one place on RIPE Labs, in order to make it easy to > discover how others are making use of the RIPE Atlas network - and maybe > spark some ideas about how you can, too. > > https://labs.ripe.net/atlas/user-experiences > > If you have your own story about how you’ve used RIPE Atlas, we want to > hear from you! Please get in touch with us at atlas(a)ripe.net , > or on this list. > > Kind regards, > > Vesna Manojlovic > Measurements Community Building > RIPE NCC > > > > >

2 1

RIPE Atlas use cases and more
by Vesna Manojlovic 14 May '14

14 May '14

Dear colleagues, There have been a lot of great examples recently of how RIPE Atlas can be used to investigate network events, troubleshoot problems, explore how the Internet behaves, and more. Some of the topics include: - Investigating customer complaints about slow servers - Comparing TCP and UDP Response Times of DNS Root Servers - Discovering Path MTU black holes on the Internet We’ve collected all of these user experiences, analyses, papers and presentations in one place on RIPE Labs, in order to make it easy to discover how others are making use of the RIPE Atlas network - and maybe spark some ideas about how you can, too. https://labs.ripe.net/atlas/user-experiences If you have your own story about how you’ve used RIPE Atlas, we want to hear from you! Please get in touch with us at atlas(a)ripe.net , or on this list. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

DENIC eG (DE) has joined RIPE Atlas anchors
by Michela Galante 09 May '14

09 May '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called de-fra-as8763 and it is hosted by DENIC eG in Frankfurt, Germany. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Change of emailaddress/loginname for atlas
by Ivo van den Maagdenberg 05 May '14

05 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi people, The login to ripe-atlas is tied to an email adres, I'd like to change that very address. How is a change of emailaddress/loginname organised? I can't seem to find the way under https://atlas.ripe.net/my-atlas/ The FAQ https://atlas.ripe.net/about/faq/ doesn't mention it neither. Kind regards, Ivo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTZ48IAAoJEO8w8Dsjf0uUd0MH/3s9DQ/P4GLBs+Z+EbC++S7Z lxzfBgsF46CEsZjJTGG1KlFcuXGS1OUnCm6SrhMUAGOmHBZ/9jIlYtn7yWkc9uaL ZtMUFQ0x7ViDr7GY6HFWiGtbnO8Oi/Trh5DSHVOKFKpyeXgvK85L6nMesBkVKWmF A/i8f1KuTNB8bTAcNEeX5a3MsPzIOvI5k2Xq6HavuTUyWsxVlLUL3NSrc8Oba07d 6JleHQvjJl6UO6GNT0v8HhZaMlxLZ2ACzKm4sYvBJzrqJZ4KphFUvvulrYz3xKa9 YUTEFaBywwWFY/8mqsUS01asuMv6LeTRTGwZu++FAlETbFiqEElURo5dbEKiqRM= =FWOv -----END PGP SIGNATURE-----

2 1

Université catholique de Louvain (BE) has joined RIPE Atlas anchors
by Michela Galante 05 May '14

05 May '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called be-lln-as2611 and it is hosted by the Université catholique de Louvain in Louvain-la-Neuve, Belgium. Congratulations to the Université catholique de Louvain! This is the first anchor in Belgium! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Internal issues this morning
by Robert Kisteleki 02 May '14

02 May '14

Dear All, This morning we had internal difficulties in the system, which caused a slowly responding system in general, and in some cases failures when trying to get to data or scheduling new measurements. System operations are now back to normal. We have identified the root cause for the issue and will implement mitigations for it. Sorry for the inconvenience this may have caused, Robert Kisteleki RIPE NCC

1 0

ADP (FR) has joined RIPE Atlas anchors
by Michela Galante 29 Apr '14

29 Apr '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called fr-tin-as196670 and it is hosted by ADP in Pantin, France. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

SuperNetwork (CZ) has joined RIPE Atlas anchors
by Michela Galante 28 Apr '14

28 Apr '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called cz-prg-as39392 and it is hosted by SuperNetwork in Prague, Czech Republic. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

V3 Probes
by Cobus Viljoen 25 Apr '14

25 Apr '14

Hi Guys, wonder if anyone can tell me where i'm going wrong. but i have received these probes and i cant seem to get them working. they have been registered, but leaving them connected just doesn't show up on the site under my probes. they are getting ip's via dhcp and have access to the internet so i cant really see why they are not showing up any advise would be greatly appreciated Cobus.

2 1

network coverage and probe API
by Bajpai, Vaibhav 23 Apr '14

23 Apr '14

Hello, The network coverage page [1] shows around 10K+ registered probes. However, if I call the probe API [2], the total_count field shows 8K probes. Probe objects also have is_public field, so I assume the API counts both public and private probes. There is also a status field, so I assume the API counts connected, disconnected and abandoned probes as well. What am I missing? [1] https://atlas.ripe.net/results/maps/network-coverage [2] https://atlas.ripe.net/api/v1/probe Best, Vaibhav ----------------------------------------------------- Vaibhav Bajpai Research I, Room 86 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com

5 7

one-off traceroute and interval parameter
by Bajpai, Vaibhav 16 Apr '14

16 Apr '14

Hello, Traceroute UDMs include an interval parameter. If I provision a one-off traceroute UDM via the GUI wizard, the interval field should get disabled no? Once the measurement is completed, the general information tab for the UDM now shows the interval for a one-off measurement as 900s. PS: We understand the interval parameter may have made no difference to the actual measurement. This is more of a bug report for visual side of things. Best, Vaibhav ----------------------------------------------------- Vaibhav Bajpai Research I, Room 86 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com

1 0

v2 in anchorv2
by Bajpai, Vaibhav 15 Apr '14

15 Apr '14

Hello, We have a RIPE atlas anchor question. Can you please tell us the reason for using v2 in anchorv2? We went to [2], but that doesn’t exist. We also searched but couldn’t find documentation on this. [1] http://anchorv2.ripe.net [2] http://anchorv1.ripe.net PS: We understand what RIPE atlas anchors do :-) Best, Vaibhav ----------------------------------------------------- Vaibhav Bajpai Research I, Room 86 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com

2 1

Related to Rip Atlas Credit System
by Roya Ensafi 14 Apr '14

14 Apr '14

Hi all, Considering RIPE Atlas credit system, ping and tracerout unit cost calculations are tricky. It closely depends on number of packets in train and size of the packets. Based on [1], predicted cost of a traceroute measurement with sent packet size of 2040 and 3 as number of packets (detail arguments are bellow) should be 10*3*(int(2040/1500)+1) = 90 (refer to [1]). However, predicted cost calculated by RIPE server is 120. After looking at available JavaScript, we couldn't find the predicted cost calculation. It sounds like calculation happens on server side and then the the value is returned. Is it possible to check the server code i.e. is the cost function calculation on server side publicly available? Thanks, Roya Enasfi [1]: https://atlas.ripe.net/docs/credits Details for a traceroute measurement : (Per result: 120.0 credits, Estimated total cost: 120 credits) Arguments: (Interval: 900 seconds, Resolve on probe: No, First hop: 1, #packets: 3, Don't fragment: True, Max hops: 32, Tcp: True,Paris: 16, Timeout resp.(ms): 4000, Port: 80, Size: 2040)

2 1

APNIC (AU) has joined RIPE Atlas anchors
by Michela Galante 14 Apr '14

14 Apr '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called au-bne-as4608 and it is hosted by APNIC in Brisbane, Australia. This is the second anchor hosted by an RIR on behalf of the RIPE NCC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

"Invalid group id" for Restful API?
by Philipp Winter 11 Apr '14

11 Apr '14

I'm trying to create a measurement using Atlas' Restful API [1]. Before that, I created an API key for measurement creation. Using my API key, when executing the simple example shown in [1], the server tells me: > {"error": {"code": 104, "message": "group: Invalid group id"}} I get the same error code with different JSON-formatted queries. Any ideas what's going on here? [1] https://atlas.ripe.net/docs/measurement-creation-api/ Cheers, Philipp

4 4

Using ripe data results on publications?
by Daniel Gomez 08 Apr '14

08 Apr '14

Good Morning everyone, What is the policy about using ripe atlas results on articles and publications? We know atlas is a great infrastructure to perform measurements, but we can find on them , i.e. traceroute, private IPs from atlas hosts networks. I know there is a lot of people on this list concerned about making public some information. Are atlas results open to share and so the probes information? Greetings, Daniel Gomez

2 1

Probe IPs are public?
by Roman Mamedov 08 Apr '14

08 Apr '14

Hello, I was under impression RIPE tries to somewhat anonymize probe information that's displayed publicly, e.g. only showing the probe IP address information down to the subnet or AS level on the maps, providing the option to use "Obfuscated DNS entry", etc. But on the public stats pages e.g. here: https://stat.ripe.net/widget/atlas-probes#w.resource=DE (+ "switch to table view") I am able to see both IPv4 and IPv6 addresses of many or most probes without even having to log-in; is that intended? Also what is the point of choosing to use the Obfuscated DNS option if the probe IPs are available in the clear anyway. -- With respect, Roman

4 3

Net Neutrality measurements
by Georg Chytil 31 Mar '14

31 Mar '14

Dear collegues, I sympathize with the cause for net measurements, and the RIPE Atlas project in particular. I´d like to draw your attention to the use of net measurement infrastructure as a means of documenting net neutrality, and a consulation of BEREC in this context: http://berec.europa.eu/eng/news_consultations/ongoing_public_consultations/… I´d appreciate if RIPE got involved in this field before less desireable and competent parties do ;-) Maybe comment on net neutrality on https://atlas.ripe.net/about/future-plans/ ? Kind Regards #g

3 2

Use case for RIPE Atlas: DNS service disruption in Turkey
by Vesna Manojlovic 31 Mar '14

31 Mar '14

Dear all, one of our most active users, Stephane Bortzmeyer, performed RIPE Atlas (and other) measurements to collect the data for his analysis, published in a blog post yesterday: "Hijacking of public DNS servers in Turkey, through routing" http://www.bortzmeyer.org/dns-routing-hijack-turkey.html Thank you for this interesting use-case! This is a call for the rest of the community to let us know if you have done some measurements or analysis to solve your problem, or to better understand a network-event - please share it with us. We are also interested in re-publishing your stories on RIPE Labs. You can find the previous articles here: https://labs.ripe.net/atlas Regards, Vesna

1 1

LACNIC (UY) has joined RIPE Atlas anchors
by Michela Galante 28 Mar '14

28 Mar '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called uy-mvd-as28000 and it is hosted by LACNIC in Montevideo, Uruguay. Congratulations to LACNIC! This is the first anchor in Latin America and the first one hosted by an RIR on behalf of the RIPE NCC. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

MWEB (ZA) has joined RIPE Atlas anchors
by Michela Galante 26 Mar '14

26 Mar '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called za-jnb-as10474 and it is hosted by MWEB in Johannesburg, South Africa. Congratulations to MWEB! We have now a total of 50 active RIPE Atlas anchors! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0