ixreport

JERNIH MULTI KOMUNIKASI

AS139409 · JERNIHNET

PT JERNIH MULTI KOMUNIKASI

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

Tools: Where can I peer with JERNIH MULTI KOMUNIKASI? · Where should JERNIH MULTI KOMUNIKASI peer next? · Compare JERNIH MULTI KOMUNIKASI with another network

This network elsewhere: the registry history of AS139361-AS139460, the block AS139409 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in JERNIH MULTI KOMUNIKASI's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on JERNIH MULTI KOMUNIKASI'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 (3)

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. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df6:480:0:2:2091:0:1
    • In the entry with IPv4 103.162.254.168: set IPv6 to 2001:df6:480:0:2:2091:0:1 (now empty).
  2. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:df5:7880:0:2:2091:0:1
    • In the entry with IPv4 49.213.56.201: set IPv6 to 2001:df5:7880:0:2:2091:0:1 (now empty).
  3. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::261
    • In the entry with IPv4 123.108.10.81: set IPv6 to 2001:7fa:2:5::261 (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.

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 JERNIH MULTI KOMUNIKASI'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 51G across 6 exchanges.

Indonesia BIX Jakarta Jakarta, Indonesia 218.100.41.13 10G Yes PeeringDB
Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.168 10G 1 routes Both IPv6 not in PeeringDB
Indonesia DE-CIX Jakarta Jakarta, Indonesia 49.213.56.201 10G 1 routes Both IPv6 not in PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.10.81 1G Yes Both IPv6 not in PeeringDB
Indonesia OMNIIX INDONESIA Batam, Jakarta, Indonesia 43.255.59.63 10G Yes Both
Indonesia OpenIXP / NiCE Indonesia, Indonesia 218.100.36.247 10G Yes PeeringDB

JERNIH MULTI KOMUNIKASI lists no facilities in PeeringDB.