ixreport

JKT-IX Route Servers: PeeringDB fix list

AS137295 · peeringdb.com/net/17146

PeeringDB

One thing to fix in JKT-IX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on JKT-IX Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

  1. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB2404:c8:0:a:0:13:7295:3 is AS140016 TRIK MEDIA DATA2404:c8:0:a:0:13:7295:3
    IPv6 address in PeeringDB, not in the export2404:c8:0:a:0:13:7295:1 2404:c8:0:a:0:13:7295:22404:c8:0:a:0:13:7295:2 2404:c8:0:a:0:13:7295:3
    Port speed differs3 × 1G10G + 2 × 1G

    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.

    • In the entry with IPv4 119.11.184.101: set IPv6 to (empty) (now 2404:c8:0:a:0:13:7295:1).
    • In the entry with IPv4 119.11.184.102: set Speed to 10000 (10G) (now 1000).
    • In the entry with IPv4 119.11.185.222: set Speed to 10000 (10G) (now 1000).

From ixreport.com/net/137295/: 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.