Usaha Mediantara Intranet: PeeringDB fix list

AS58817 · peeringdb.com/net/33017

PeeringDB

2 things to fix in Usaha Mediantara Intranet's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Usaha Mediantara Intranet'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 Usaha Mediantara Intranet'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.55
    IPv62001:7fa:2:5::247
    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.

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
    Address belongs to another network in PeeringDB2001:7fa:2:5::247 is AS149934 Pangkalan Lintas Data2001:7fa:2:5::247

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    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/58817/: 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.