A10H: PeeringDB fix list

AS21868 · peeringdb.com/net/35636

PeeringDB

5 things to fix in A10H's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on A10H'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 (2)

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

  1. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
    IPv4193.239.118.125
    IPv62001:7f8:13::a502:1868:1
    SpeedNot published
    RS peerYes

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

  2. United States NVIX Ashburn, United States · PeeringDB 4462From its website members list
    IPv4149.112.60.48
    IPv62001:504:125:e2::48
    SpeedNot published
    RS peerNot published

Correct these entries (3)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.147.253
    • In the entry with IPv6 2001:7f8:ca:1:0:2:1868:1: set IPv4 to 185.1.147.253 (now empty).

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

  2. Germany FogIXP Frankfurt Frankfurt, Germany · PeeringDB 4200
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.30.41
    • In the entry with IPv6 2001:7f8:11c:1:0:2:1868:1: set IPv4 to 185.0.30.41 (now empty).

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

  3. Canada UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone192.34.27.143
    • Add an entry: IPv4 192.34.27.143, IPv6 –.

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

From ixreport.com/net/21868/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.