- ripe-atlas - mailman.ripe.net

Introduction of RIPE Atlas Quick Looks
by Vesna Manojlovic 07 May '13

07 May '13

Dear colleagues, A new RIPE Atlas feature is now available to RIPE NCC members: Quick Look measurements. LIRs can use this service for a quick, real-time assessment of connectivity without hosting a RIPE Atlas probe. This feature is based on one-off measurements that are available to all RIPE Atlas probe hosts. Please find more information on RIPE Labs: https://labs.ripe.net/Members/kistel/ripe-atlas-quick-look-for-members Regards, Vesna

1 0

Fwd: [mat-wg] New on RIPE Labs: Releasing RIPE Atlas Measurements Source Code
by Robert Kisteleki 06 May '13

06 May '13

Dear RIPE Atlas users, Some of you might be interested in the news below. Regards, Robert Kisteleki -------- Original Message -------- Subject: [mat-wg] New on RIPE Labs: Releasing RIPE Atlas Measurements Source Code Date: Mon, 06 May 2013 16:43:07 +0200 From: Mirjam Kuehne <mir(a)ripe.net> To: mat-wg(a)ripe.net Dear colleagues, This new article on RIPE Labs introduces the RIPE Atlas measurement source code. The measurement code is the part that runs on the RIPE Atlas probes to schedule and execute particular measurements, and thereby forms the core of the RIPE Atlas system. https://labs.ripe.net/Members/philip_homburg/ripe-atlas-measurements-source… Kind regards, Mirjam Kuehne RIPE NCC

1 0

News about latest RIPE Atlas release and a use-case story
by Vesna Manojlovic 03 May '13

03 May '13

Dear colleagues, as regular users, I am sure you have noticed the big changes we implemented last week: - new look of the opening page for visitors - new dashboard for logged-in users - new maps There are also more things added that are not so visible, but are the important features that you asked for: - probe sharing - one-off measurements - REST APIs Please see the details in this article by Robert Kisteleki, and let us know how happy you are with it all: https://labs.ripe.net/Members/kistel/new-ripe-atlas-features-april-2013 And just today, RIPE Labs article by Stéphane Bortzmeyer was published, about using RIPE Atlas to take a look at how his anycast implementation behaves and which instance is the most popular: https://labs.ripe.net/Members/stephane_bortzmeyer/using-atlas-udm-to-find-t… If you have such an interesting measurement, please share it with us, and with the world. Regards, Vesna

1 0

AS number in traceroute data
by Pavel Veselovskiy 29 Apr '13

29 Apr '13

Hello, Is it possible to perform RIPE Atlas measurements with a key "-A" that shows the number of autonomous systems? - Kind Regards, Pavel Veselovskiy, Samara State Aerospace University

6 5

RRDs for pings with 25 probes.
by Ben Clifford 26 Apr '13

26 Apr '13

When I create ping UDMs with 20 probes, I get RRDs. When I create ping UDMs with 25 probes, the "visualize" checkbox gets turned off somehow and I don't get RRDs. Is there something funny going on? (or is there something else forcing visualize off that i have miscorrelated with the probe count). --

4 5

Fetching results for ongoing measurements
by Sebastian Castro 25 Apr '13

25 Apr '13

Hi: I've setup my first UDM (thanks Stephane for the code), and when I try to fetch the results, it gives me two different responses: No results or "Sorry, this request could not be processed. Please try again later". If I check the Atlas interface, I see my probes, credits being discounted, but the "my measurements" section is empty. The measurement have been going for 12 hours so far. Is there a restriction regarding fetching results for ongoing measurements, meaning I need to stop it first to be able to get any results, or it's a temporary error, or something else? Kind Regards, -- Sebastian Castro DNS Specialist .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

4 6

RIPE Atlas roadmap has a new home
by Vesna Manojlovic 22 Apr '13

22 Apr '13

Dear Atlas community, [apologies for duplicates] we determine the roadmap for RIPE Atlas together: based on RIPE NCC internal plans and ideas, and on your wishes and suggestions & needs. After publishing the incremental updates to the roadmap in the RIPE Labas articles and presentations, we now have a permanent location for the RIPE Atlas roadmap: http://roadmap.ripe.net/ripe-atlas/ It is part of the listing of a few RIPE NCC services and their plans. We publish the features in 4 categories: * recently delivered * in progress * planned & * requests We will keep updating this page, every time when one of the features move from "in progress" to "delivered", and so on. Next steps are * to add more details about all of those listed features, * to take on your comments, feedback, suggestions, and prioritize those that are only "requested", so that we can understand what exactly the feature means, and to move it to the "planned" category. * do consider automating the expression & collection of feedback More information: RIPE Labs article: https://labs.ripe.net/Members/mirjam/introducing-ripe-ncc-roadmap Please do let us know what you think of this! Vesna

1 0

Planned woks on Atlas this week
by Robert Kisteleki 22 Apr '13

22 Apr '13

Dear All, In the first half of this week (Mon-Wed) we'll carry out multiple changes and upgrades to the RIPE Atlas infrastructure. This work includes some capacity increases and rollout of new features, and involves temporary suspension of data processing and occasional downtimes for the UI. We apologise for the inconvenience this may cause. Regards, Robert Kisteleki

1 0

Result consumption issues at the moment
by Robert Kisteleki 22 Apr '13

22 Apr '13

Dear Atlas users, At the moment we have a hardware issue with one of the backend servers which serves built-in measurement results for probes with ID in the range 4500-4999. We're working on resolving this and will get back to you with an update. Regards, Robert Kisteleki

1 1

[Fwd: [mat-wg] Measuring IP address hijacking with RIPE Atlas?]
by Vesna Manojlovic 18 Apr '13

18 Apr '13

Dear colleagues, in case you are not following MAT-WG mailing-list: this was posted there yesterday (text bellow). To see the whole thread, start here: http://www.ripe.net/ripe/mail/archives/mat-wg/2013-April/000273.html Any comments, ideas, feedback? Please have a discussion on the MAT-WG list, or, if you prefer to reply on this list, I will collect your feedback & bring it to the mat-wg. Thanks, Vesna -------- Original Message -------- Subject: [mat-wg] Measuring IP address hijacking with RIPE Atlas? Date: Wed, 17 Apr 2013 16:01:18 +0200 From: Anatole Shaw <ripemat(a)omni.poc.net> To: mat-wg(a)ripe.net Currently I work with Greenhost, which is a RIPE LIR that was recently the recipient of a malicious route advertisement, as described here: https://greenhost.nl/2013/03/21/spam-not-spam-tracking-hijacked-spamhaus-ip/ IP address hijacking is a real problem. How often does it happen? Which networks are being spoofed, and which networks are the victims? My sense is that we don't have solid up-to-date answers to these questions. I have some thoughts about how to detect successful IP hijacking, using empirical measurements taken from multiple network vantagepoints. I'll hold off on details for now, but I'm aware that the answer is *not* simple analysis of AS paths or traceroute output, both of which are increasingly spoofed. It seems like the RIPE Atlas probe network would be an ideal platform for this type of study. Does such a study already exist? How does one begin to propose a RIPE Atlas project? Regards, Anatole Shaw

1 0