The probe's network usage is now visualised on the probe details page. We show both bits/sec and packets/sec, as seen on the probe's network interface. Note that these include broadcast traffic, so it most likely overestimates the actual network traffic related to the probe.
You can now easily look at the last traceroute(6) result of each built-in measurement: click on the link of the "Target Address" column.
Downloading the logs for a measurement done by your probe has been moved to the probe details page. The previous method (allowing downloads from the probes grid) did not scale well.
A probe host can now ask for notification (via email or an http POST) if the probe is disconnected from our network for more than 30 minutes. You can turn on this feature in the probe settings page.
A probe host can also ask for a monthly probe connection report, also in the probe setting page.
The most notable change is that from now on the download format of your probe's measurement data is JSON. The actual syntax is pretty much self-explanatory.
The DNS anycast map now visualises server versions and SOA serials too.
We made further changes to the way we show static network configuration of a probe on the "probe status" page.
We're making preparations to include Atlas in RIPE NCC Access, the RIPE NCC single sign-on system.
Beyond these changes, we've made some enhancements to the scalability of the upcoming User Defined Measurement feature and did some additional internal ("invisible to the users") modifications.
From now on, the user authentication behind RIPE Atlas is done through RIPE NCC Access, the RIPE NCC single sign-on system. In order to use RIPE Atlas, you'll have to log in with your single sign-on credentials.
This change allows us to offer easier access to other RIPE NCC services, as well as to provide more specialised content to RIPE NCC members in the future.
A new version of the RIPE Atlas probe firmware will be released later this month. This release will affect the raw data structure of measurement results.
Probe firmware version 4470 will be released soon. This version includes a small data structure change from 4460 which only affects DNS measurements: the addition of the optional field 'src_addr'.
We have also published a correction for version 4460, which mistakenly listed a field 'src' for DNS measurements. This field does not exist in 4460.
This update brings a number of internal changes as well as a few additions to th UI:
API keys: similarly to the API keys used in RIPE NCC LIR portal, it's now possible to manage "API keys" in RIPE Atlas. At this time these keys can be used to download and share your measurement results (probe built-in measurements and UDMs). More information can be found in the documentation section.
There's a new graph about the credit consumption rate of the last two months; it allows visual inspection of your credit generation/consumption trends. From October on we'll also make your "transaction statements" downloadable for each previous month. You can find both of these by clicking on the "Archives" button at the bottom of the "My Credits" section of the UDMs menu item.
Applying for probes: we made simplifications to this procedure which allows easier communication between a would-be-host and us, as well as a more logical procedure flow.
We added the possibility to filter the output of the "UDM list". This comes handy for the users who have many UDMs.
Various smaller enhancements:
flipping through pages in the UDM list should be faster now
you'll a separate credit transaction for each of your probes, in case you have more than one
You can now download you credit reports for previous months
The RIPE NCC Access (single sign-on) subsystem now recognizes RIPE NCC members, so from now on we can develop more features that require recognition of particular members and their registered users.
The probes' "Assigned UDMs" section now shows entries about previous measurements, so hosts can look up what the probe did recently.
In preparation for the upcoming Atlas anchors and newer probe hardware models, the probe's architecture is now shown in the UI.
Auto-notification about down probes is now using a "three strikes" model.
Probes can now be earmarked for sponsors, so a sponsor's probe list is now populated with all their sponsored probes, not only the activated ones.
We've added a "top hosts" community page.
We've added a "top spenders" community page.
UDM data downloads are now much more responsive, also with large result sets.