PeeringDB wants input from everyone who uses our interconnection database. Our anonymous survey is now open until 23:59 UTC on 16 October 2022. We would like your feedback to help us make PeeringDB more useful to everyone involved in connecting networks.
Take the PeeringDB 2022 user survey
We had around 250 responses to last year’s survey that helped guide our product development. Key changes delivered so far in 2022 include:
● Adding an API Key support to peeringdb-py
● Adding FIDO U2F 2FA support to the PeeringDB website
● Normalizing place names
We’ve also published more documents in our HOWTO documentation series.
“The 2021 survey helped us focus development where it was most needed. We used it to develop our roadmap. We are still implementing things we have learned from previous surveys but want your input on how we should adapt. Please take a few moments of their time to help us make PeeringDB a better service!”Steve McManus, PeeringDB Product Committee Chair
What’s new in 2022
In 2022 we have added a couple of extra questions. We’d like to know how many people use PeeringDB at your organization. We’d also like to know how you use it: Either via the web, API, or a local cache. We will use your answers to focus development work where it is most needed.
The survey is available in the six UN languages, Portuguese, and Ukrainian. Please provide comments in whatever language you want to express yourself.
We’ll share the results and the new product roadmap early in 2023.
Take the survey to help guide PeeringDB’s future development.
If you have an idea to improve PeeringDB you can share it on our mailing lists or create an issue directly on GitHub. If you find a data quality issue, please let us know at: firstname.lastname@example.org.
PeeringDB is a freely available and user-maintained database of networks, and the go-to location for interconnection data. The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centers, and other interconnection facilities, and is the first stop in making interconnection decisions.
Leo Vegoda is developing PeeringDB’s product roadmap.
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.