Arthaloka Networks: PeeringDB fix list

AS150196 · peeringdb.com/net/34251

PeeringDB

2 things to fix in Arthaloka Networks's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 21:35 UTC.

Make the changes on Arthaloka Networks'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::439
    • In the entry with IPv4 123.108.12.43: set IPv6 to 2001:7fa:2:5::439 (now empty).

    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
    IPv6 address differs2404:c8:0:a:0:19:2834:12404:c8:0:a:0:15:196:1
    Port speed differs10G2G
    • In the entry with IPv4 119.11.184.70: set IPv6 to 2404:c8:0:a:0:15:196:1 (now 2404:c8:0:a:0:19:2834:1); set Speed to 2000 (2G) (now 10000).

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