Skip to content

PeeringDB updates#

ITNOG9 digest Program Adjacent pick 19–20 May 2025

Slides

Livio Morina

  • Why: PeeringDB is the de-facto interconnection data layer, and this update has a directly relevant identity angle: mandatory phishing-resistant-adjacent MFA (TOTP plus FIDO U2F) and the elimination of password-based API auth — a small but real instance of passkey-class auth reaching core Internet infrastructure.
  • What: The 2024/2025 PeeringDB review: 2024 growth (networks 29,148→31,597, exchanges 1,152→1,239, users +11.2%), new Carrier (L1/L2 providers) and Campus (multi-facility cross-connect) object types, automatic removal of RIR-reclaimed ASNs, KML/KMZ geographic export, and the 2025 roadmap.
  • How: MFA becomes mandatory for all authenticated users on 1 July 2025 — TOTP with backup codes, or FIDO U2F; API access moves to API keys, no more username/password. A new web tool will compare interconnection opportunities across facilities; peeringdb-py local sync is recommended to avoid query limits and PeeringDB-side load. The whole platform is BSD-2-Clause open source on GitHub.
  • Where applicable: Universal for peering coordinators and anyone using PeeringDB data in automation (it is a common input for router config generation). The MFA/API-key mandate is an early signal of what Internet infrastructure services will require of integrators.