Tool guideNetwork Diagnostics

IXP & Peering Explorer – Complete Guide to PeeringDB, Internet Exchanges, Facilities and Peering Policies

What PeeringDB, Internet Exchanges, route servers and peering policies are, how the NetTools.tech IXP & Peering Explorer searches networks, exchanges and facilities, how to read every field, and why PeeringDB is self-published metadata rather than routing evidence.

By NetTools.tech · · 11 min read

Before you request peering, order a cross-connect or pick a colocation site, you need to know where the other network is present: which Internet Exchanges it is connected to, which data centers it is in, what its peering policy is and how to reach its peering team. That information is published by the networks themselves in PeeringDB, spread over network, exchange and facility records.

The IXP & Peering Explorer reads those records for you. Search by AS number or by a network, exchange or facility name, then move between a network's IX connections and facilities, an exchange's member list and a data center's tenants. Everything on the page comes from PeeringDB and is labelled as what it is: self-published metadata, not proof of how traffic is routed.

What is an IXP & Peering Explorer?

In simple terms

Networks exchange traffic either by paying a transit provider or by peering: connecting directly and exchanging their own and their customers' traffic, often without payment. Peering usually happens at an Internet Exchange Point (IXP), a shared switch where many networks have a port, or over a private cable between two networks in the same facility (data center). PeeringDB is the shared directory where networks say where they are and on what terms they peer. A peering explorer is a convenient way to browse that directory.

Technical background

TermMeaning
Internet Exchange (IX, IXP)A layer-2 peering fabric. Each member gets a port and IP addresses on the exchange's peering LAN and sets up BGP sessions with other members.
Bilateral peeringA BGP session agreed directly between two members.
Route serverA BGP speaker run by the exchange that collects members' routes and passes them on, so one session reaches many members (RFC 7947). It does not forward traffic.
Private network interconnect (PNI)A direct cross-connect between two networks in a shared facility.
Peering policyThe terms a network states: Open, Selective, Restrictive (PeeringDB also allows No), plus optional requirements such as locations, ratio and contracts.
IRR as-setThe Internet Routing Registry object peers use to build prefix filters for the network's routes.
Prefix countsIn PeeringDB these are the numbers of IPv4 and IPv6 prefixes the network expects to announce, which peers typically use as maximum-prefix limits on their sessions.

PeeringDB organizes data into objects. The tool uses networks (net), a network's IX connections (netixlan) and facilities (netfac), exchanges (ix), exchange facilities (ixfac), facilities (fac) and points of contact. A netixlan entry is one port of one network on one exchange LAN, with its speed, its peering IP addresses and whether it peers with the route servers.

Why use the IXP & Peering Explorer?

  • Find common exchanges and facilities with a network you want to peer with.
  • Read a peering policy and its requirements before sending a request.
  • Get the peering IP addresses of a network on an exchange to configure a bilateral session.
  • Check route server participation when deciding between bilateral sessions and the route servers.
  • Evaluate an exchange or data center: who is connected, at what capacity, and which other exchanges are in the same building.
  • Find a published contact (by role) for a NOC or peering request.

Who should use it?

Peering coordinators and network engineers at ISPs, content, hosting and cloud providers, IX and data center sales or operations staff checking their listings, network architects choosing interconnection sites, and NOC staff who need a public contact for another network. Anyone investigating actual routing should combine it with the BGP Looking Glass and the ASN Explorer.

How the IXP & Peering Explorer works

The browser sends your query to the NetTools.tech API, and the NetTools server queries the PeeringDB API (https://www.peeringdb.com/api) — the only source this page uses. When the site operator has configured a PeeringDB API key it is sent from the server as an Authorization header; it never reaches the browser. Without a key the server queries PeeringDB anonymously with lower request pacing.

What each view requests:

ViewPeeringDB requests
Network (?asn=)net for the ASN with depth 2, which includes the network's IX connections, facilities and contacts
Search (?q=)net, ix and fac with a name-contains search, up to 25 results each; an AS number searches networks only
Internet Exchange (?ix=)the ix record, its netixlan connections, the member net names and its ixfac facilities
Facility (?fac=)the fac record, the networks (net) and exchanges (ix) present there

Normalization. A network's ports on the same exchange are combined into one row: the number of connections, their summed capacity, all peering IPs, and Route server Yes if any port peers with the route servers. Exchanges are sorted by capacity, facilities by country and name, members by capacity. Only contacts the network marked Public are shown, by role (for example NOC or Policy) with their e-mail, URL or phone; personal names are not displayed. Empty fields stay empty.

Limits and caching. Exchange member lists are read up to 1,500 networks; for very large exchanges the page notes that the list may be incomplete. Each request has a 25-second timeout and one retry on timeouts, HTTP 429 and server errors, and requests are paced to stay within PeeringDB's limits. Network, exchange and facility records are cached on the server for up to 6 hours, searches for 1 hour.

How to use the NetTools.tech IXP & Peering Explorer

  1. Open the IXP & Peering Explorer.
  2. In ASN, network, Internet Exchange or facility, enter:
    • an AS number (AS13335 or 13335) to open that network's record directly, or
    • at least two characters of a name (DE-CIX, AMS-IX, Equinix) to search networks, exchanges and facilities. You can also click one of the examples.
  3. Press Search. A name search shows three columns: Networks, Internet Exchanges and Facilities, each with up to 25 matches.
  4. Click a result to open it. Every exchange, facility and network name in the results is a link, so you can move from a network to an exchange it is on, to a member of that exchange, to a facility, without leaving the page. Back and forward work.
  5. From a network, continue to BGP routes of AS… (the BGP Looking Glass) or the ASN Explorer; View PeeringDB record opens the original.
  6. Export with CSV, JSON, Copy all or Print. Member and network lists in the export are complete even when the page shows only the first 300 or 600 rows.
  7. Share the URL: /peering?asn=13335, /peering?ix=<PeeringDB ID>, /peering?fac=<PeeringDB ID> or /peering?q=<search>.

Understanding the results

Network view

ResultMeaningWhat to look for
NetworkName, with "also known as" or long nameSeveral networks with similar names: check the ASN
Peering policyOpen, Selective, Restrictive, No or Not statedWhether a policy document is linked
Internet Exchanges / FacilitiesNumber of exchanges (and connections) and facilitiesOverlap with your own presence
Network type, traffic levels, traffic ratio, geographic scopeAs stated by the networkSelf-reported categories, not measurements
IPv6 support, unicast / multicastPublished flags–
Prefixes (IPv4 / IPv6, as published)Expected number of announced prefixesUse for max-prefix limits, not as a count of routes
IRR as-setObject for building prefix filtersMissing as-set makes filter generation harder
Never via route serversThe network asks not to be reached through route serversPlan a bilateral session instead
Policy locations, ratio requirement, contractPolicy detailsRequirements you must meet
Looking glass, route serverURLs the network publishes–
Record updatedLast change in PeeringDBVery old records may be out of date
Internet Exchange connectionsExchange, connections, capacity, route server, peering IPs (first four per row); first 15 rows, Show all for moreThe peering IPs for your session
FacilitiesFacility with city and country; first 24, Show all for moreCandidate sites for a PNI
Public contactsRole with e-mail, URL or phoneUse the role that matches your request

Internet Exchange view

ResultMeaningWhat to look for
NetworksMember count as stated by PeeringDBMay differ from the listed members
Route server peersMembers with at least one route server port, of those listedHow much you can reach over the route servers
Facilities, IPv6Buildings where the exchange is available; IPv6 Supported, No or Not stated–
MembersASN (links to the ASN Explorer), network, capacity, route server; filter by ASN or nameLarge members and route server participation

Facility view

ResultMeaningWhat to look for
Networks, Internet ExchangesTenants and exchanges published for the buildingPotential PNI partners
Location, address, CLLI, websiteFacility detailsCLLI is a telecom location code, often empty outside North America
Record updated, PeeringDBLast change and a link to the original record–

The Sources & freshness box under every view shows the PeeringDB request, when NetTools fetched it, whether it came from the cache and a link to the record at PeeringDB.

Example: from an exchange to a peering session

  1. Search for DE-CIX. The Internet Exchanges column lists the PeeringDB exchanges whose names contain that string, with city, country and the network count PeeringDB states. Networks and facilities whose names match appear in the other columns.
  2. Open one exchange. The KPI cards show the member count, how many listed members peer with the route servers, the facilities and IPv6 support. Filter the member list by the ASN you are interested in.
  3. Click the member's name to open its network record and check the Peering policy, Never via route servers and the Internet Exchange connections table.

An IX connection row then reads like this (illustrative values with documentation addresses, not real output):

Internet Exchange   Connections   Capacity    Route server   Peering IPs
Example-IX          2             20 Gbit/s   Yes            192.0.2.10
                                                             198.51.100.10
                                                             2001:db8::10

Read it as: the network has two ports on that exchange with a combined 20 Gbit/s, at least one of them peers with the route servers, and those are the addresses to configure if you agree a bilateral session. It does not tell you whether the network will accept your session, or that it announces any particular prefix there; check the policy and contact the published Policy or NOC role, and use the BGP Looking Glass for routes.

Common use cases

  • Peering request preparation: common exchanges, policy, as-set, max-prefix values and contact in one view.
  • Session configuration: the peer's IPv4 and IPv6 addresses on a shared exchange.
  • Site selection: compare which networks are present in candidate facilities and exchanges.
  • Listing check: verify that your own network, exchange or facility record shows what you expect, and when it was last updated.
  • Contact lookup: find a public NOC contact for another network.

Troubleshooting

"No network matches" for a well-known company

Name search matches PeeringDB record names, which are often brand or network names rather than company names. Search by AS number, a shorter part of the name, or the name of an exchange where the network is present.

"AS… has no PeeringDB record"

The network has not published one. This is common and says nothing about its routing; use the ASN Explorer for the registry holder and announced prefixes.

"Enter at least two characters"

Searches need two characters or more. A pure number is treated as an ASN and opens the network record.

"PeeringDB has no Internet Exchange with this ID" / "… no facility with this ID"

The ix or fac ID in the URL does not exist or the record was deleted. Search by name instead.

"PeeringDB is busy" or "is rate limiting requests"

NetTools paces requests to PeeringDB and stops waiting after about 20 seconds; PeeringDB may also throttle. Try again in a minute. If the message says PeeringDB rejected the NetTools credentials, the server's API key needs attention from the site operator.

Member list "may be incomplete"

Very large exchanges exceed the 1,500 networks NetTools reads per exchange. Search for the specific network instead.

Common mistakes

  • Treating an IX connection as an active peering. It is a port on the exchange, not a BGP session with you or anyone else.
  • Treating PeeringDB as routing evidence. For what a network actually announces, use the BGP Looking Glass.
  • Reading capacity as traffic. Capacity is the summed port speed; traffic levels are a self-reported range.
  • Reading published prefix counts as announced routes. They are the network's expected numbers for max-prefix limits.
  • Relying on an outdated record. Check "Record updated"; networks maintain their own entries.
  • Assuming the member count and the listed members are equal. The KPI uses PeeringDB's count; the table lists the connections PeeringDB returns.

Limitations

  • Self-published data: accuracy depends on each network, exchange and facility keeping its record up to date; fields are optional.
  • One source: only PeeringDB. Networks without a record, and exchanges or facilities not listed, are invisible here.
  • No routing or session data: the tool cannot tell whether a BGP session is up, which routes are exchanged or how much traffic flows.
  • Search scope: name search returns up to 25 matches per type; large member lists are capped at 1,500 networks.
  • Cached: up to 6 hours for records and 1 hour for searches.

Security & privacy

The explorer is read-only: it queries PeeringDB from the NetTools server and never connects to the networks, exchanges or route servers it lists. Your search term or ID is sent to the NetTools.tech API and from there to PeeringDB; your browser contacts PeeringDB only if you follow a link to the original record. The API key, when configured, stays on the server. Only contacts that networks marked Public are shown, by role. Queries contain nothing secret, so there is no reason to enter internal information. See the privacy policy.

Summary

The IXP & Peering Explorer turns PeeringDB's network, exchange and facility records into linked views: where a network peers, under which policy and with which addresses, who is on an exchange and who is in a building. It is the right starting point for peering requests and site selection. Treat everything it shows as what the networks publish about themselves, and confirm actual routing with the BGP Looking Glass.

Frequently asked questions

What is PeeringDB?

PeeringDB is a freely available database where networks, Internet Exchanges and facilities publish their interconnection details: which exchanges and buildings they are in, their peering policy and how to reach their NOC. Network operators use it to plan and configure peering.

Does an IX connection in PeeringDB mean two networks exchange traffic?

No. It means the network has a port on that exchange. Whether two members actually peer, directly or through the route servers, depends on their BGP sessions and policies, which PeeringDB does not show.

What do Open, Selective and Restrictive peering policies mean?

They are the general policy a network states in PeeringDB. Open means it generally peers with anyone at common locations, Selective means it peers under conditions such as traffic volume or ratio, and Restrictive means it rarely accepts new peers; the tool shows Not stated when the field is empty.

What does Route server Yes mean?

The network marked at least one of its connections at that exchange as peering with the exchange's route servers. Route servers let members receive many members' routes over one BGP session instead of configuring a session with each member.

Why does a network have no PeeringDB record?

Records are created by the networks themselves, and many networks never publish one. A missing record says nothing about how the network is routed; use the BGP Looking Glass or ASN Explorer for routing data.

Why are some fields empty or shown as Not stated?

Most PeeringDB fields are optional and filled in by the network. NetTools shows empty fields as not stated or leaves them out rather than guessing a value.

How current is the information?

Each record shows when it was last updated in PeeringDB. NetTools caches network, exchange and facility records for up to 6 hours and searches for up to 1 hour, and the Sources & freshness box says when the data was fetched.