ixreport

MITRACOM SOLUSI TEKNOLOGI

AS149964 · mitracom

PT. MITRACOM SOLUSI TEKNOLOGI

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

Tools: Where can I peer with MITRACOM SOLUSI TEKNOLOGI? · Where should MITRACOM SOLUSI TEKNOLOGI peer next? · Compare MITRACOM SOLUSI TEKNOLOGI with another network

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

PeeringDB fix list Printable page · CSV

4 things to fix in MITRACOM SOLUSI TEKNOLOGI's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct, 1 to check. As of 2026-11-19 18:41 UTC.

Make the changes on MITRACOM SOLUSI TEKNOLOGI's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in MITRACOM SOLUSI TEKNOLOGI's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::2:49cc:1
    SpeedNot published
    RS peerYes

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::149:964:1
    • In the entry with IPv4 43.254.83.88: set IPv6 to 2401:91e0:31::149:964:1 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change 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::a3
    • In the entry with IPv4 123.108.8.163: set IPv6 to 2001:7fa:2:5::a3 (now empty).

    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 MITRACOM SOLUSI TEKNOLOGI 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.54
    IPv6–
    Speed1000 Mbps (1G)

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

Exchanges over time

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

Map

Where MITRACOM SOLUSI TEKNOLOGI'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 33G, at the 6 of 7 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::2:49cc:1 Yes Not in PeeringDB
Indonesia AIX Tapos, Depok, Indonesia 43.254.83.88 1G Yes Both IPv6 not in PeeringDB
Indonesia CXC Jakarta Jakarta, Indonesia 103.225.173.54 1G Yes PeeringDB only
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.8.163 10G Yes Both IPv6 not in PeeringDB
Indonesia ILIX Surabaya, Indonesia 157.10.16.26 2404:2f80:206::26 10G PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.170 10G Yes Both
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.147.80 1G PeeringDB

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

These exchanges have a switch in a facility where MITRACOM SOLUSI TEKNOLOGI lists itself in PeeringDB, but don't have MITRACOM SOLUSI TEKNOLOGI 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 (4)

The buildings MITRACOM SOLUSI TEKNOLOGI 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 ProDCJakarta Selatan 1 of 2