Closed Strykar closed 2 years ago
Those parse errors are from the RIPEStat API, most likely gateway timeout errors from the API endpoint. I am afraid there is little to do when the endpoint times out, except for either notifying RIPE about it (and asking them to beef up their resources), or merely using a different source.
Regarding your specific need, I tried your search and (after the same timeout you are experiencing), I got the following output:
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ Announced prefixes (aggregated) for AS45609 (BHARTI-MOBILITY-AS-AP Bharti Airtel Ltd. AS for GPRS Service, IN) │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
───── IPv4 ─────
106.0.0.0/8
110.224.0.0/14
117.96.0.0/14
125.16.0.0/13
171.48.0.0/12
171.76.0.0/14
182.0.0.0/8
223.176.0.0/12
223.224.0.0/12
27.56.0.0/13
59.144.0.0/15
───── IPv6 ─────
2401:4900::/32
Which looks accurately aggregated, after quickly glancing at their announced /48 prefixes. If you're looking for the individual prefixes, I guess you can try the RIPEstat UI directly from the web. Their new beta UI also conveniently separates them between IPv4 and IPv6. Try here ("announced prefixes" widget).
Thanks for the beta ripestat link, looking good. Should I close this then, could we have asn print timeout errors when they occur?
Leave it open, I will add some timeout handling and close the issue as soon as I get around to doing it. Thanks for the feedback!
This ASN has a large number of prefixes and I'm trying to get a list of just the IPv6's. When I add an IP Reputation token, it's still running for over 30 mins on a 50 Mbit FTTH uplink.