- ripe-atlas - mailman.ripe.net

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