EUROTELE-PLUS: PeeringDB fix list
AS6768 · peeringdb.com/net/5532
3 things to fix in EUROTELE-PLUS's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on EUROTELE-PLUS'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 EUROTELE-PLUS's PeeringDB record. Add one entry per connection with these values.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members listIPv4 185.1.32.130 IPv6 2001:7f8:8f::a500:6768:1 Speed Not published RS peer Not published
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.236.203 178.18.227.22 178.18.236.203 IPv6 address missing from PeeringDB 2a03:5f80:4:2::236:203 2a03:5f80:4::227:22 2a03:5f80:4:2::236:203 Port speed differs 20G 3 × 100G + 20G + 3 × 10G - In the entry with IPv4 178.18.236.203: set Speed to 10000 (10G) (now 20000).
- Add an entry: IPv4 178.18.227.22, IPv6 2a03:5f80:4::227:22, speed 10000 (10G), RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If EUROTELE-PLUS has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 212.91.0.142 IPv6 – Speed 20000 Mbps (20G)
From ixreport.com/net/6768/: 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.