ixreport

Dinar Wahana Gemilang: PeeringDB fix list

AS141130 · peeringdb.com/net/30938

PeeringDB

2 things to fix in Dinar Wahana Gemilang'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 Dinar Wahana Gemilang'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 Dinar Wahana Gemilang'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.12.27
    IPv62001:7fa:2:5::429
    Speed10000 Mbps (10G)
    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 Dinar Wahana Gemilang 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.167
    IPv62404:c8:0:a:0:14:1130:1
    Speed1000 Mbps (1G)

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