Introduction & Update
Arnold Nipper, arnold@peeringdb.com

What is PeeringDB?
Mission statement: “PeeringDB, a nonprofit member-basedorganization, facilitates the exchange of user maintainedinterconnection related information, primarily for Peering Coordinators
and Carrier, Internet Exchange, Facility, and Network Operators.”•••

A PeeringDB record makes it easy for people to find you,and helps you to establish peering
If you aren’t registered in PeeringDB, you can register athttps://www.peeringdb.com/register
We use basic verification for new accounts and requirecurrent whois information, so please••

Update and maintain your whois information
Register from an email address associated with your ASN /company
SANOG41 & INNOG7, Mumbai, India?
…
2

What is PeeringDB?
Why should my carrier, exchange, network or facility be listed inPeeringDB?
• Helps establish new peering more efficiently, with all information easy
to find in one place•••••

Maintain all of your contact and connection info
Find other network's peering contact and connection info
Find interconnection facility and IXP info

A PeeringDB record is required by many networks to peer
Can be used for automation to generate router configurations••

Initial configuration to setup peering quickly
Update configuration if maximum prefixes change
SANOG41 & INNOG7, Mumbai, India

3How to access PeeringDB?
•••

Provides a GUI and an API
The GUI nicely puts together what you
can retrieve via the API separately
The API is useful for automating andmass info retrieval•

See https://www.peeringdb.com/apidocs/
for more information

SANOG41 & INNOG7, Mumbai, India

4

Governance and Membership•••PeeringDB is a United States 501(c)(6) volunteer organization that is 100% fundedby sponsorships
Healthy organization, building financial reserves and executing the long term
strategic plan
Membership rules••••••

A corporation, limited liability company, partnership or other legal business entity may be a
Member of the Corporation
Membership is determined by having both an active PeeringDB.com account and an individual
representative or role subscription to the PeeringDB Governance mailing list
480 addresses subscribed to the Governance mailing list (as of April 15, 2024)
Elections every year, renewing half of the board. Closing at 2024-04-29T23:59Z
Governance list is at https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov
More information available at https://docs.peeringdb.com/gov/
SANOG41 & INNOG7, Mumbai, India5

Board of Directors and Officers

Chris Caputo – Secretary andTreasurer (Officer)

Aaron Hughes – Vice President(Term Expires 2024)

Rahul Makhija – Director(Term Expires 2025)

Christopher Malayter – President(Term Expires 2025)

Livio Morina – Director(Term Expires 2025)

Job Snijders – Director(Term Expires 2024)

SANOG41 & INNOG7, Mumbai, India

6Committees
Admin Committee•••

Manage administration ofuser accounts andPeeringDB records
Answer support tickets
Cleansing and completionof PeeringDB records

Operations Committee•

Manage PeeringDB
infrastructure•••

Leads: Patrick Gilmore (Chair) Leads: Job Snijders (Chair)Contact: admincom@
and Aaron Hughes (Vicelists.peeringdb.com
Chair)
Contact: pdb-ops@
lists.peeringdb.com

Outreach Committee

Product Committee

Manage marketing and social •media
Develop and maintain•presentations, workshops
and webinars
Coordinate presentations•and attendance at events

Manage roadmap anddevelopment priorities
Ask for input from thecommunity on desiredfeaturesWrite SoWs to solicit bids tocomplete requestedfeatures

Leads: Ben Ryall (Chair) andBijal Sanghani (Vice Chair)Contact: outreachcom@
lists.peeringdb.com

SANOG41 & INNOG7, Mumbai, India

Leads: Stephen McManus(Chair) andMatt Griswold (Vice Chair)
Product Manager: Leo Vegoda
Contact: productcom@
lists.peeringdb.com

7

Product Development Workflow•

All issues tracked using GitHub at https://github.com/peeringdb/peeringdb/issues••••

Product Committee issue process•••••Anyone can open a feature requests or file a bug report
Open and transparent process for product development
Workflow is at http://docs.peeringdb.com/workflow/
Evaluate and prioritize the requests
Request a quote for development costs
Request budget from the board
Manage implementation and schedulingYour input is needed on features!

SANOG41 & INNOG7, Mumbai, India

8

Release Process•

Announced at least one week in advance with all changes to give thecommunity notice•••

Released on Wednesdays at 0400Z and avoids••••

Beta site is already running the development version for testingAnnounced on PDB Announce list, Twitter, Facebook
Mondays and Fridays
International holidays
Large conferences and events (APRICOT, EPF, GPF, NANOG, RIPE, etc.)

List of current changes (release notes) for each version are on GitHub athttps://github.com/peeringdb/peeringdb/milestones
SANOG41 & INNOG7, Mumbai, India

9

Beta Development•

Beta server
•
••
•

•

Latest changes••••

Available at https://beta.peeringdb.com/
Runs the latest beta software version
Full access over HTTP and the API
Database is local to the beta server only, changes are not reflected on the production servers
Available at https://beta.peeringdb.com/changes
Redirects to the list of issues on GitHub
Documents all of the changes in the current beta version

Anyone can log bugs and feature requests in GitHub athttps://github.com/peeringdb/peeringdb/issues

SANOG41 & INNOG7, Mumbai, India

10Updates
News from the Frontlines
••
•
•
•

Web UI design changes
New KMZ export feature
Improved search
Beta testing
Call for Volunteers

SANOG41 & INNOG7, Mumbai, India

11

Web UI
Planned Improvements• Better device presentation• Dashboard options• Lazy loading

SANOG41 & INNOG7, Mumbai, India

12New KMZ Features
Facility Data• Locations and metadata• Exported daily• Importable to Google Maps

Later this year
• Export searches to KMZ• Improved visual attributes
SANOG41 & INNOG7, Mumbai, India

13

Search (pending release)
Search is getting better••••

Location support
Object type searching
Boolean operators
Refined results

SANOG41 & INNOG7, Mumbai, India

14

We Need Beta Testers
Consider using the Beta environment as default•

Just over half a percent of users visit beta.peeringdb.com each month•

We recognize that there are good and bad reasons for this!

•As of release 2.57.0, beta.peeringdb.com refreshes once an hour
Early access to improvements
Easy feedback mechanism
Try it at https://beta.peeringdb.com•Contact us at pc@peeringdb.com with any questions•••

SANOG41 & INNOG7, Mumbai, India

15

Call for Volunteers•

Admin Committee•••

Answer user support questions
Suggest improvements based on experience
Only apply if you have free slots at least four days the weekfor 15 minutes

Email us at admincom@lists.peeringdb.com for more info.
SANOG41 & INNOG7, Mumbai, India

16

Tracking Growth
End of 2023, and growthon 2022•••••SANOG41 & INNOG7, Mumbai, India

Facilities: 5,282• 6% increase
IXs: 1,152• 8% increase
Networks: 29,148• 10% increase
Orgs: 27,174• 10% increase
Users: 41,975• 10% increase
17

SANOG from PeeringDB POV
CC

IXP

ASN

LASN

Colo

ASN

LASN

PDB

RIR

AF

1/1

15

130/0

00

15

1326

62

BD

10/10

114

107

33/32

1715121

113

507

1744

BT

1/1

128

3/3

111281534IN40/21

906

785

221/59

704

576

1106

926

1370

5782

LK

0/0

00

1/1

0000

929

MM

2/1

2720

6/5

32272063

159

MV

1/1

85

1/1

2285

1018

NP

2/1

32

28

6/6

223228

65

183

PK

2/2

44

18/17

117

139157374

LASN: Local ASN, ie. ASN in CC

TASN TLASNTASN: Total ASN (IXP + Colo) TLASN: Total Local ASN
SANOG41 & INNOG7, Mumbai, India

18

Thank you to our sponsors!
DiamondSponsorPlatinumSponsors

GoldSponsors

SilverSponsors
SANOG41 & INNOG7, Mumbai, India

19