level66.network: PeeringDB fix list
AS56381 · peeringdb.com/net/21292
4 things to fix in level66.network's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on level66.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 (2)
On the exchange's own member list, but not in level66.network's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 193.189.82.212 IPv6 2001:7f8:33::a105:6381:1 Speed 1000 Mbps (1G) 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.
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.
-
Problem PeeringDB has The export has Port speed differs 100G 1G - In the entry with IPv4 185.1.147.29: set Speed to 1000 (1G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 185.0.30.21: 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.
From ixreport.com/net/56381/: 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.