- ripe-atlas - mailman.ripe.net

NTT Communications (US, Seattle and Atlanta) have joined RIPE Atlas anchors
by Michela Galante 06 Jun '14

06 Jun '14

Dear RIPE Atlas users, We're happy to announce that two more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors, both hosted by NTT Communications in United States, are: us-sea-as2914, in Seattle us-atl-as2914, in Atlanta Congratulations to NTT Communications for their third and forth anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors 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

A collection of tools in Perl
by Stephane Bortzmeyer 04 Jun '14

04 Jun '14

https://github.com/pierdom/atlas-toolbox

3 2

RIPN (RU) has joined RIPE Atlas anchors
by Michela Galante 03 Jun '14

03 Jun '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 ru-mow-as15835 and it is hosted by RIPN in Moscow, Russia. 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

Changes to the Distribution Model for RIPE Atlas Probes
by Vesna Manojlovic 03 Jun '14

03 Jun '14

Dear colleagues, we have made some adjustments in the distribution model of RIPE Atlas probes to ensure wider topological and geographical probe coverage. Please read more in this RIPE Labs article: https://labs.ripe.net/Members/fatemah_mafi/changes-to-the-distribution-mode… Regards, Vesna

1 0

Probe not showing IPv6 ASN and subnet on map
by JC 02 Jun '14

02 Jun '14

Hi, We just setup our probe (id: 17328) and configured static IPv6 on it. Built-in measurements to IPv6 destinations seems to perform correctly from this probe. However, when we display detailed information about the probe on the coverage map https://atlas.ripe.net/results/maps/network-coverage/ we only see IPv4 information and no IPv6 subnet or ASN. Besides, searching for our IPv6 ASN (21538) in the filter field brings no results. Thanks for your help. Regards, JC

2 1

Where is "My probe" tab?
by Gilles Pion 28 May '14

28 May '14

Hello, Just received my probe today, Registered it, plugged it, all leds seem correct. I've followed the instruction on page https://atlas.ripe.net/get-involved/become-a-host/ where one can read: "Once we see that your probe is connected to the RIPE Atlas infrastructure, you'll be able to see it listed on the Public Probes page and, when you are logged in to the RIPE Atlas website, it will appear under the "My Probes" tab on that page. But, although logged on the web site I'm unable to find this "My Probes" tab on the "Public Probes" page Could someone help? -- Gilles

2 2

Bogal AB (SE) has joined RIPE Atlas anchors
by Michela Galante 28 May '14

28 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 se-got-as50168 and it is hosted by Bogal AB in Gothenburg, 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 creation tools and library
by Matt Calder 28 May '14

28 May '14

Hi, I'm announcing a set of Python-based command-line tools/library for measurement creation available at https://github.com/USC-NSL/ripe-atlas. Since the focus is heavily on assisting measurement creation, I think that it should compliment Sagan nicely. It has been slowly under development for a while now but still has plenty of room to grow in supporting all of the options for different measurement types. Thanks, Matt

2 1

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