ixreport

Pedjoeang Digital Networks AS50104: PeeringDB fix list

AS50104 · peeringdb.com/net/32030

PeeringDB

2 things to fix in Pedjoeang Digital Networks AS50104's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.

Make the changes on Pedjoeang Digital Networks AS50104'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 (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 JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address differs2404:c8:0:a:0:21:537:12404:c8:0:a:0:5:104:1
    • In the entry with IPv4 119.11.184.153: set IPv6 to 2404:c8:0:a:0:5:104:1 (now 2404:c8:0:a:0:21:537:1).

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 TarIX JKTghost Jakarta, Indonesia · PeeringDB 4643

    Only one outside network

    IPv489.213.160.2
    IPv62602:fac2:b0:b::501:4
    Speed40000 Mbps (40G)

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