PeeringDB lookup

What this tool checks

PeeringDB is the shared database where networks publish how and where they interconnect. This tool reads a network's public PeeringDB record by AS number and shows:

• the network's name, type, scope, IRR as-set and the prefix counts it expects peers to accept (for max-prefix limits);
• its peering policy: open, selective, restrictive or none, with the policy URL, location and ratio requirements and whether a contract is needed;
• every internet exchange (IXP) port: exchange name, port speed, IPv4 and IPv6 peering addresses, and whether it peers with the route servers;
• the facilities (data centres) it is present in;
• its public role contacts (NOC, policy, technical, abuse), shown as role and email address only.

The data comes from PeeringDB's public API without logging in. Only contacts the network has marked public are visible, and personal names and phone numbers are left out. PeeringDB limits anonymous lookups, so each AS number is cached for an hour. If PeeringDB is busy, the tool says so, and it shows what it could load.

PeeringDB contains what networks enter themselves, so it can be out of date. For what a network actually announces, use the ASN & BGP lookup.

Reading the results

• AS is in PeeringDB as … - a pass: the network has a record.
• Peering policy - for information, with what the policy usually means in practice.
• Present at N internet exchanges with N ports - for information, with the total port capacity.
• No internet exchange ports are listed - for information. The network may peer only privately, or not at all.
• No IRR as-set is listed - a warning. Peers and route servers use the as-set to build prefix filters.
• No public NOC, policy or technical contact - a warning. Other networks have no published way to reach the operators.
• The record was last updated - for information when it has not changed for two years.
• No PeeringDB record - for information. Many networks that do not peer publicly never create one.

Ports marked "not operational" are greyed out. Exchange and facility names link to their PeeringDB pages.

Common problems and fixes

Missing or outdated as-set

Create an as-set in your RIR's IRR database (or another IRR such as RADB) listing your AS and your customers' AS numbers or as-sets, then enter it in your PeeringDB record:

as-set:   AS64496:AS-CUSTOMERS
members:  AS64496, AS64497

Max-prefix values out of date

Peers set max-prefix limits from the IPv4 and IPv6 prefix counts in PeeringDB. If you announce more routes than that, sessions can be torn down. Keep the values above your real count with headroom, and update them before you grow.

No reachable contact

Add role addresses that a team watches, such as noc@example.net and peering@example.net, with visibility "Public". Personal addresses go stale when people leave.

Exchange ports missing

Most exchanges update PeeringDB themselves, but some leave it to members. Add the connection under your network's exchange points, with the IP addresses the exchange assigned.

FAQ