ixreport

DJASANET: PeeringDB fix list

AS137351 · peeringdb.com/net/19351

PeeringDB

4 things to fix in DJASANET's PeeringDB record, from what its exchanges publish: 2 to correct, 2 to check. As of 2026-10-08 22:13 UTC.

Make the changes on DJASANET'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 (2)

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 differs10G1G
    • In the entry with IPv4 123.108.9.61: set Speed to 1000 (1G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 119.11.186.13: set Speed to 1000 (1G) (now 10000).

Check these entries (2)

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

  1. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472Not on its IX-F export or website members list
    IPv4103.162.254.126
    IPv62001:df6:480:0:2:1887:0:1
    Speed10000 Mbps (10G)
  2. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411Not on its IX-F export or website members list
    IPv449.213.56.3
    IPv62001:df5:7880:0:2:1887:0:1
    Speed10000 Mbps (10G)

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