ixreport

kejoraNET: PeeringDB fix list

AS139949 · peeringdb.com/net/22062

PeeringDB

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

Make the changes on kejoraNET'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 kejoraNET's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.188
    IPv62001:7f8:9e:0:2:22ad:0:1
    Speed10000 Mbps (10G)
    RS peerYes

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 in PeeringDB, not in the export2404:c8:0:a:0:13:9949:1none
    • In the entry with IPv4 119.11.184.155: set IPv6 to (empty) (now 2404:c8:0:a:0:13:9949:1).

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