HOWTO: Work Within PeeringDB’s Query Limits

PeeringDB implements query throttling to encourage efficiently formatted queries and/or local caching. Many popular tools have been upgraded to use PeeringDB more efficiently.

Query limits

Duplicate queries:

Query rate limit:

Efficient queries

We encourage users to make fewer, larger queries instead of making many small queries.

Instead of sending each ASN you want to learn about as a separate query, create a list of ASNs and send them in a single query. The query element would look like this:


We encourage sending lists of up to 150 ASNs in a single query. We have a HOWTO article describing the basics of using our API using popular command line tools such as curl, Python, and jq.

Please use API Keys when automating queries to PeeringDB and set a User-Agent header that identifies the unique software you are using, rather than just a generic query library name.

We also encourage you to leave at least two seconds between queries.

Local cache

We encourage you to use a local cache and synchronize it every hour or less frequently in accordance with your organization's needs. When you use a local cache you will only be sent changes since the last sync.

We publish peeringdb-py, which can be used directly or as a reference implementation. Code is here and documentation is here.

Use of an API key with peeringdb-py is highly recommended.

If you want to implement a local cache using different tools and would like advice, we are happy to talk. Contact us at


Popular tools, including arouteserver have been updated to include support for API Keys and to make more efficient queries. We publish a list of tools that we know use PeeringDB. Check the list for tools that you use and upgrade old versions to take advantage of new features and improve everyone’s PeeringDB experience.