ixreport

Ring Media Nusantara: PeeringDB fix list

AS141642 · peeringdb.com/net/25929

PeeringDB

2 things to fix in Ring Media Nusantara's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Ring Media Nusantara'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 IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 123.108.10.2: set Speed to 10000 (10G) (now 100000).

    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 Ring Media Nusantara 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.0
    IPv62001:de8:12:100::103:0
    Speed100000 Mbps (100G)

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