- ripe-atlas - mailman.ripe.net

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