Evoxt: PeeringDB fix list
AS149440 · peeringdb.com/net/33385
2 things to fix in Evoxt'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 Evoxt'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 Evoxt's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.16.103.69 IPv6 2001:de8:12:100::103:69 Speed 2000 Mbps (2G) RS peer No
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 Address belongs to another network in PeeringDB 103.16.103.69 is AS150436 Byteplus Pte. Ltd. 103.16.103.69 Address belongs to another network in PeeringDB 2001:de8:12:100::103:69 is AS150436 Byteplus Pte. Ltd. 2001:de8:12:100::103:69 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/149440/: 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.