- ripe-atlas - mailman.ripe.net

Logistics Q: probe "owner" leaving an organisation, but probe remains
by Wilfried Woeber 18 Feb '14

18 Feb '14

Hi folks, maybe there's already an FAQ answer somewhere or it has been discussed before, and I missed it. Please point me into the right direction :-) Background: I handed out a probe (from an ambassador batch) and the probe was connected to the 'net. Now, a rather short while later, the "owner" of that probe left the organisation, and left the probe behind. It is still connected :-) What is the procedure or advice for assigning a new "owner" from the hosting organisation? Thanks, Wilfried

1 0

Denial of Measurement
by Sebastian Castro 18 Feb '14

18 Feb '14

Hi: Trying to investigate a problem with one of our boxes, I came across the following error message: "10 UDMs are already measuring 202.46.187.130/2001:dce:7000:2:0:0:0:130. Cannot add 1 more" What I did was to add a one-off DNS UDM to ns2.dns.net.nz, to track if reachability was OK, but I can't because someone else is already doing that. None of those UDMs is mine, so effectively someone created a "Denial of Measurement" against me. Any recommendations what to do about this? Cheers, -- Sebastian Castro Technical Research Manager .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

2 1

CERN (FR) has joined RIPE Atlas anchors
by Michela Galante 17 Feb '14

17 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 fr-prm-as513 and it is hosted by CERN in Prévessin-Moëns, France on behalf of RIPE NCC since they are one of our k-root hosts and RIS Remote Route Collector 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

VIX (AT) has joined RIPE Atlas anchors
by Michela Galante 13 Feb '14

13 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 at-vie-as1120 and it is hosted by VIX in Vienna, Austria on behalf of RIPE NCC since they are one of our RIS Remote Route Collector 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

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

graph generation stopped on 9.1.2014
by Wilfried Woeber 09 Jan '14

09 Jan '14

It looks like the generation of graphs to be displayed on the summary page for my probes stopped at some point in time, today, Jan. 9. Before around noon it was working, now they are gone. Probes affected: 414, 466, 6009 Any hints? Wilfried

1 1

Atlas F.ROOT ping
by Peter Gervai 09 Jan '14

09 Jan '14

Hello, Atlas helped me today first to see a hard-to-detect bug: F-root anycast algo works fine for v4 but fails miserably for v6, as instead of AMSterdam it sends all traffic to some remote island in the pacific. ;-) Seems to be the reverse true for M-root: ipv4 sends me off to nowhere land while v6 is great. A-root follows the F-suit. (C-root is not a good avertisement valie for Cogent, with v4 only address and considerable ongoing pkt loss.) Thanks! Peter

4 5

Fwd: [service] Technical Outage Resolved
by Vesna Manojlovic 09 Jan '14

09 Jan '14

Dear colleagues, RIPE NCC has experienced outage, and some RIPE Atlas probes were also affected. We will send more information tomorrow, as we assess the extent of the impact. Regards, Vesna -------- Original Message -------- Subject: [service] Technical Outage Resolved Date: Wed, 08 Jan 2014 18:18:46 +0100 From: Nick Hyrka <nick(a)ripe.net> To: ncc-announce(a)ripe.net CC: ripe-list(a)ripe.net Dear colleagues, At 15:45 Amsterdam time, the RIPE NCC experienced a technical outage affecting a number of our services. >From 16:15, we were able to recover some services and by 17:45 all were fully functional. We apologise for any inconvenience this may have caused. Regards, Nick Hyrka Communications Manager RIPE NCC

2 1

Updated RIPE Atlas roadmap
by Vesna Manojlovic 30 Dec '13

30 Dec '13

Dear colleagues, we have considered the feedback we have received from you in the previous few months, on this list and MAT-wg mailing list, and last week we have made an updated version of the roadmap: http://roadmap.ripe.net/ripe-atlas/ We have added few new items under "requested features", and shifted some of the previously requested and planned towards "in progress". We are updating this document every two months, so you can expect newer requests to be added early next year. Regards, Vesna

6 9

probe information - useful feature?
by Gilles Massen 24 Dec '13

24 Dec '13

Hi, With a few measurements I was stumbling about probes returning 'unexpected' results (e.g. having DNS responses rewritten). I was wondering if it made sense to provide a way to add information to probes that are somehow 'noteworthy'. Just adding free comments to probes could be enough. The reason is not to lose time each time someone stumbles over the results and has to investigate the specifics over and over again. The probe selection does not have to be affected - after all the weirdness is part of the internet. It shouldn't either result in some kind of blaming, only information sharing. Additionally a probe host could be notified if some text is added to his probe (he might not be aware after all). Thoughts? Best, Gilles

2 1

ISNIC (IS) has joined RIPE Atlas anchors
by Michela Galante 24 Dec '13

24 Dec '13

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-as1850 and is hosted by ISNIC 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 ---------------------- The RIPE Atlas Team wishes you happy holidays and all the best for 2014! https://atlas.ripe.net/media/community/action/originals/RIPE-Atlas-Christma…

1 0

SURFnet (NL) has joined RIPE Atlas anchors
by Michela Galante 23 Dec '13

23 Dec '13

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-ams-as1101 and is hosted by SURFnet in Amsterdam, 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 ---------------------- The RIPE Atlas Team wishes you happy holidays and all the best for 2014! https://atlas.ripe.net/media/community/action/originals/RIPE-Atlas-Christma…

1 0

BGP hijacking
by Bogdan Arvunescu 20 Dec '13

20 Dec '13

Hello Lukasz, thank you for reporting the problem with the six /8s originated by our AS. For future notice, please note that our company has a response time of 15 minutes to e-mails sent to noc(a)adnettelecom.ro aut-num: AS5541 [...] remarks: E-mail NOC: noc(a)adnettelecom.ro We have been notified by one of our customers that you have sent several e-mails to the ripe-atlas mailing list related to our company. We have investigated the problem reported and noticed that last night, while enabling our BGP session with AS6939 an error in the config caused the announcement of six /8s. The problem is now fixed and the colleague with the fat fingers will have to eat within the next hour 0.000001 Christmas candies for each IP in the rogue announcements. We wish you a Merry Christmas! and ask you to send us an e-mail to noc(a)adnettelecom.ro if you see any problem originated from our AS in the future. Best regards, Bogdan -- Best regards, Bogdan *Help us improve Technical Support <http://www.adnettelecom.ro/feedback-suport-tehnic/> , Service Delivery <http://www.adnettelecom.ro/feedback-livrare-servicii/>* -- *Bogdan Arvunescu* Senior Network Engineer phone: +40-21.527.37.37 mobile: +40-737.999.009 fax: +40-21.320.61.18 e-mail: bogdan.arvunescu(a)adnet.ro AdNet Telecom 96B Basarabia Blvd, District 2 022121, Bucharest, Romania www.adnettelecom.ro <http://www.adnettelecom.ro> www.datacity.ro <http://www.datacity.ro> www.adnettv.ro <http://www.adnettv.ro>

1 0

BGP hijacking
by Lukasz Trabinski 20 Dec '13

20 Dec '13

Hi I know that is not related with RIPE atlas, but maybe do know where to report in RIPE BGP hijacking topic? >From today BGP table: 46.0.0.0/8 xx 33 6939 5541 I 77.0.0.0/8 xxx 33 6939 5541 I 89.0.0.0/8 xxx 33 6939 5541 I 91.0.0.0/8 xxx 33 6939 5541 I 94.0.0.0/8 xxx 33 6939 5541 I 95.0.0.0/8 xxx 33 6939 5541 I

4 4

SOX (RS) has joined RIPE Atlas anchors
by Michela Galante 20 Dec '13

20 Dec '13

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 rs-beg-as13004 and is hosted by SOX (Serbian Open eXchange) in Belgrade, Serbia. 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

DANTE (UK) has joined RIPE Atlas anchors
by Michela Galante 19 Dec '13

19 Dec '13

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 uk-lcy-as20965 and is hosted by DANTE in London, United Kingdom. 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

ATE (FR) has joined RIPE Atlas anchors
by Michela Galante 17 Dec '13

17 Dec '13

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-zdb-as35625 and is hosted by ATE in Sainghin en Mélantois, 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

Emergency RIPE Atlas firmware upgrade
by Robert Kisteleki 17 Dec '13

17 Dec '13

Dear RIPE Atlas users, We want to let you know about a recent issue in the RIPE Atlas system involving an open port on the latest generation (v3) probes. Due to an issue with the latest firmware release, a subset of the v3 probes were listening to incoming connections on an open port that should not have been left open. As a secondary measure, however, access to this port required credentials only available to the RIPE Atlas probe developers. It therefore never presented open access to the probes. This port (SSH) is used for development purposes in our internal development environment. We upgraded the v3 probes to a new, corrected firmware version, and improved the checks in our firmware release process. We would like to thank ZeelandNet for reporting the issue to us. We want to assure you that the security of the RIPE Atlas system is important to us. We are continually improving the controlling infrastructure as well as the probes themselves in order to prevent vulnerabilities. We apologise for this issue and want to stress that no probes were actually affected in any way. You can learn more about the security of the RIPE Atlas system on our dedicated security page at: https://atlas.ripe.net/docs/security/ Thank you for your continuing support of RIPE Atlas. Regards, Robert Kisteleki RIPE NCC

10 17

IPv6 Gateway Undetermined/Unknown
by Christopher Werny 17 Dec '13

17 Dec '13

Hi Everybody, we received our probe a couple of days ago and after successful "deployment" (with static configuration), I noticed that the Configuration pane states that the IPv6 gateway is in the state "Undetermined/Unknown". It is correctly configured and IPv6 measurements are working fine. I couldn't find anything related to my "observation", hence why I am asking here. I just want to make sure I did everything right and whether this might be a known bug or limitation? Thanks for your time. Cheers, Christopher

2 1

Enjoy the holiday season with photos of RIPE Atlas probes
by Vesna Manojlovic 13 Dec '13

13 Dec '13

Dear colleagues, we have uploaded lots of pretty photos to the Community page: https://atlas.ripe.net/get-involved/community/#!tab-actionshots I am attaching the screenshot and one, most colorful photo. Please upload your own photos, and enjoy the holiday season. Share and Enjoy :) Vesna

1 0

Re: [atlas] Measurements at an interval
by warwick 13 Dec '13

13 Dec '13

Hi Daniel, I sent an email (included below.) outlining a measurement with a specific interval done through the API and listed the response, please look at the email below. As for the Web UI measurement here is an example: /{u'result': u'/api/v1/measurement/1044471/result/', u'status': {u'id': 4, u'name': u'Stopped'}, u'msm_id': 1044471, u'interval': 1200, u'description': u'', u'participant_count': 50, u'can_visualise': False, u'resolve_on_probe': False, u'start_time': 1386161734, u'af': 6, u'creation_time': 1386161734, u'is_oneoff': False, u'stop_time': 1386165633, u'all_scheduling_requests_fulfilled': True, u'resolved_ips': [u'2001:7b8:40:1:d0e1:0:0:1'], u'dst_asn': u'12859', u'query': {u'type': u'AAAA', u'class': u'IN', u'value': u'nlnetlabs.nl.'}, u'is_public': True, u'type': {u'id': 7, u'name': u'dns'}, u'dst_addr': u'2001:7b8:40:1:d0e1:0:0:1', u'dst_name': u'2001:7b8:40:1:d0e1::1'}// / Robert Kisteleki suggested I send it through to atlas(a)ripe.net which I did and it has been listed as: [ripe.net #1113749] I received a response from Robert Kisteleki (which is the very last email included below), he said it might be a week or later until this gets investigated so he was right on the money :-) . Thank you for your response and we hope to see this bug(or whatever it is) get squashed :D P.S. If you could, please include Willem Toorop(Willem(a)nlnetlabs.nl) in the response as he was the one to mention this limitation to me and the one who suggested I email about this. He also sent an email outlining this issue but heard no response so I'm sure he would like to hear when a resolution to this limitation/bug/whatever has been found. P.P.S. At the bottom of the first included email is our work around which is get the probes specific to our needs (ipv6/4 etc..) and the chunk them into sizable chunks(50 probes work). Kind regards, Warwick Louw -------- Original Message -------- Subject: Re: [atlas] Measurements at an interval Date: Wed, 04 Dec 2013 14:04:05 +0100 From: warwick <warwick(a)nlnetlabs.nl> To: atlas(a)ripe.net Hello, Regarding the previous email: Measurements at an interval, below is the Json constructed for the measurement: / / /{'definitions': [{'description': '', 'use_probe_resolver': False, 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': False, 'recursion_desired': False, 'target': '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168052, 'probes': [{'requested': 100, 'type': 'area', 'value': 'WW'}]}/ And below is the response: /{"error": {"code": 104, "message": "You do not have enough credit to schedule this measurement."}}/ It seems as though it's a trivial mistake, that I might actually not have enough credits to perform this measurement but I'm sure I do since it's a simple DNS query with only 100 probes. With 50 probes: /{'definitions': [{'description': '', 'use_probe_resolver': False, 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': False, 'recursion_desired': False, 'target': '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168333, 'probes': [{'requested': 50, 'type': 'area', 'value': 'WW'}]}/ This request is executed as expected. With the following response: /{u'measurements': [...]}/ (measurement id removed.) To get past this problem we have been chunking our probes in groups of 50. I just thought you might be interested. Kind regards, Warwick Louw -------- Original Message -------- Subject: [ripe.net #1113749] Re: [atlas] Measurements at an interval Date: Wed, 4 Dec 2013 15:24:32 +0100 From: Robert Kisteleki <atlas(a)ripe.net> Reply-To: atlas(a)ripe.net To: warwick(a)nlnetlabs.nl Hi, Got it, we'll look into this (probably early next week when the best person for this is back). Regards, Robert On 2013-12-04 14:09:08, warwick(a)nlnetlabs.nl wrote: > Hello, > > Regarding the previous email: Measurements at an interval, below is the > Json constructed for the measurement: > / > / > > /{'definitions': [{'description': '', 'use_probe_resolver': False, > 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', > 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': > False, 'recursion_desired': False, 'target': > '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168052, 'probes': > [{'requested': 100, 'type': 'area', 'value': 'WW'}]}/ > > > And below is the response: > > /{"error": {"code": 104, "message": "You do not have enough credit > to schedule this measurement."}}/ > > > It seems as though it's a trivial mistake, that I might actually not > have enough credits to perform this measurement but I'm sure I do since > it's a simple DNS query with only 100 probes. > > With 50 probes: > > /{'definitions': [{'description': '', 'use_probe_resolver': False, > 'af': 6, 'query_argument': 'nlnetlabs.nl', 'query_type': 'AAAA', > 'interval': 1200, 'query_class': 'IN', 'type': 'dns', 'is_oneoff': > False, 'recursion_desired': False, 'target': > '2001:7b8:40:1:d0e1::1'}], 'stop_time': 1386168333, 'probes': > [{'requested': 50, 'type': 'area', 'value': 'WW'}]}/ > > > This request is executed as expected. With the following response: > > /{u'measurements': [...]}/ (measurement id removed.) > > > To get past this problem we have been chunking our probes in groups of > 50. I just thought you might be interested. > > Kind regards, > Warwick Louw > -- Robert Kisteleki, R&D Manager, RIPE NCC RIPE Atlas Team

1 0

Measurements at an interval
by warwick 13 Dec '13

13 Dec '13

Hello again, I stumbled upon something peculiar when submitting measurements with an interval via the API. It seems when submitting a measurement with a specific interval the maximum number of probes I could use was 50, but through the web interface the exact measurement is acceptable with many more probes. Kind regards, Warwick Louw

2 1

Spectrum Internet Ltd (UK) has joined RIPE Atlas anchors
by Michela Galante 11 Dec '13

11 Dec '13

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 uk-cdf-as48294 and is hosted by Spectrum Internet Ltd in Cardiff, United Kingdom. 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

Looking for more beta testers
by Vesna Manojlovic 04 Dec '13

04 Dec '13

Dear RIPE Atlas users, we are currently testing one new feature -- alerting functionality that would enable you to incorporate results from RIPE Atlas into your nagios (or similar). There is a closed list for beta-testers, where we announce these kind of small tests, to smooth out worst bugs before enabling the feature for all the users. We would like to invite few more brave users who are willing to give us feedback on these early prototypes. If interested, please subscribe to this list: https://www.ripe.net/mailman/listinfo/atlas-testers Your applications need to be approved, so please allow several days until you get a confirmation from us. Thanks! Vesna

1 0

Credits System
by warwick 04 Dec '13

04 Dec '13

Hello, I was wondering if you please explain how the credit system works, specifically traceroute measurements. I performed 2 measurements yesterday using large packets(1500) and targeted 500 probes per experiment. When the bill came it was rather shocking. I realize this is a tall order, but is the amount correct? The measurements I'm referring to are : 1043292 and 1043293. They each totaled to 1M credits, should it not be half of that? Kind regards, Warwick Louw

2 1

A new RIPE Atlas anchor is now online
by Michela Galante 03 Dec '13

03 Dec '13

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 gr-ath-as5408 and is hosted by GRNET in Athens, Greece. 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