nusa-IX Route Server: PeeringDB fix list

AS212001 · peeringdb.com/net/38699

PeeringDB

4 things to fix in nusa-IX Route Server's PeeringDB record, from what its exchanges publish: 3 to add, 1 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

Make the changes on nusa-IX Route Server'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 (3)

On the exchange's own member list, but not in nusa-IX Route Server's PeeringDB record. Add one entry per connection with these values.

  1. Indonesia AIX Tapos, Depok, Indonesia · PeeringDB 4449From its IX-F export
    IPv443.254.82.247
    IPv62401:91e0:31::212:1:1
    Speed1000 Mbps (1G)
    RS peerNo

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

  2. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411From its IX-F export and website members list
    IPv449.213.56.91
    IPv62001:df5:7880:0:3:3c21:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476From its IX-F export
    IPv4119.11.186.230
    IPv62404:c8:0:a:0:21:2001:1
    Speed1000 Mbps (1G)
    RS peerYes

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Indonesia nusa-IX Surabayaghost Surabaya, Indonesia · PeeringDB 5077

    Only one outside network

    IPv431.56.97.1
    IPv62a06:9f44:d000:79::1
    Speed10000 Mbps (10G)

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