ixreport

MLINK.ID

AS149365 · MLINK.ID

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

Tools: Where can I peer with MLINK.ID? · Where should MLINK.ID peer next? · Compare MLINK.ID with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in MLINK.ID'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 MLINK.ID'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 JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs100G1G
    • In the entry with IPv4 119.11.185.143: set Speed to 1000 (1G) (now 100000).

Check these entries (1)

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

  1. Indonesia CXC Jakarta Jakarta, Indonesia · PeeringDB 2737Not on its website members list
    IPv4103.225.173.69
    IPv62400:9c80:0:173::149:365
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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 MLINK.ID'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 150G across 6 exchanges.

Indonesia AIX Tapos, Depok, Indonesia 43.254.82.202 10G Yes Both
Indonesia CENTRO-IX Pekanbaru - Jakarta, Indonesia 103.138.70.124 2404:ce40:3::1a 10G Yes PeeringDB
Indonesia CXC Jakarta Jakarta, Indonesia 103.225.173.69 2400:9c80:0:173::149:365 10G Yes PeeringDB only
Indonesia EdgeNXT Jakarta, Indonesia 103.61.232.154 2001:df1:d440:1::9a 10G Yes PeeringDB
Indonesia ILIX Surabaya, Indonesia 157.10.16.124 2404:2f80:206::24 10G Yes PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.143 2404:c8:0:a:0:14:9365:1 100G Yes Both Speed differs

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

These exchanges have a switch in a facility where MLINK.ID lists itself in PeeringDB, but don't have MLINK.ID 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.

Facilities (7)

The buildings MLINK.ID lists in PeeringDB, and how many of the exchanges in each it's on.

Indonesia Datacenter APJII-CyberJakarta Selatan 4 of 17
Indonesia IDC 3DJakarta Selatan 3 of 12
Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 5 of 12
Indonesia Equinix JK1 - JakartaJakarta 1 of 3
Indonesia neuCentrIX - BandungKota Bandung 0 of 2
Indonesia DCI Indonesia (H2-01)Karawang 0 of 1
Indonesia DCI Indonesia (H2-02)Karawang 0 of 1