ixreport

Media Solusi Sukses

AS142393 · Shafanet

PT Media Solusi Sukses

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
2To fix in PeeringDB
3Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

2 things to fix in Media Solusi Sukses's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Media Solusi Sukses'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 in PeeringDB, not in the export2401:91e0:31::142:393:1none
    • In the entry with IPv4 43.254.83.46: set IPv6 to (empty) (now 2401:91e0:31::142:393:1).

    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
    Port speed differs20G10G
    • In the entry with IPv4 123.108.9.191: set Speed to 10000 (10G) (now 20000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change 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 Media Solusi Sukses'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 91G across 6 exchanges.

Indonesia AIX Tapos, Depok, Indonesia 43.254.83.46 2401:91e0:31::142:393:1 1G Yes Both IPv6 not in export
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.9.191 2001:7fa:2:5::1bf 20G Yes Both Speed differs
Indonesia ILIX Surabaya, Indonesia 157.10.16.15 2404:2f80:206::15 10G Yes PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.13 2404:c8:0:a:0:14:2393:1 40G Yes Both
Indonesia ODIX Omadata Surabaya, Indonesia 103.28.80.140 2403:1a00:55:659:a:14:2393:1 10G Yes PeeringDB
Indonesia OpenIXP / NiCE Indonesia, Indonesia 43.252.146.116 10G Yes PeeringDB

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

These exchanges have a switch in a facility where Media Solusi Sukses lists itself in PeeringDB, but don't have Media Solusi Sukses 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 (3)

The buildings Media Solusi Sukses lists in PeeringDB, and how many of the exchanges in each it's on.

Indonesia Datacenter APJII-CyberJakarta Selatan 3 of 17
Indonesia NTT Jakarta 2 Data Center (JKT2)Jakarta 4 of 12
Indonesia ProDCJakarta Selatan 1 of 2