On 2025/06/24 14:17, Robert Kisteleki wrote:
Hello Ray,
We made quite some changes in the UI recently and eventually removed some older (undocumented, "internal") calls. This was one of them. Apologies if this causes you grievance.
You have three alternatives - I'm assuming you're really after basic probe data, in particular coordinates:
Yes, just coordinates and ID.
1. Use the probes API: /api/v2/probes/ for info about multiple probes or a single one
I have an implementation of this now, but only getting 500 at a time is somewhat suboptimal, for both of us! ;)
2. I highly recommend using the daily dumps of the same (https:// ftp.ripe.net/ripe/atlas/probes/archive/ <https://ftp.ripe.net/ripe/ atlas/probes/archive/>) if you don't need real-time values for connectedness (which is usually the case). This is the cheapest option.
Does your web server support on the fly uncompression of the bzip2 data? I note that the meta-latest is missing its .bz2 suffix despite being compressed.
3. There's an alternative internal call with similar data to that original one, which we heavily use internally from now on. I can give you the URL if you insist :-) but this is subject to unannounced changes
Understood - I'll get back to you on that if I can't make option 2 work. I'd prefer for folks that deploy the code not to have to deploy server-side logic to regularly download (and decompress) the latest file, but instead have the JS client retrieve it direct. The bzip2 compression might prevent that, though. thanks! Ray