NT(CAT) IIG: PeeringDB fix list
AS4651 · peeringdb.com/net/2202
3 things to fix in NT(CAT) IIG's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on NT(CAT) IIG'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 NT(CAT) IIG's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.162.254.48 IPv6 2001:df6:480::122b:0:2 Speed 10000 Mbps (10G) RS peer Yes
Correct these entries (2)
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.162.254.48 is AS152830 Elemen Jaringan Nusantara 103.162.254.48 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.
-
Problem PeeringDB has The export has Port speed differs 30G 100G - In the entry with IPv4 80.81.193.238: set Speed to 100000 (100G) (now 30000).
From ixreport.com/net/4651/: 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.