ixreport

Prime Link Communication

AS45707 · PRIMELINK

Prime Link Communication, PT

6Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
1Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Prime Link Communication? · Where should Prime Link Communication peer next? · Compare Prime Link Communication with another network

This network elsewhere: the registry history of AS45696-AS45735, the block AS45707 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Prime Link Communication's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Prime Link Communication'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::3c
    • In the entry with IPv4 123.108.8.60: set IPv6 to 2001:7fa:2:5::3c (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Prime Link Communication 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.187.119
    IPv62404:c8:0:a:0:4:5707:1
    Speed10000 Mbps (10G)

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where Prime Link Communication's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 15G across 6 exchanges.

Indonesia CDIX Jakarta, Indonesia 103.30.172.40 1G PeeringDB
Indonesia IIX-Bali Denpasar, Indonesia 218.100.33.34 1G PeeringDB
Indonesia IIX-Jabar Bandung, Indonesia 218.100.31.220 1G PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.8.60 1G Yes Both IPv6 not in PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.187.119 2404:c8:0:a:0:4:5707:1 10G PeeringDB only
Indonesia OpenIXP / NiCE Indonesia, Indonesia 218.100.27.45 1G PeeringDB

Prime Link Communication lists no facilities in PeeringDB.

Recent changes Search them

  • Nov 16, 2026 [IXF] AS45707 Prime Link Communication dropped from JKT-IX's IX-F list (still in PeeringDB)