CS LoxInfo (IX): PeeringDB fix list
AS45265 · peeringdb.com/net/13402
2 things to fix in CS LoxInfo (IX)'s PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on CS LoxInfo (IX)'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 CS LoxInfo (IX)'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.
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 203.159.68.108 203.159.68.108 203.159.68.188 IPv6 address missing from PeeringDB 2001:df5:b881::108 2001:df5:b881::108 2001:df5:b881::188 Port speed differs 10G 100G + 10G - Add an entry: IPv4 203.159.68.188, IPv6 2001:df5:b881::188, speed 100000 (100G), 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.
From ixreport.com/net/45265/: 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.