PeeringDB is a widely used resource for interconnection data, and in these regular updates, we help users keep track of how the platform evolves. This report summarises significant PeeringDB changes over the last six months.
As usual at PeeringDB, we've been publishing notes with every release and sharing updates on new features and bug fixes via social media. In this report, though, we want to step back and look at the broader sweep of change and what it means for users. You can find our previous half-yearly reports here: one, two, three.
Operational changes
We’ve now completed our transition to Kubernetes. This gives us more flexibility and allows us to scale faster when needed, improving reliability as the platform continues to grow.
We’ve also implemented rate limiting for unauthenticated web users. We saw unprecedented activity from automated web scrapers in late 2025. Previously, we only rate limited API users, both because humans don’t search fast enough to cause problems and because most users search once, get their result, and move on.
But since automated scraping did start to cause problems, these requests are now limited to 120 queries per minute. We’ll review and adjust this threshold based on operational experience.
ASN comparison is better
We've made several improvements to the ASN comparison feature in advanced search. You can now:
- Input a list of ASNs as text or use our autocomplete function
- Perform comparisons at both exchanges and facilities
- See which countries matches are in
- Dynamically filter results on the page
Data quality
We have normalised more location data. We do this because it makes search and data analysis simpler when a single place has a single name. We also know that some users prefer a particular spelling, so we support multiple inputs.
We normalise the presentation of data while allowing users to search for locations in any language. For example, you can search for interconnection facilities in київ, but will see results for Kyiv.
We now normalise all countries to their ISO 3166 codes. We also do this for internal divisions within countries, such as provinces and states where relevant. We don't apply this everywhere, as internal divisions aren’t always necessary.
Please let us know if we need to improve location data normalisation for a particular country.
Expanding the 'copy an API query' feature
In March 2025, we added a feature that lets users generate properly formatted API queries for basic searches. We've now expanded this feature to support advanced search, making it more useful and helping users get more from PeeringDB in less time.
As before, queries can be formatted for curl, Python, JavaScript, Go, Ruby, and PHP.
Looking forward
We are examining ways to support AI-assisted software development for PeeringDB. We anticipate demand from users who want to develop and contribute features, whether in the service we operate or in a local mirror used under the terms of our AUP.
A key concern will be ensuring that submitted code is thoroughly reviewed and tested before deployment. We want to catch bugs before they reach production and protect the integrity of the service. We’ll provide updates in the notes of our regular meetings, on GitHub, and in this blog.
If you have an idea to improve PeeringDB, you can share it on our low-traffic mailing lists or create an issue directly on GitHub. If you find a data quality issue, please let us know at support@peeringdb.com.
PeeringDB is a freely available, user-maintained database of networks and the go-to location for interconnection data. It facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centres, and other interconnection facilities, and is often the first stop for making interconnection decisions.
Comments 0