PT. SaranaInsan MudaSelaras: PeeringDB fix list

AS23671 · peeringdb.com/net/20095

PeeringDB

2 things to fix in PT. SaranaInsan MudaSelaras's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on PT. SaranaInsan MudaSelaras'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
    IPv6 address missing from PeeringDBnone2404:c8:0:a:0:2:3671:1
    • In the entry with IPv4 119.11.184.233: set IPv6 to 2404:c8:0:a:0:2:3671:1 (now empty).

Check these entries (1)

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

  1. Singapore SGIX Singapore, Singapore · PeeringDB 429Not on its IX-F export or website members list
    IPv4103.16.103.33
    IPv62001:de8:12:100::103:33
    Speed10000 Mbps (10G)

From ixreport.com/net/23671/: 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.