SPB Git forge
38commits 1branches 0releases
338.7 MBsize
maindefault branch
3 h agolast push
HTML 53.9% TypeScript 44.5% JavaScript 0.6% SQL 0.5%
2.8 KB · 53 lines yaml
Raw Blame History
1id: peeringdb2name: PeeringDB3domain: www.peeringdb.com4kind: dataset5mode: api6priority: 27# DISABLED 2026-09-11 pending written approval from support@peeringdb.com: the AUP excludes commercial application8# and requires permission for bulk reproduction. Re-enable (enabled: true) once approval + PEERINGDB_API_KEY are in place.9enabled: false10# Verbatim from https://www.peeringdb.com/aup (retrieved 2026-09-11). PeeringDB publishes no CC/ODbL license; the AUP governs use.11license: >-12  PeeringDB Acceptable Use Policy (https://www.peeringdb.com/aup), © 2004-2026 PeeringDB All Rights Reserved:13  "Except for Internet operational purposes approved by PeeringDB, no part of the PeeringDB data may be reproduced,14  stored in a retrieval system, or transmitted, in any form or by any means [...] without prior permission of PeeringDB15  on behalf of the copyright holders. [...] The PeeringDB data may not be passed on in bulk to any other person or16  organization unless approved by PeeringDB. [...] Users will not be able to download the full contents of the database17  unless the intended use is for 'Internet operational issues'. These words are tightly defined and would include18  network trouble-shooting, abuse reporting, and Internet research and analysis. It would not include compiling19  marketing lists, demographic mapping, or any other commercial application."20  → Usage here = Internet research and analysis (facility/IXP graph); confirm with support@peeringdb.com before public redistribution.21attribution: "Data: PeeringDB"22homepage: https://www.peeringdb.com/23notes: >-24  Public REST API, anonymous access allowed but throttled (20 req/min per IP; repeated identical anonymous requests25  > 100 kB limited to 1/hour). Set PEERINGDB_API_KEY in the environment for the authenticated tier (40 req/min,26  header "Authorization: Api-Key …"). Incremental runs use ?since=<unix ts>; full refresh every params.fullRefreshDays.27coverage: { global: true }28fetch:29  level: 130  maxLevel: 131  userAgent: bot32  rpm: 2033  concurrency: 134  respectRobots: true        # robots.txt only disallows account pages; /api/ is allowed35  timeoutMs: 12000036  maxBytes: 100000000        # facilities dump ≈ 6 MB, org (fields) ≈ 6 MB, netfac (fields) ≈ 4 MB37  maxCreditsPerRun: 038schedule:39  facilities: daily          # incremental (since=) daily, full weekly (params.fullRefreshDays)40  ixps: daily41  campuses: weekly42  operators: weekly43  carriers: weekly44implementation: peeringdb45params:46  apiBase: https://www.peeringdb.com/api47  minDelayMs: 2000           # "leave at least two seconds between queries" (PeeringDB HOWTO)48  incremental: true49  fullRefreshDays: 750  carrierHotelMinIx: 3       # facilityType carrier_hotel when ix_count ≥ 3 AND net_count ≥ 15051  carrierHotelMinNets: 15052parserVersion: peeringdb_v153