All integrationsUtilities

PeeringDB

Look up who connects where on the internet, from PeeringDB's public database of networks, Internet exchanges and data centres.

actions
20

Actions

Steps a workflow can run in PeeringDB.

  • Search networksFind networks in PeeringDB by any mix of name, a list of AS numbers, network type, peering policy, where they operate, their traffic level and ratio, an exchange or facility they are at, the organization that runs them, or when they last changed. Each comes back with its AS number, policy, AS-SET, suggested prefix limits and how many exchanges and facilities it is at. No API key required.
  • Get a networkRead one network's full PeeringDB record by its PeeringDB id: its AS number, peering policy and where to read it, AS-SET, suggested prefix limits, traffic, looking glass, the organization behind it, its notes, and its public contacts with the NOC, abuse and peering emails picked out. No API key required.
  • Get a network by ASNRead the PeeringDB record of the network using an AS number: its name, peering policy, AS-SET, suggested prefix limits, the organization behind it and its public contacts with the NOC, abuse and peering emails picked out. An AS number nobody has registered comes back with 'found' set to false rather than failing the step. No API key required.
  • List a network's exchange connectionsList every port a network has at Internet exchanges: the exchange, the port speed, its IPv4 and IPv6 addresses, whether it peers with the route servers and whether it is in service, with the total capacity. Narrow to one exchange to check whether a network is there. No API key required.
  • List a network's facilitiesList the data centre facilities a network says it is in, with each facility's city and country, for finding where two networks could connect privately. Narrow to one country. No API key required.
  • Search exchangesFind Internet exchanges by name, country, city, continent, the organization that runs them, a facility they can be reached in, or when they last changed. Each comes back with its PeeringDB id, location, how many networks and facilities it has, and its support and commercial terms. No API key required.
  • Get an exchangeRead one Internet exchange's PeeringDB record: where it is, who runs it, how many networks and facilities it has, its technical, peering and sales contacts, its traffic statistics page, and its peering LANs with their MTU and route server AS number. No API key required.
  • List an exchange's membersList the networks connected to an Internet exchange, one row per port: the network's name, AS number and peering policy, the port speed, its IPv4 and IPv6 addresses and whether it peers with the route servers. Narrow to route server users or to fast ports. No API key required.
  • List an exchange's peering LAN prefixesList the IPv4 and IPv6 address ranges of an exchange's peering LANs, the addresses its members use to peer, and whether each range is announced to the wider internet. Handy for filters and for spotting exchange addresses in routing data. No API key required.
  • List an exchange's facilitiesList the data centre facilities an Internet exchange can be reached in, with each one's city and country, sorted by country and city. No API key required.
  • Search facilitiesFind data centre facilities by name, country, city, continent, the organization that runs them, the campus they are on, or when they last changed. Each comes back with its PeeringDB id, address, coordinates, and how many networks, exchanges and carriers are in it. No API key required.
  • Get a facilityRead one data centre facility's PeeringDB record: who runs it, its full address and coordinates, how many networks, exchanges and carriers are in it, its sales and technical contacts, power options and notes. No API key required.
  • List networks at a facilityList the networks in a data centre facility, with each one's AS number, type and peering policy, for finding who could be reached with a cross connect there. Narrow by network type or peering policy. No API key required.
  • List exchanges at a facilityList the Internet exchanges that can be reached in a data centre facility, with each one's location and how many networks it has. No API key required.
  • Search organizationsFind the companies and institutions behind networks, exchanges and facilities, by name, country, city, the AS number of a network they run, or when they last changed. Each comes back with its PeeringDB id, address and website. No API key required.
  • Get an organizationRead one organization's PeeringDB record: its address and website, and the PeeringDB ids of every network, facility, exchange, carrier and campus it runs, with how many of each. No API key required.
  • Search carriersFind carriers, the companies that run fibre and circuits between facilities, by name, the organization behind them, or when they last changed. Each comes back with its PeeringDB id and how many facilities it serves. No API key required.
  • Get a carrierRead one carrier's PeeringDB record, with every facility it offers connections in, by name and PeeringDB id. No API key required.
  • Search campusesFind campuses, groups of facilities close enough together to be treated as one site, by name, country, city, the organization behind them, or when they last changed. Each comes back with the PeeringDB ids of its facilities. No API key required.
  • Look up an exchange IP addressFind whose port an IPv4 or IPv6 address is at an Internet exchange, such as a BGP neighbour's address: the network's name and AS number, the exchange, the port speed and the network's other address on the same port. An address that is not on any exchange comes back with 'found' set to false rather than failing the step. No API key required.

Automate PeeringDB with Lodol.

Connect PeeringDB and ask your AI for your first workflow.

Free plan, no credit card