You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The clients-from-peeringdb command performs multiple PDB API calls
sequentially to obtain ASNs' info. Users reported some errors related to
429s and an investigation on the PeeringDB side showed some logs where
those API calls were made without any API key.
Even though I was not able to reproduce the issue (all the API
calls were made with the proper API key) I introduce here this
workaround to reduce the n. of calls made in one minute, to match the
limit on the PeeringDB side.
PeeringDB API calls made to handle the
clients-from-peeringdb
command are done without the API key:The text was updated successfully, but these errors were encountered: