ixreport

Mandiri Citra Makmur: PeeringDB fix list

AS38211 · peeringdb.com/net/33349

PeeringDB

2 things to fix in Mandiri Citra Makmur's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Mandiri Citra Makmur'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 Mandiri Citra Makmur's PeeringDB record. Add one entry per connection with these values.

  1. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210From its IX-F export
    IPv4123.108.10.125
    IPv62001:7fa:2:5::28d
    Speed1000 Mbps (1G)
    RS peerYes

    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 Mandiri Citra Makmur has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476Not on its IX-F export
    IPv4119.11.185.104
    IPv6–
    Speed1000 Mbps (1G)

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