ixreport

PT Emlima Koneksi Nusantara

AS153822 · EMLIMA

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

Tools: Where can I peer with PT Emlima Koneksi Nusantara? · Where should PT Emlima Koneksi Nusantara peer next? · Compare PT Emlima Koneksi Nusantara with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in PT Emlima Koneksi Nusantara's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on PT Emlima Koneksi Nusantara'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 AIX Tapos, Depok, Indonesia · PeeringDB 4449
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:91e0:31::153:822:1
    • In the entry with IPv4 43.254.83.25: set IPv6 to 2401:91e0:31::153:822:1 (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.

  2. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::3a7
    • In the entry with IPv4 123.108.11.151: set IPv6 to 2001:7fa:2:5::3a7 (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

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

Map

Where PT Emlima Koneksi Nusantara'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 21G across 3 exchanges.

Indonesia AIX Tapos, Depok, Indonesia 43.254.83.25 1G Yes Both IPv6 not in PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.151 10G Yes Both IPv6 not in PeeringDB
Indonesia ILIX Surabaya, Indonesia 157.10.16.64 10G Yes PeeringDB

Exchanges in its buildings that it isn't on (1)

These exchanges have a switch in a facility where PT Emlima Koneksi Nusantara lists itself in PeeringDB, but don't have PT Emlima Koneksi Nusantara as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Indonesia JDXJakarta, Indonesia 13 ProDC
Facilities (2)

The buildings PT Emlima Koneksi Nusantara lists in PeeringDB, and how many of the exchanges in each it's on.

Indonesia Area31 Data CenterDepok 2 of 2
Indonesia ProDCJakarta Selatan 1 of 2