Kaopu Cloud HK: PeeringDB fix list
AS138915 · peeringdb.com/net/21265
3 things to fix in Kaopu Cloud HK's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Kaopu Cloud HK'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 Kaopu Cloud HK's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export 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 193.169.199.68 193.169.199.68 193.169.199.69 IPv6 address missing from PeeringDB 2001:7f8:58::1ea3:2:1 2001:7f8:58::1ea3:2:1 2001:7f8:58::1ea3:2:2 - Add an entry: IPv4 193.169.199.69, IPv6 2001:7f8:58::1ea3:2:2.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Kaopu Cloud HK has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 103.101.136.70 IPv6 2401:ee00:58:500::70 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/138915/: 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.