ixreport

PT Citra Prima Media: PeeringDB fix list

AS151589 · peeringdb.com/net/34516

PeeringDB

2 things to fix in PT Citra Prima Media's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on PT Citra Prima Media'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 (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.

  1. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::299
    Port speed differs10G1G
    • In the entry with IPv4 123.108.10.136: set IPv6 to 2001:7fa:2:5::299 (now empty); set Speed to 1000 (1G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export119.11.186.57 119.11.187.49119.11.186.57
    Port speed differs2 × 10G1G
    • In the entry with IPv4 119.11.186.57: set Speed to 1000 (1G) (now 10000).
    • The entry with IPv4 119.11.187.49, IPv6 – isn't in the export: delete it if that connection is gone.

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