Media Solusi Sukses: PeeringDB fix list

AS142393 · peeringdb.com/net/30028

PeeringDB

2 things to fix in Media Solusi Sukses's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 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.

From ixreport.com/net/142393/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.