ixreport

PT. Pika Media Komunika: PeeringDB fix list

AS38506 · peeringdb.com/net/7833

PeeringDB

2 things to fix in PT. Pika Media Komunika's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on PT. Pika Media Komunika'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
    Port speed differs10G1G
    • In the entry with IPv4 123.108.8.35: 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 missing from PeeringDB119.11.186.218119.11.186.32 119.11.186.218
    IPv6 address in PeeringDB, not in the export2404:c8:0:a:0:3:8506:1none
    Port speed differs10G1G
    • In the entry with IPv4 119.11.186.218: set IPv6 to (empty) (now 2404:c8:0:a:0:3:8506:1); set Speed to 1000 (1G) (now 10000).
    • Add an entry: IPv4 119.11.186.32, IPv6 –, speed 1000 (1G), RS peer yes.

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