ixreport

ALUE NETWORK: PeeringDB fix list

AS25085 · peeringdb.com/net/42555

2 things to fix in ALUE NETWORK's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on ALUE NETWORK'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 3AM Network IX Amsterdam, Netherlands · PeeringDB 5023
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone91.213.211.90
    • In the entry with IPv6 2001:7f8:17d::90: set IPv4 to 91.213.211.90 (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. Netherlands Kawaii IX AMS Amsterdam, Netherlands · PeeringDB 4973
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone195.60.92.75
    • In the entry with IPv6 2602:f93b:1a35:1311::75: set IPv4 to 195.60.92.75 (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/25085/: 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.