DE-CIX Jakarta Route Servers: PeeringDB fix list

AS9748 · peeringdb.com/net/12034

PeeringDB

One thing to fix in DE-CIX Jakarta Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on DE-CIX Jakarta Route Servers'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 DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB49.213.56.249 is AS205529 DE-CIX Monitoring49.213.56.249
    Address belongs to another network in PeeringDB2001:df5:7880::2614:c:1 is AS205529 DE-CIX Monitoring2001:df5:7880::2614:c:1
    IPv4 address missing from PeeringDB49.213.56.252 49.213.57.25249.213.56.249 49.213.56.252 49.213.56.254 49.213.57.252
    IPv6 address missing from PeeringDB2001:df5:7880::2614:a:1 2001:df5:7880::2614:a:22001:df5:7880::2614:a:1 2001:df5:7880::2614:a:2 2001:df5:7880::2614:b:dead 2001:df5:7880::2614:c:1
    Port speed differs2 × 10G4 × 20G

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 49.213.56.252: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 49.213.57.252: set Speed to 20000 (20G) (now 10000).
    • Add an entry: IPv4 49.213.56.254, IPv6 2001:df5:7880::2614:b:dead, speed 20000 (20G), RS peer no.

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