Akm Link Net: PeeringDB fix list

AS149689 · peeringdb.com/net/30936

PeeringDB

2 things to fix in Akm Link Net's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Akm Link Net'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 IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::99
    Port speed differs10G1G
    • In the entry with IPv4 123.108.8.153: set IPv6 to 2001:7fa:2:5::99 (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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Akm Link Net has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476Not on its IX-F export
    IPv4119.11.186.49
    IPv6–
    Speed10000 Mbps (10G)

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