PeeringDB, the user-maintained interconnection database, has released a six-month product update covering April to September 2026. The changes focus on automation, geographic visualization, and data accuracy for network operators and Internet Exchange Points (IXPs).
What changed
The update introduces several new features and operational adjustments. Users can now generate API queries directly from the Advanced Search interface, supporting multiple formats such as curl and common scripting languages. This allows operators to transition seamlessly between manual searches and automated workflows without rewriting queries.
An optional interactive map view has been added to Advanced Search, displaying facility locations within a city. The feature is enabled through user profile settings and provides a visual complement to the existing table-based results. For broader geographic analysis, PeeringDB continues to offer its facility dataset as a downloadable KMZ file for use in GIS platforms.
Data quality improvements include updated AS-SET naming conventions. AS-SET names now include their originating Internet Routing Registry (IRR) where known, reducing ambiguity. For example, AS4608:AS-APNIC is now displayed as APNIC::AS4608:AS-APNIC. A new editor has been introduced to help users enter AS-SET information consistently, with additional refinements planned, such as warnings for duplicate AS-SET names.
Operationally, PeeringDB has streamlined its software release process. Following community feedback, the public beta stage was removed for the August release, moving directly from internal testing to production deployment. The change was adopted as standard after no issues were reported. For larger changes, particularly those affecting the user interface or API behavior, public beta testing will still be used where appropriate.
A redeveloped internal operations dashboard has been completed, with access rolled out to PeeringDB volunteers in September. The dashboard is expected to be made publicly available later in 2026.
What’s next
PeeringDB is planning further enhancements, including new metadata fields for signaling joining or leaving dates at exchanges and MTU values. A discussion document for a new PeeringDB API has been published, aiming to separate read and write architecture to enable distributed instances and more efficient queries. Network operators and API users are encouraged to review the draft and provide feedback before implementation.
The platform is also exploring ways to notify users if a network’s published maximum prefix count is smaller than the observed number of prefixes. Additionally, PeeringDB is setting up an MCP server and publishing an Agent Skills directory to support AI-powered workflows, while also considering new comparison tools for IXPs and facilities.
Background: PeeringDB is a freely available, user-maintained database that facilitates global interconnection of networks at IXPs, data centers, and other facilities. It serves as a primary resource for operators making interconnection decisions, with data contributed and updated by the community.
For professionals: The new API query generation and interactive maps reduce manual effort for network planning and automation. Operators should review the updated AS-SET naming conventions to ensure consistency in their PeeringDB entries and prepare for upcoming metadata expansions.
Companies mentioned
Automated pipeline · Cloud & Infrastructure
Synthesized from 1 industry feed on 7 Oct 2026. Passed independent editor verification (score 95/100) before publication. Style guide v1.4.
Sources
Decision trail
- Checking for duplicates — Deduped batch of 1 candidates
- Checking for duplicates — New story No recent or in-pipeline article covers PeeringDB product updates for April-September 2026.
- Checking for duplicates — New story pre_write:; No recent or in-pipeline article covers PeeringDB product updates.
- Writing the article — Draft created article_id=658 slug=peeringdb-rolls-out-api-mapping-and-as-set-upgrades
-
Editor review — Approved
- Score: 95/100
- Style compliance: The standfirst mentions a 'six-month update' but the body does not explicitly state the update covers April to September 2026 in the opening paragraph. While the date is correct and traceable to the source, it should be introduced earlier for clarity.
- No copied phrasing: The phrase 'freely available, user-maintained database' in the Background block is very close to the source wording. While the fact is correct, the phrasing should be restructured to avoid echoing the source.
- Style compliance: The 'What’s next' section could be more clearly separated with a `##` heading (e.g., `## What to watch`) to maintain consistency with the style guide’s section structure rules.
- Generating reader Q&A — Generated 4 items
- Assigning hero image — Reused library image reused image #15
- Linking related stories — Linked 3 relations from 330 candidates
- Publishing — Published peeringdb-rolls-out-api-mapping-and-as-set-upgrades
- Mastodon — Posted https://mstdn.social/@hostingpaper/117397833745765270
Discussion · coming soon
Be the first to join the thread when community discussion launches.