- ripe-atlas - mailman.ripe.net

Using RIPE Atlas for monitoring: introducing "Status Checks"
by Vesna Manojlovic 12 Feb '14

12 Feb '14

Dear colleagues, After having some of you testing Status Checks, we are now introducing this new feature to all users. It allows you to integrate RIPE Atlas into any monitoring tool you currently use, such as Nagios or Icinga. Please find a new article on RIPE Labs that explains simple steps, gives an example, and points to our future plans: https://labs.ripe.net/Members/suzanne_taylor_muzzin/introducing-ripe-atlas-… Direct link to Status Checks: https://atlas.ripe.net/docs/status-checks/ We are pleased to announce this feature that the operators community has been asking for, and we are looking forward to both your feedback and success stories. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 0

Some of the UDM results are unavailable
by Eravuchira, Steffie Jacob 12 Feb '14

12 Feb '14

Dear community, I am trying to access some of the the UDMs. I find some problems in getting results for some probes in some UDM. For example, I can access the UDM [1] and get measurements from all the probes. Whereas when I try to filter the same UDM using probe ID, the result is not available for some particular probes [2]. But it is available for some others [3] in the same UDM. [1] https://atlas.ripe.net/api/v1/measurement/1037214/result/ [2] https://atlas.ripe.net/api/v1/measurement/1037214/result/?prb_id=2330 [3] https://atlas.ripe.net/api/v1/measurement/1037214/result/?prb_id=12781 Kind Regards, Steffie

3 2

SIDN (NL) has joined RIPE Atlas anchors
by Michela Galante 06 Feb '14

06 Feb '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 nl-arn-as1140 and it is hosted by SIDN in Arnhem, Netherlands. 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

Hringiðan (IS) has joined RIPE Atlas anchors
by Michela Galante 03 Feb '14

03 Feb '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 is-rey-as25509 and it is hosted by Hringiðan in Reykjavik, Iceland. 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

New on RIPE Labs: Increased Reach of RIPE Atlas anchors
by Michela Galante 29 Jan '14

29 Jan '14

Dear colleagues, Please take a look at the latest features and the new plans for RIPE Atlas anchors in the RIPE Labs article published today, "Increased Reach of RIPE Atlas anchors": https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-anchors-janu… If you wish to apply for an anchor, the requirements and other useful information are available online at: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Kind regards, Michela Galante Measurements Community Building RIPE NCC

1 0

Linking to measurements?
by Brian Rak 28 Jan '14

28 Jan '14

Is there any real way to send someone a link to a measurement? I've figured out how to send them links to individual RRD detail pages (https://udm01.atlas.ripe.net/atlas/udm_graph_history.html), but not a link to the overall public measurement. The UI is all AJAXy, so I haven't seen any obvious places to pull a link out of.

3 3

BIX (HU) has joined RIPE Atlas anchors
by Michela Galante 28 Jan '14

28 Jan '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 hu-bud-as12303 and it is hosted by BIX in Budapest, Hungary on behalf of RIPE NCC since they are one of our K-root hosts. 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

Rezopole/LyonIX (FR) has joined RIPE Atlas anchors
by Michela Galante 27 Jan '14

27 Jan '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-vbn-as199422 and it is hosted by Rezopole/LyonIX in Lyon, 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

Aivivid (SE) has joined RIPE Atlas anchors
by Michela Galante 21 Jan '14

21 Jan '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 se-sto-as59521 and it is hosted by Aivivid in Stockholm, Sweden. 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

measurement start_time and stop_time fields
by Matt Calder 17 Jan '14

17 Jan '14

Hi, For the filter fields such as start_time__lt, stop_time__gte the API at https://atlas.ripe.net/docs/rest/ claims that a unix timestamp should be valid for these but I am seeing the error message "'1389655981' value has an invalid format. It must be in YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format." I was trying with this query: https://atlas.ripe.net/api/v1/measurement/?limit=20&type=2&format=txt&use_i… Thanks, Matt

2 2

probe status "abandoned" - "garbage collect" attempt?
by Wilfried Woeber 16 Jan '14

16 Jan '14

Dear community, as a side-effect of looking at maps and country-related info, I recognised that there's a considerable number of probes in our country which are marked as "abandoned". We may be able to follow up on some of them. Looking at https://stat.ripe.net/widget/atlas-probes#w.resource=AT and switching to table view, I'm missing the AS# column. Being able to search for "our" ASes would be nice. Thanks, Wilfried PS: a text / table version that can be saved locally and then subjected to a 'grep' would be nice, too. PPS: the sort function by address family is really nice!

4 4

"funny" comment in pop-up display for a measurement? (v4/v6 addr mismatch)
by Wilfried Woeber 16 Jan '14

16 Jan '14

Some more digging and some more confusion? Logged in, looking at "My measurements", selecting 1033944, a traceroutev6. Bringing up the Map tab, clicking on the green balloon in Bremen (Probe ID 13255) with the *2* (hops) in it, pop-up comes up. Nice! But the *-comment at the bottom puzzles me, by saying: * The last address does not match the target IP (192.153.174.196) This is sort of obvious, as the address referred to is 2001:6f8:114e:4::1 What's the background for this behaviour? Wilfried

3 4

FICIX (FI) has joined RIPE Atlas anchors
by Michela Galante 16 Jan '14

16 Jan '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 fi-hel-as3292 and it is hosted by FICIX in Helsinki, Finland on behalf of RIPE NCC since they are one of our K-root hosts. 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

UDM display, session expiration
by Wilfried Woeber 16 Jan '14

16 Jan '14

Just an observation... I started a TR6 connectivity measurement against our Anchor, late in the evening yesterday and had the measurement panel open. Trying to reload today I was left with the "fan" spinning, not showing anything. It turns out, that my session was expired and trying to pull up the summary got me logged-in again. Then the reload for #1410005 also worked again. I am wondering, whether it would be possible to "force" a re-login by hitting the "reload" button on top-right of the measurement display panel? Cheers, Wilfried

2 1

Atlas credits
by Imre Szvorenyi 15 Jan '14

15 Jan '14

Hey Guys, Just a small thing I've noticed recently. When I open the 'My Atlas -> Credits' submenu, the number of current credits with big blue numbers are different to (less than) the one that can be seen in the History->Balance lines under it. Please note that I have no running jobs or anything like that. I'm hosting 3 probes, and by the look of the history, my credits are updated after 2. Is this a bug or I just missed something, please? [image: Inline image 1]

2 1

(no subject)
by Eravuchira, Steffie Jacob 15 Jan '14

15 Jan '14

Hi, There are three hardware versions of RIPE Atlas probes namely v1,v2 and v3. Each of the support different firmware versions. Can I get the latest firmware version supported by each the hardware versions? Thanks, Steffie

4 6

BelWü/Universität Stuttgart (DE) has joined RIPE Atlas anchors
by Michela Galante 15 Jan '14

15 Jan '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-str-as553 and it is hosted by BelWü/Universität Stuttgart in Stuttgart, 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

synch delay for Coverage Map?
by Wilfried Woeber 15 Jan '14

15 Jan '14

Hi folks, just out of curiosity, what are the intervals or the delay for updates to the "Global RIPE Atlas Network Coverage" map? [1] We just got the 1st probe connected in Cuba, thanks to the ambassador program, and I can see it as on-line. But it is not yet visible on the Coverage Map. Cheers, Wilfried [1] https://atlas.ripe.net/results/maps/network-coverage/

3 3

Newest RIPE Atlas features - seismograph improvements & more
by Vesna Manojlovic 15 Jan '14

15 Jan '14

Dear colleagues, We are proud to announce the latest features added to RIPE Atlas in the previous few months: - time selection in seismograph: zoom, and calendar menu; - filtering probe by country & ASN on maps & seismograph - one-off SSL measurements ... and much more! Please find out the details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-update-janua… We are looking forward to your feedback! Regards, Vesna -- Measurements Community Building team RIPE NCC

1 0

Poznan Supercomputing and Networking Center (PL) has joined RIPE Atlas anchors
by Michela Galante 14 Jan '14

14 Jan '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 pl-poz-as9112 and it is hosted by Poznan Supercomputing and Networking Center in Poznan (Poland) on behalf of RIPE NCC since they are one of our K-root hosts. 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

Measurement history "smoke ping style"
by Alex Saroyan 13 Jan '14

13 Jan '14

Hi, There is very useful "smoke ping style" RTT history for all Built-in measurements but I can't find such for User Defined Measurements (seismograph is not the same). I hope that such "smoke ping style" history/graph is available and I simply can't find it. If really no - then I desperately wish such feature to be implemented by Atlas team. -- Regards. /Alex Saroyan

1 0

RIPE Atlas 2013: A Year in Review
by Michela Galante 13 Jan '14

13 Jan '14

Dear colleagues, 2013 was an exciting year for RIPE Atlas. Take a look at what you helped us to achieve in 2013, in the new article on RIPE Labs: https://labs.ripe.net/Members/michela_galante/ripe-atlas-2013-year-in-review Kind regards, Michela Galante Measurements Community Building RIPE NCC

1 0

University of Tokyo/WIDE BB (JP) has joined RIPE Atlas anchors
by Michela Galante 13 Jan '14

13 Jan '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 jp-tyo-as2500 and it is hosted by University of Tokyo/WIDE BB in Tokyo (Japan) on behalf of RIPE NCC since they are one of our RIS-RRC locations. 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

Proposing more public RIPE Atlas data and clarifying the current situation
by Vesna Manojlovic 10 Jan '14

10 Jan '14

Dear colleagues, Sharing information about Internet performance is at the heart of collaborative efforts such as RIPE Atlas. Most of the RIPE Atlas probes and RIPE Atlas measurements are already public, and we'd now like to suggest opening up the publication of RIPE Atlas data further. We also want to clarify exactly what is and isn't public in the current system. We describe this in more detail in this RIPE Labs article, where we also ask for community feedback about our suggested plan to move forward: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… Our proposed plan is to make all *new* measurements and technical information about the *new* probes public from an agreed upon date in the future. We propose implementing this change in mid-April. All probes and measurements that were not marked "public" by April 2014 would remain non-"public". For a detailed description of what this means, please see the RIPE Labs article (above). Although we believe that having public measurement data contributes to the goal of RIPE Atlas, the RIPE NCC greatly values our users' privacy. We want to ensure you that we will continue to protect our probe hosts' personal information. We look forward to your feedback and comments on the MAT Working Group Mailing List. Regards, Vesna Manojlovic Senior Community Builder Measurements Community Building RIPE NCC

12 18

call for help or ptr to doc - saving graphs?
by Wilfried Woeber 10 Jan '14

10 Jan '14

Apologies, if this has been discussed before or should be obvious from some documentation... So here we go: In the "good old days" (no I prefer the current state :-) ) it was asy to get hold of the extended graphs by simply clicking onto the graph in the summary page and then do "save" or "save as". Since the (better, interactive,...) graphs are generated locally, I failed to come up with a method to "get hold" of the graph, for storing locally, printing, whatever. I just today tried to hit "print" in the browser, but the page seems to be inadequately structured/formatted for printing. The result is gaebage all over. Does anyone have a pointer or suggestion for me, sort of "better" than doing a screen shot and then work with the pixels? TIA, Wilfried

2 2