The Routing Status API consistently fails to retrieve data for certain ASNs.For example, ASN16509.The detailed URL of the request is as follows:
curl --location --request GET “https://stat.ripe.net/data/routing-status/data.json?resource=16509&min_peers_seeing=1”
Hi,
The AS in question is used for Amazon Web Services, and as such originates over 20,000 prefixes. Given the way we currently access RIS data, the routing-status backend does not cope with such a large AS very well. We have recently completed a large migration of the RIS data, and we are now looking into ways of improving how we ingest, store, and access RIS data in the future in order to improve the performance and capabilities of RIPEstat — your report sparked some ideas for improving routing-status in this regard specifically, so thank you for letting us know!
What fields do you need? Depending on your use case, it may be possible to get the data you are looking for through other means — perhaps through the RIS dumps (in MRT format or Parquet format) or the RISwhois service.
Hi, svankampen
Thank you so much for your suggestion. I will look into the tools you provided.