PeeringDB — approval request (to send before enabling the connector)
The PeeringDB Acceptable Use Policy (https://www.peeringdb.com/aup) allows bulk download only for "Internet
operational issues" (including "Internet research and analysis") and requires PeeringDB's permission before data is
reproduced or passed on in bulk. DataCenterIndex republishes derived facility / IXP records publicly, so the
peeringdb connector ships disabled (config/connectors/peeringdb.yaml, enabled: false) until written approval
is received. Once approved, request an API key (Authorization: Api-Key) and set PEERINGDB_API_KEY in
deploy/.env.crawl, then set enabled: true and redeploy the crawl node.
Draft e-mail — to: support@peeringdb.com
Subject: Request for approval — use of PeeringDB facility/IX data in DataCenterIndex.io (research index)
Hello PeeringDB team,
I am Simon-Pierre Boucher (contact@spboucher.ai), operator of DataCenterIndex.io, a non-commercial public research index of data center infrastructure (facilities, campuses, operators, cloud regions, internet exchanges, projects) hosted on my own infrastructure (MacLustr, www.maclustr.io).
I would like to use the public PeeringDB API (fac, org, campus, ix, ixfac, netfac, net) as one of the
sources of the index, specifically to:
- list colocation facilities with their operator, address, coordinates and PeeringDB id;
- show which internet exchanges and how many networks/carriers are present at each facility;
- link each record back to its PeeringDB page with the attribution "Data: PeeringDB".
Data would be refreshed at most weekly (incremental since= requests, one request per endpoint, spaced ≥ 2 s), stored
with full provenance, and displayed per facility/IX page — no bulk redistribution, no resale, no marketing use. Every
displayed value keeps its PeeringDB source and link. I am happy to register an API key under this account, add a
User-Agent identifying the crawler (DataCenterIndexBot/0.1 (+https://www.datacenterindex.io/bot)), and to comply
with any additional attribution or rate-limit requirements you have.
Could you confirm whether this use is acceptable under the AUP, and if so, what attribution wording you prefer?
Thank you, Simon-Pierre Boucher contact@spboucher.ai — https://www.datacenterindex.io