Trivox: PeeringDB fix list

AS216078 · peeringdb.com/net/34692

PeeringDB

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

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

Correct these entries (2)

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. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 185.1.240.159: set Speed to 10000 (10G) (now 100000).

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

  2. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:134::41
    • In the entry with IPv4 185.1.184.124: set IPv6 to 2001:7f8:134::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.

From ixreport.com/net/216078/: 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.