What is PeeringDB?
PeeringDB is an open database where networks publish their ASN, IX and facility presence and peering policy. We explain the records and why accuracy matters.
Last updated:
PeeringDB is an open, community-run database of networks where operators publish what is needed to set up peering: their autonomous system number (ASN), traffic policies, the internet exchanges (IXPs) and data centers where they are present, and contact details. It is the de facto industry directory for interconnection. When an engineer considers peering with your network, the first thing they check is your PeeringDB profile. The data is served through a web interface and a public REST API, so automation tools can pull it programmatically.
The records: network, facility and exchange
PeeringDB organizes data around three main record types that link together to form a complete picture of a network's presence. The network (net) record describes a single ASN, while facility and exchange records show where you can physically and logically meet that network.
- Network (net) is the ASN record: name, traffic scale, network type, peering policy (open, selective, restricted) and NOC contacts.
- Facility (fac) is a data center or colocation site where a network has equipment and can run a cross-connect.
- Exchange (ix) is an internet exchange point, with its participant list and peering LAN prefixes.
- NetIXLan is the entry linking a network to a specific IXP, holding the IPv4 and IPv6 addresses and the port speed.
- NetFac is the entry linking a network to a specific facility (colocation).
Why an accurate profile matters
An accurate record speeds up peering because the other side immediately sees whether you meet at the same IXP or facility, how much traffic you carry and whether your policy is open. The IPv4 and IPv6 addresses from PeeringDB feed straight into BGP configuration generators, so a typo in a peering address means a session that never comes up. The maximum-prefix field is often pulled automatically and set as a protective limit on the session. If it is wrong or empty, a partner may fall back to a restrictive default. A stale profile is a real loss of potential peerings.
PeeringDB versus other data sources
PeeringDB describes a network's intent and presence, meaning where it wants to peer and on what terms, but it is not the source of truth for who may originate a given prefix. That role belongs to the internet routing registries (IRR), with route and as-set objects, and to RPKI, with signed ROAs. In practice the three work together: PeeringDB tells you the partner and its peering details, while IRR and RPKI verify which prefixes it may announce. PeeringDB also offers record ownership verification, tying an account to the organization's RIR registration to curb ASN impersonation.
PeeringDB and AS202520 SkyPass
AS202520 SkyPass keeps an up-to-date PeeringDB record with an open peering policy, current IPv4 and IPv6 addresses at the Polish internet exchanges (THINX, TPIX, WRIX, POZIX, 1-IX) and a list of facilities in Warsaw and Wrocław. This lets you confirm where we meet and generate a session configuration straight from our profile. For operators without their own port at an IXP we offer remote access, and we validate our routes in line with RPKI and MANRS best practices.
Frequently asked questions
Is PeeringDB free to use?
Yes. PeeringDB is free both to browse and to maintain your own record. It is run as a non-profit funded by industry sponsors, and access to the data through the web interface and the API is open.
How do I update my network record?
You create an account, confirm your link to the organization (usually via an email address in its domain or RIR verification) and edit the net record fields, including peering policy, traffic volume, max-prefix and the NetIXLan entries with your addresses at each IXP.
Does PeeringDB replace IRR and RPKI route filtering?
No. PeeringDB tells you who to peer with, where, and what limits to apply, but IRR (route and as-set objects) and RPKI (ROAs) decide which prefixes a partner may legitimately announce. The sources complement each other.
Where do tools get the max-prefix limit from?
Many BGP configuration generators pull the max-prefix value directly from the PeeringDB record and apply it as a protective limit on the session. That is why it is worth keeping realistic, current values there for both IPv4 and IPv6.