ixreport

PT Solusi Media Telekomunikasi

AS141889 · SIMTEL

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

Tools: Where can I peer with PT Solusi Media Telekomunikasi? · Where should PT Solusi Media Telekomunikasi peer next? · Compare PT Solusi Media Telekomunikasi with another network

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

PeeringDB fix list Printable page · CSV

4 things to fix in PT Solusi Media Telekomunikasi's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on PT Solusi Media Telekomunikasi'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 PT Solusi Media Telekomunikasi's PeeringDB record. Add one entry per connection with these values.

  1. Indonesia CXC Jakarta Jakarta, Indonesia · PeeringDB 2737From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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. Indonesia AIX Tapos, Depok, Indonesia · PeeringDB 4449
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:91e0:31::14:889:1
    • In the entry with IPv4 43.254.82.239: set IPv6 to 2401:91e0:31::14:889: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::31f
    • In the entry with IPv4 123.108.11.15: set IPv6 to 2001:7fa:2:5::31f (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.

  3. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2404:c8:0:a:0:14:1889:1
    • In the entry with IPv4 119.11.185.246: set IPv6 to 2404:c8:0:a:0:14:1889:1 (now empty).

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, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where PT Solusi Media Telekomunikasi'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 41G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Indonesia AIX Tapos, Depok, Indonesia 43.254.82.239 10G Yes Both IPv6 not in PeeringDB
Indonesia BIX Jakarta Jakarta, Indonesia 218.100.41.182 10G Yes PeeringDB
Indonesia CXC Jakarta Jakarta, Indonesia Not in PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.11.15 1G Yes Both IPv6 not in PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.246 10G Yes Both IPv6 not in PeeringDB
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.146.6 10G Yes PeeringDB

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

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

Bulgaria NetIXSofia, Bulgaria 204 Datacenter APJII-Cyber
Indonesia DE-CIX JakartaJakarta, Indonesia 177 Datacenter APJII-Cyber; IDC 3D
Singapore DE-CIX ASEANSingapore, Singapore 140 Datacenter APJII-Cyber
Indonesia ILIXSurabaya, Indonesia 122 Datacenter APJII-Cyber
Indonesia OMNIIX INDONESIABatam, Jakarta, Indonesia 111 IDC 3D
Indonesia Transhybrid IX NetworkJakarta, Indonesia 63 Datacenter APJII-Cyber; IDC 3D
Indonesia CENTRO-IXPekanbaru - Jakarta, Indonesia 39 Datacenter APJII-Cyber
Indonesia CNI-IXJakarta, Indonesia 18 Datacenter APJII-Cyber; IDC 3D
Indonesia Metta-IXJakarta, Indonesia 16 Datacenter APJII-Cyber
Indonesia GPMIXLampung Timur, Indonesia 13 Datacenter APJII-Cyber
Indonesia JDXJakarta, Indonesia 13 Datacenter APJII-Cyber; IDC 3D
Indonesia Swin ExchangeDepok, Indonesia 13 IDC 3D
Indonesia BatamIX JakartaJakarta, Indonesia 7 Datacenter APJII-Cyber; IDC 3D
Indonesia IFORTE XchangeJakarta, Indonesia 7 IDC 3D
Indonesia Super Internet eXchange (SIX)Bogor, Indonesia 4 Datacenter APJII-Cyber
Indonesia ABS-IXJAKARTA, Indonesia 3 Datacenter APJII-Cyber
Facilities (2)

The buildings PT Solusi Media Telekomunikasi 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 4 of 12