This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] API error
- Previous message (by thread): [atlas] API error
- Next message (by thread): [atlas] Tagging probes which are using the ISP's DNS server?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Fri Oct 7 09:15:19 CEST 2022
Dear colleagues, The issue with the latest and results endpoints not working for restricted built-in measurements has now been resolved. You should now be able to see results for public probes and probes hosted by you on these endpoints. Apologies again for the inconvenience. Regards, Chris On 26/09/2022 15:58, Ernst J. Oud wrote: > > Hi, > > Since a short while (1 or 2 days) I get an authorization error when > downloading the data from the built-in first and second hop to > ping.ripe.net. > > Thus: > > https://atlas.ripe.net/api/v2/measurements/1/results/?probe_ids=1004467&start=1664150400&stop=1664236799&format=json > > > Gives: > > {"error":{"detail":"Authentication credentials were not provided.","status":403,"title":"Forbidden","code":104}} > > If I logon with my credentials via “My Atlas”, I get: > > {"error":{"detail":"You do not have permission to perform this action.","status":403,"title":"Forbidden","code":104}} > > > All other tests let me download the data fine, logged in or not. > > Same happens to download first and second hop data of other public probes. > > Any clues? > > Regards, > > Ernst J. Oud >
- Previous message (by thread): [atlas] API error
- Next message (by thread): [atlas] Tagging probes which are using the ISP's DNS server?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]