Dear colleagues,
The good news: RIPE Atlas is growing both in terms of geographical
diversity and ASN coverage. What's more, RIPE Atlas is evolving, with a
new generation of probe hardware having already passed the test phase
and a pilot programme underway to assess the viability of VM anchors.
The not so good news: With RIPE Atlas so much in demand, and with our
current provider having ceased manufacturing the probe hardware, we've
had to dramatically reduce the number of probes we're distributing.
Please find more details on RIPE Labs:
https://labs.ripe.net/Members/alun_davies/ripe-atlas-probes-delays-in-distr…
Kind regards,
Mirjam Kühne
RIPE NCC
Hi everyone,
I'm working on a project where I create a measurement via API and
immediately subscribe to the result stream as well as the metadata stream (
https://atlas.ripe.net/docs/api/v2/manual/measurements/result-streaming.html
).
socket.emit("atlas_subscribe", {stream_type: "result", msm: mid,
sendBacklog: true});
socket.emit("atlas_subscribe", {stream_type: "metadata", msm: mid});
Now even with (and also without) the sendBacklog option enabled, I rarely
get even close to receive all results (the measurement produces max. 10 in
total, I received max. 4-5, often only one or even none).
Same goes for metadata, where I sometimes get the action: creation event,
but never a notification when the measurement is stopped. Another question
in this context: When does a one-off measurement gets stopped?
I also subscribed to (dis)connect, atlas_error and atlas_subscribed but
they give no hint what could be going wrong. I also tried the replay
feature, which did not work at all for me either:
socket.emit("atlas_subscribe", {stream_type: "result", msm: mid, startTime:
<Time of creation>});
What am I doing wrong?
Thanks, Tim
Tim Wattenberg
mail(a)timwattenberg.de
+49 1578 8248731
Hi,
Has there been a change in the way that API keys work for the measurement
results API?
I've got an API key which is granted permission to get results from a
non-public measurement. When I do:
curl -H "Authorization: Key $KEY" "
https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/results/?start=
1520510400"
(Replacing $KEY with the key and $MEASUREMENT with the measurement ID) I
get:
{"error":{"status":400,"errors":[{"source":{"pointer":""},"detail":"Your
keys has no grants"}],"code":102,"detail":"There was a problem with your
request","title":"Bad Request"}}
This was previously working, but I'm not sure exactly when it stopped.
I've checked that getting the data through my browser works while I'm
logged into the site, and that if I request
https://atlas.ripe.net/api/v2/measurements/$MEASUREMENT/latest using the
API key I get data returned.
Regards,
Dan
Dear colleagues,
In this article we present a new way to access the dataset on the RIPE
Atlas platform. Instead of fetching individual results from measurements
using the available APIs, you can now download files containing public
measurements for a given day.
Please find more details on RIPE Labs:
https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data…
Kind regards,
Mirjam Kühne
RIPE NCC
