ixreport

AS212635 Network: PeeringDB fix list

AS212635 · peeringdb.com/net/24632

PeeringDB

3 things to fix in AS212635 Network's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on AS212635 Network'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 AS212635 Network's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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 AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 80.249.215.23: set Speed to 1000 (1G) (now 10000).

    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 EVIX Fremont, United States · PeeringDB 2274
    ProblemPeeringDB hasThe export has
    Port speed differs100M1G
    • In the entry with IPv4 206.81.104.78: set Speed to 1000 (1G) (now 100).

    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/212635/: 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.