Please log bugs and feature requests at GitHub.
Several PeeringDB mailing lists are listed below.
Questions, comments and everything else should go to firstname.lastname@example.org.
We have changed the way in which PeeringDB will be announcing future enhancements, changes, maintenance windows, and other information. If you would like to be notified of certain events, or participate in certain discussions, please subscribe to one of the following email lists:
All PeeringDB administrative information, such as upgrades,
maintenances, outages, etc.
Discussion list for PeeringDB governance issues This is a
community-based effort, the community’s input will help guide the
future of the PeeringDB (as it has always done).
Discussion of the back end of PeeringDB & other technical topics
All other list traffic.
Our goal is to give you all the information you want, and no more. Please subscribe to any of these lists you feel are appropriate, or none. You will still be able to use the database even if you are not subscribed to any lists.
PeeringDB is available at https://www.peeringdb.com/ with self-describing API docs at https://www.peeringdb.com/apidocs/. More thorough docs are at API Specs, but in a nutshell, just prepend the URL with
api/ to get that object in JSON.
List all via API by taking the
- [es] Guía corta para uso de peeringdb.com - Fabián Mejía
- PeeringDB Update at TOP-IX Meeting, Torino, IT - September 26, 2017 - Bijal Sanghani
- PeeringDB Update at NPD 17, The Hague, NL - September 15, 2017 - Arnold Nipper
- PeeringDB Update at SAFNOG-3, Durban, ZA - September 6, 2017 - Arnold Nipper
- PeeringDB Update at AfPIF 2017, Abidjan, CI - August 24, 2017 - Arnold Nipper
- PeeringDB Update at SANOG 30 Peering Forum, Gurgaon, IN - July 10, 2017 - Arnold Nipper
- More benefits from PeeringDB at DE-CIX Technical Meeting, Frankfurt, DE - June 22, 2017 - Arnold Nipper
- PeeringDB Update at NANOG 70, Bellevue, WA, US - June 5, 2017 - Aaron Hughes
- PeeringDB Update at BOSNOG Meeting & IX Peering Forum, Cambridge, MA, US - June 2, 2017 - Stephen McManus
- Orientações no preenchimento de participantes do IX.br at GTER 43, Foz do Iguaçu, BR - May 25, 2017 - Julimar Lunguinho Mendes
- PeeringDB Update at ENOG 13.0, Saint Petersburg, RU - May 23, 2017 - Arnold Nipper
- PeeringDB Update at Global Peering Forum 12.0, New York, NY, US - April 26, 2017 - Aaron Huges
- PeeringDB at GORE/ESNOG Reunion 19, Barcelona, ES - April 6, 2017 - Arnold Nipper
- PeeringDB at CEE Peering Days 2017, Ljubljana, SL - March 23, 2017 - Arnold Nipper
- PeeringDB 2.0 at APRICOT 2017, Ho Chi Minh City, VN - February 28, 2017 - Arnold Nipper
- PeeringDB at 19 KIKE Conference, Serock, PL - November 23, 2016 - Robert Jakub
- PeeringDB 2.0 at ITNOG2, Bologna, IT - November 3, 2016 - Arnold Nipper
- PeeringDB Product Committee Charter Survey at EPF 11, Sofia, BG - September 20, 2016 - Eric Loos
- PeeringDB 2.0 at NPD 16, The Hague, NL - September 16, 2016 - Walt Wollny
- PeeringDB 2.0 at AfPIF 2016, Dar es Salaam, TZ - August 30, 2016 - Arnold Nipper
- PeeringDB 2.0 for IXPs at AFIX 2016, Dar es Salaam, TZ - August 29, 2016 - Arnold Nipper
- PeeringDB 2.0 at ENOG 11, Moscow, RU - June 7, 2016 - Arnold Nipper
- PeeringDB 2.0 at RIPE 72, Copenhagen, DK - May 25, 2016 - Greg Hankins
- PeeringDB 2.0 at CHI-NOG 06, Chicago, IL, US - May 12, 2016 - Matt Griswold
- PeeringDB 2.0 e o Cenário Brasileiro and IX.br Guia de cadastro de informações de ASNs no PeeringDB at GTER 41, Uberlândia, BR - May 12, 2016 - Eduardo Ascenço Reis
- PeeringDB 2.0 for IXPs at 28th Euro-IX Forum, Luxembourg, LU - April 26, 2016 - Greg Hankins / Arnold Nipper
- RIPE SEE 5, Tirana, AL - April 19, 2016 - Arnold Nipper
- PeeringDB 2.0 at UKNOF34, Manchester, UK - April 21, 2016 - Greg Hankins
- PeeringDB Update at GPF 11, Los Angeles, CA, US - April 13, 2016 - Aaron Hughes
- NetNod, Stockholm, SE - March 17, 2016 - Job Snijders
- DKNOG6, Copenhagen, DK - March 10, 2016 - Job Snijders
- PeeringDB Update - Aaron Hughes
- PeeringDB Version 2 Coding Introduction at NANOG 66, San Diego, CA, US - February 8, 2016 - Matt Griswold
- PeeringDB Version 2 Brazil - Matt Griswold / Greg Hankins
- IX (PTT) Fórum 9, São Paulo, BR - December 8, 2015 - Greg Hankins
- PeeringDB Version 2 Introduction - Matt Griswold
This section lists tools for using PeeringDB, and tools that use PeeringDB.
django-peeringdb is a Django library with a local PeeringDB database sync. It defines the database schema to create a local database copy. The library is easy to integrate into a common framework for local tools and custom interfaces, and also supports multiple database engines (MySQL, Postgres, SQLite).
The Isolario project improve knowledge about the AS-level ecosystem of the Internet by increasing the amount of Autonomous Systems (ASes) from which BGP data is collected. Isolario offers network operators services based on the real-time analysis of inter-domain routing from different points of view in return for full routing tables.
Ixgen is yet another open source, multiplatform peering configuration generator that is based on the PeeringDB API. It can also run its own server for faster results. Ixgen is configured using an INI- or JSON-style format, and produces custom template-driven or fixed JSON-style configurations,
peeringdb-py is a Python client for PeeringDB. It features functions to get objects and display them in JSON or YAML format, and provides a whois-like display of records. The client also has an integrated local database sync, and provides a Python library for integration with custom tools. Some examples are available too.
Pinder is a tool that facilitates peering. If peering is desired between two networks, and you're happy to just configure sessions without a commercial agreement, Pinder acts as the middle man. You can submit the request via either a basic web UI or an API, and the other network is notified or can periodically check their outstanding requests. If both network agree to peer, they are notified to configure a session. Once both networks indicate that sessions are configured and established, the request is then deleted. A brief slide deck explains the functionality in more detail.
TraceMON is a tool for visualizing a network topology generated by traceroutes that provides one-click access to IXP and network information. It also displays PeeringDB information and allows the user to update their record. RIPE Atlas users can access it by selecting a traceroute measurement and clicking on the TraceMON tab.
The PeeringDB beta server is running the latest beta software version, with full access over HTTP and the API. Note that changes made to the beta database are local to the beta server only, and are not reflected on the production servers.
The latest changes to PeeringDB automagically redirects to the list of issues on PeeringDB's GitHub repository that document all of the changes in the current beta version.
- The PeeringDB 1.0 MySQL interface is gone. The last available MySQL dump is archived at https://www.peeringdb.com/v1/final_export.sql.
- MySQL dumps from July, 29 2010 to March 14, 2016 are archived by CAIDA at http://data.caida.org/datasets/peeringdb-v1/.
How you can help
Check your entries and make sure everything looks correct
Port any scripts to the new API
Send us feedback
Improve these docs
Thanks for your feedback, we look forward to hearing from you!