CTCSCI TECH LIMITED: PeeringDB fix list
AS9886 · peeringdb.com/net/20891
3 things to fix in CTCSCI TECH LIMITED's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on CTCSCI TECH LIMITED'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 CTCSCI TECH LIMITED's PeeringDB record. Add one entry per connection with these values.
-
Hong Kong Global Internet Exchange Hong Kong, Hong Kong · PeeringDB 4625From its IX-F export and website members listIPv4 160.22.49.199 IPv6 2404:c140:101e::9886 Speed 100000 Mbps (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.
-
UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list2 connections, so 2 entries:
IPv4 192.34.27.52 IPv6 – Speed Not published RS peer Not published IPv4 – IPv6 2602:ffb1:200:0:192:34:27:52 Speed Not published RS peer Not published 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 (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 Port speed differs 200G 100G - In the entry with IPv4 103.16.103.76: set Speed to 100000 (100G) (now 200000).
From ixreport.com/net/9886/: 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.