LU-CIX Route Servers: PeeringDB fix list

AS49624 · peeringdb.com/net/19273

PeeringDB

2 things to fix in LU-CIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

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

  1. Belgium BNIX Brussels, Belgium · PeeringDB 59From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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

Correct these entries (1)

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. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB188.93.170.255 188.93.171.0188.93.170.252 188.93.170.254 188.93.170.255 188.93.171.0 188.93.171.1 188.93.171.2
    IPv6 address missing from PeeringDB2001:7f8:4c::ffff:1 2001:7f8:4c::ffff:22001:7f8:4c::ffff:1 2001:7f8:4c::ffff:2 2001:7f8:4c::ffff:6 2001:7f8:4c::ffff:7 2001:7f8:4c::ffff:aaaa 2001:7f8:4c:0:250:56ff:feb1:c3d7
    Port speed differs2 × 10G4 × 10G
    • Add an entry: IPv4 188.93.170.252, IPv6 2001:7f8:4c::ffff:6, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 188.93.171.1, IPv6 2001:7f8:4c::ffff:aaaa, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 188.93.171.2, IPv6 2001:7f8:4c::ffff:7, speed 10000 (10G), RS peer no.
    • Add an entry: IPv4 188.93.170.254, IPv6 2001:7f8:4c:0:250:56ff:feb1:c3d7, speed 10000 (10G), RS peer no.

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