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 (v1) querying probes by ID
- Previous message (by thread): [atlas] Probe uptime?
- Next message (by thread): [atlas] API (v1) querying probes by ID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wenqin SHAO
wenqin.shao at telecom-paristech.fr
Wed Feb 3 11:07:57 CET 2016
Dear list, I have the impression that querying probes by ID returns unexpected results. An example is: https://atlas.ripe.net/api/v1/probe/?id=1 <https://atlas.ripe.net/api/v1/probe/?id=1> As a result, I get the entire probe list: "meta": { "total_count": 16973, "use_iso_time": false, "next": "/api/v1/probe/?id=1&limit=100&offset=100", "limit": 100, "offset": 0, "previous": null }, And ID 1 is an valid ID, which corresponds to the first entry of results: "id": 1, "type": "Probe", "is_public": false, "first_connected": "2010-10-29T15:53:03Z", "last_connected": "2016-02-03T10:02:28.407276Z", "is_anchor": false, "address_v4": null, "address_v6": null, "asn_v4": 3265, "asn_v6": 3265, "country_code": "NL", "prefix_v4": "212.238.0.0/16", "prefix_v6": "2001:980::/29", Regards, wenqin -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20160203/cf4930f6/attachment.html>
- Previous message (by thread): [atlas] Probe uptime?
- Next message (by thread): [atlas] API (v1) querying probes by ID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]