- ripe-atlas - mailman.ripe.net

Selecting only anchors for UDM
by Ondřej Caletka 12 Jun '14

12 Jun '14

Hello list, is there a way to run an UDM on Anchors only? I think it would be a good feature, especially for precise latency measurement. Cheers, Ondřej Caletka

10 18

Using RIPE Atlas to Debug Network Issues
by Vesna Manojlovic 12 Jun '14

12 Jun '14

Dear colleagues, Please find the use-case for RIPE Atlas in debugging network issues, in this RIPE Labs article written by Tim Kleefass from BelWü, who is hosting a RIPE Atlas anchor. (and who holds the record for the shortest time from purchasing the anchor to it going live!) https://labs.ripe.net/Members/tim_kleefass/how-fast-the-ripe-atlas-anchor-h… Regards, Vesna

1 0

Speed tests?
by Brian Rak 11 Jun '14

11 Jun '14

Are there any plans to allow testing download speed from the probes? I guess this could cause problems for people who have the probes on metered bandwidth plans.

12 12

Lemuria Communications (US) has joined RIPE Atlas anchors
by Michela Galante 10 Jun '14

10 Jun '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-as7366 and it is hosted by Lemuria 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

Empty from feild
by john 06 Jun '14

06 Jun '14

Hello All, Quick question about the data format. What would cause a measurement to have an empty from field but contain data? An example would be probe_id 13663 from measurement 1672218[1]. A cursory glance seems to happens a lot more with V6 Thanks John [1]https://atlas.ripe.net/api/v1/measurement-latest/1672218/

3 4

NTT Communications (US, Seattle and Atlanta) have joined RIPE Atlas anchors
by Michela Galante 06 Jun '14

06 Jun '14

Dear RIPE Atlas users, We're happy to announce that two more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors, both hosted by NTT Communications in United States, are: us-sea-as2914, in Seattle us-atl-as2914, in Atlanta Congratulations to NTT Communications for their third and forth anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors 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

A collection of tools in Perl
by Stephane Bortzmeyer 04 Jun '14

04 Jun '14

https://github.com/pierdom/atlas-toolbox

3 2

RIPN (RU) has joined RIPE Atlas anchors
by Michela Galante 03 Jun '14

03 Jun '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 ru-mow-as15835 and it is hosted by RIPN in Moscow, Russia. 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

Changes to the Distribution Model for RIPE Atlas Probes
by Vesna Manojlovic 03 Jun '14

03 Jun '14

Dear colleagues, we have made some adjustments in the distribution model of RIPE Atlas probes to ensure wider topological and geographical probe coverage. Please read more in this RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/changes-to-the-distribution-mode… Regards, Vesna

1 0

Probe not showing IPv6 ASN and subnet on map
by JC 02 Jun '14

02 Jun '14

Hi, We just setup our probe (id: 17328) and configured static IPv6 on it. Built-in measurements to IPv6 destinations seems to perform correctly from this probe. However, when we display detailed information about the probe on the coverage map https://atlas.ripe.net/results/maps/network-coverage/ we only see IPv4 information and no IPv6 subnet or ASN. Besides, searching for our IPv6 ASN (21538) in the filter field brings no results. Thanks for your help. Regards, JC

2 1