ixreport

API VERSA OU

AS214976 · API VERSA OU

AVS ISP

WebsitePeeringDB Follow changes
1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with API VERSA OU? · Where should API VERSA OU peer next? · Compare API VERSA OU with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in API VERSA OU's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-12 18:41 UTC.

Make the changes on API VERSA OU's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in API VERSA OU's PeeringDB record. Add one entry per connection with these values.

  1. Germany NeverIX Velbert Velbert, Germany · PeeringDB 5124From its IX-F export
    IPv4–
    IPv62602:fa86:ffe::c
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

01Nov 9, 2026Nov 12, 20261

Collecting since Nov 9, 2026: one point a day, so this fills in as the days go by.

Show as a table
DateExchanges
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261

Map

Where API VERSA OU's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 10G across 1 exchange.
Germany NeverIX Velbert Velbert, Germany 2602:fa86:ffe::c 10G Yes Not in PeeringDB

API VERSA OU lists no facilities in PeeringDB.