PeeringDB has published its latest half-yearly development report, covering platform changes from April through September 2026. The update highlights feature additions, operational refinements and data quality work completed during the period.

Feature updates

Advanced Search enhancements

The platform extended its 'Copy API Query' capability to the Advanced Search interface, fulfilling a commitment made in the previous update. Users designing searches through the web interface can now generate equivalent API queries in multiple formats, including curl and several popular scripting languages. The addition bridges manual exploration and automated workflows.

An optional in-page map view for Advanced Search has also been introduced. Accessible via user profile settings, the map displays facility locations within a city, offering a visual complement to table-based results and helping users grasp local interconnection patterns more quickly. The full PeeringDB facility dataset remains downloadable as a KMZ file for use in GIS platforms and mapping applications for users requiring broader geographic analysis.

Interactive facility maps

Operational improvements

Streamlined software releases

In August, PeeringDB tested a revised deployment workflow that eliminated the public beta phase, moving directly from internal testing to production. The change responded to community input indicating that the existing beta process no longer delivered meaningful value. Since the August release proceeded without issues or concerns, the organization has made this the standard approach going forward. For substantial changes—particularly those affecting user interface or API behavior—public beta testing will continue to be used where warranted.

New operations dashboard

PeeringDB completed a redevelopment of its internal operations dashboard. Rollout to PeeringDB volunteers is scheduled for September, with public availability planned for later in the year.

Data quality improvements

More accurate AS-SET naming

Following input from community member James Bensley, PeeringDB modified how AS-SET names appear across the platform to enhance clarity and eliminate confusion. AS-SET names now include their originating IRR when known; for instance, AS4608:AS-APNIC displays as APNIC::AS4608:AS-APNIC. When an appropriate IRR cannot be determined automatically, the team contacts network operators directly to verify correct information. A new editor has been introduced to help users enter AS-SET data consistently. Upcoming refinements include warnings when an AS-SET name duplicates one already in use elsewhere in PeeringDB.

Looking ahead

PeeringDB is expanding the metadata values available in the platform. Starting next month, users will be able to record the date of joining or leaving an exchange, MTU settings, and additional information.

A discussion document for a new PeeringDB API has been released. Two primary objectives drive the redesign:

  • Separating read and write components of the architecture, enabling PeeringDB instances to be deployed in multiple locations
  • Enabling more efficient queries, such as retrieving a network with its exchange presences, an exchange with its members, or a facility with its occupants

API users are encouraged to review the draft and subscribe to the API v3 discussion list to provide feedback before implementation begins.

The team is also examining how to alert users when a network's published maximum prefix count falls below the observed number of prefixes.

While most PeeringDB users are human, the platform has observed significant automated searches from AI systems. To help these users query PeeringDB efficiently, an MCP server will be set up and an Agent Skills directory will be published in peeringdb/peeringdb. Alongside AI-powered workflow support, PeeringDB is working to improve its own comparison tools. The team has identified several enhancements and is seeking user input on capabilities such as:

  • Showing networks common to two specified IXes
  • Showing networks common to two specified facilities
  • Showing the nearest IX where another specified ASN is present, given an ASN and a location

Users with ideas for PeeringDB improvements can post to the low-traffic mailing lists or open an issue on GitHub. Data quality issues should be reported to support@peeringdb.com.