Welcome to our third half-yearly update. While we publish release notes with each update and promote new features and bug fixes on social media, these reports take a broader look at recent changes.
You can find our previous half-yearly reports here and here.
In 2025, PeeringDB’s board approved a 50% increase in spending on development and operations compared to 2024. All committees now have access to these resources, allowing us to complete more development work each month and devote more time to operational improvements.
People, process, and volunteer translations
The Product Committee’s membership has stabilized, and we are working more efficiently. More of our discussions are now asynchronous, which shortens decision times on proposed changes.
We still encourage users to submit feature requests and bug reports on GitHub. Please let us know whether you would use a proposed feature and how it would benefit you. You can share feedback via GitHub, our mailing list, or in person at industry events.
A new translation to Lithuanian was contributed by Saulius Jeraminas and deployed in our August release.
Get Involved: Help translate PeeringDB
PeeringDB depends on its community to make the platform accessible worldwide. It’s a simple process, and with a PeeringDB account, you can start contributing right away. New translations are added at the next scheduled release. If you are interested in contributing, please join the translation list to get support. Your work will be acknowledged.
Last six months
Comparison in search
Users can now compare networks at facilities. This feature was released in July, and we have already received two strong suggestions for improvement.
Based on the initial feedback, we will add comparisons to include Internet Exchange Points (IXPs) to augment the existing facility (data centre) comparison. We’ll also show the economies where facilities are based and make the columns sortable.
Web UI
We have begun a staged rollout of our new web UI. We started with PeeringDB volunteers and will next opt in 20% of users, who can choose to opt out.
The goal is to make better use of the screen space available to the 80% of visitors on larger displays, while improving rendering for the 20% of visitors using phones.
Additional columns, such as those for Bidirectional Forwarding Detection (BFD) support, have caused display issues, for example, long IPv6 addresses being obscured. Refinements to fix these are underway. Once complete, we will opt in more users while keeping the option to revert to the old design.
MFA mandate
Anonymous use remains available. However, authentication for extra queries or data changes now requires multi-factor authentication (MFA). Options include:
- API keys for API queries
- Backup codes
- Passkeys
- Time-Based One-Time Passwords (TOTP)
- U2F hardware security tokens
We announced this change well in advance, and no users have been locked out. Accounts can be recovered via email.
We saw a small spike in users just before the MFA requirement came into effect, but overall usage remains in line with the past year.
Address normalization
Over the past year, we have standardized address formatting using Google and Melissa services. Four elements are now normalized:
- Economy names
- Province / state names
- City names
- Street names
A few anomalies remain and will be corrected in the coming weeks.
Coming up
Website
You may see the new web UI in the next few months. If you are opted in and prefer the old design, you can switch back in your profile settings.
Once search improvements are complete, we will focus on enhancing configuration and profile management. We will then add lazy loading to speed up text display in browsers.
Comparison
Early adopters of the Autonomous System Number (ASN) comparison tool have suggested valuable improvements. We will implement these and welcome more ideas. Tell us how this feature could be made more useful for your work or automation tasks.
Behind the scenes
We are completing our migration to containers and introducing service-level indicators to detect when the site is up but loading slowly.
Recent incidents have shown that heavy query loads from development work can affect performance. We are working on ways to maintain high availability, even when query limits are exceeded.
All PeeringDB data is also available for query through a local mirror: peeringdb-py. This has been improved and is now easier to install and update.
If you have ideas for improving PeeringDB, you can share them on our low-traffic mailing lists or raise an issue directly on GitHub. For data quality issues, contact support@peeringdb.com.
PeeringDB is a freely available, user-maintained database of networks and the go-to location for interconnection data. The database facilitates the global interconnection of networks at IXPs, data centres, and other interconnection facilities, and is the first stop in making interconnection decisions.
Leo Vegoda is PeeringDB’s Product Manager.
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.