KTPNET: PeeringDB fix list

AS24528 · peeringdb.com/net/21880

PeeringDB

One thing to fix in KTPNET's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

Make the changes on KTPNET'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 KTPNET's PeeringDB record. Add one entry per connection with these values.

  1. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210From its IX-F export
    IPv4123.108.9.20
    IPv62001:7fa:2:5::114
    Speed1000 Mbps (1G)
    RS peerYes

    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/24528/: 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.