PCCW Global: PeeringDB fix list
AS3491 · peeringdb.com/net/1451
6 things to fix in PCCW Global's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on PCCW Global'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 (3)
On the exchange's own member list, but not in PCCW Global'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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 185.1.8.36 IPv6 2001:7f8:73::da3:0:1 Speed 1000 Mbps (1G) RS peer Yes
Correct these entries (3)
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 20G 100G + 2 × 10G - In the entry with IPv4 80.249.209.37: set Speed to 100000 (100G) (now 20000).
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 IPv6 address in PeeringDB, not in the export 2001:43f8:bb1::94 none - In the entry with IPv4 196.216.148.94: set IPv6 to (empty) (now 2001:43f8:bb1::94).
-
Problem PeeringDB has The export has Port speed differs 10G 20G + 10G - In the entry with IPv4 196.60.8.152: set Speed to 20000 (20G) (now 10000).
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/3491/: 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.