- ripe-atlas - mailman.ripe.net

Feature you asked for: "latest results" API
by Vesna Manojlovic 27 May '14

27 May '14

Dear RIPE Atlas community, last week we enabled a new feature that quite a few people had an interest in: an API that lets you get up to 10 most recent results of any measurement: https://atlas.ripe.net/docs/measurement-latest-api/ We wrote an article with more details: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-resul… From the article: "This new feature could come in useful in a number of different situations, such as: - Creating a widget for a website that monitors a specific result in near real time, such as ping results from 100 probes around the world toward your own website - Monitoring your network by setting up an alert based on the average measurement result from the past hour - Staying aware of a major network event, such as an Internet outage in a certain region - DNS monitoring of your own domain, with configurable measurements using 10 RIPE Atlas anchors - Prototyping a script using RIPE Atlas data" Please let us know if you find other creative uses for this new API! If you develop custom code for configuring the results of this API, please share it at the GitHub RIPE Atlas Community repository: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib We would love to hear your success stories! Regards, Vesna

2 1

Unable to connect my probe
by Vincent Roussillat 27 May '14

27 May '14

Hello I've received my probe #16969 yesterday, registered it and tried to connect it behind my Orange Livebox here in France. It doesn't succeed to get connected and even doesn't get an IP from the DHCP server of my box (which delivers IP address to my other devices). I have tried this morning to connect it to another Internet access, at work and this failed too. Led #4 remains blinking. I can see in MyAtlas interface that the probe got connected just after the first boot, as I can see to request to DNS servers logged in the interface. May be, an upgrade began and got interrupted, leaving the probe in a strange state, I don't know... Anyway, what should I do now ? Request another probe ? Send this one back to the RIPE ? If so, where should I send it ? Regards.

2 1

Introducing: the new result parsing library (Sagan)
by dquinn 26 May '14

26 May '14

Hi everyone, in advance of the RIPE Meeting, I thought I'd let you all know about the new parsing library we've developed for use against measurement results. This was mentioned in a recent RIPE Labs article[1] but I thought it worth detailing here for those of you who aren't avid Labs followers. The idea is that you run every result you get through this handy Python library and out comes programmer-friendly Python objects. It supports the various changes in result format over time, and even does some of the heavy lifting for you like calculating ping median rtt, parsing the DNS abuf, or counting the traceroute hops. The project code is published on GitHub[2], and pull requests are welcome. Installation can be done via Pypi[3], and documentation is included in the module and available online[4] as well If you have any questions feel free to post to the list and one of us will see what we can do for you. [1] RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-latest-resul… [2] Project: https://github.com/RIPE-NCC/ripe.atlas.sagan [3] Pypi: https://pypi.python.org/pypi/ripe.atlas.sagan/ [4] Documentation: https://atlas.ripe.net/docs/sagan/

3 3

RIPE Atlas use case on RIPE Labs: Evaluating new IXP peers
by Vesna Manojlovic 26 May '14

26 May '14

Dear colleagues, in this article Daniel Gomez explain how RIPE Atlas helped to evaluate new synaix's peering partners within an Internet Exchange Point and how this helped to improve customer services. Please find more details on RIPE Labs: https://labs.ripe.net/Members/daniel_gomez/basic-evaluation-of-new-ixp-peer… Kind regards, Vesna Manojlovic RIPE NCC

1 0

Atlas Latest
by john 23 May '14

23 May '14

Hi, I have been playing with the latest API over the past few days and it seems like there may be a cache in place. Is this the case? if so how long is it? Thanks John

2 2

Probe cannot connect from behind IDS/IPS with HTTPS inspection
by Ondřej Caletka 21 May '14

21 May '14

Hello list, I just observed strange behaviour of one Atlas probe. It was unable to connect to the control server from a corporate network. I suspect that some IDS/IPS appliance detects and drops probe attempt to use port 443 for non-TLS traffic*. I've tested it by trying to SSH to control server from within that network and it failed. However, normal SSH to port 22 works fine. It would be nice if the probe would be able to try more ways to reach the control server, eg. first attempt on port 443, second on port 22, third on some arbitrary high port number. I know that it would be better to put the probe in front of the firewall/IPS, but this is much more complicated in many corporate networks. *) At least it doesn't do MitM on HTTPs traffic. I've checked that too. Cheers, Ondřej Caletka

6 10

a thought about public probe page...
by Wilfried Woeber 21 May '14

21 May '14

I've got a small comments regarding the probes' overviw page at https://atlas.ripe.net/probes/ - for the country filter, top right, could the list of countries be sorted? Thanks, low prio :-) Wilfried.

1 0

Problems with DNS measurements and NSID
by Klaus Darilion 21 May '14

21 May '14

Hi! Whatever I try I fail to get the nameserver id. See measurement: https://atlas.ripe.net/api/v1/measurement/1666014/ But there is no NSID in the results: https://atlas.ripe.net/api/v1/measurement/1666014/result/ Am I doing something wrong, or is there a bug? Thanks Klaus

5 12

NTT Communications (US, Miami) has joined RIPE Atlas anchors
by Michela Galante 20 May '14

20 May '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 us-mia-as2914 and it is hosted by NTT Communications in Miami, United States. Congratulations to NTT Communications for their second anchor online! 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

high volume IPs/anycasted?
by Jared Mauch 19 May '14

19 May '14

I have a few IPs on our network that are anycasted that I'd like to see the "9 limit" increased for, is there a proper way to do this? - Jared

1 0