ixreport

NETFINITY: PeeringDB fix list

AS152407 · peeringdb.com/net/35553

PeeringDB

3 things to fix in NETFINITY's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on NETFINITY'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 (3)

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
    IPv6 address missing from PeeringDBnone2001:df5:7880:0:2:5357:0:1
    Port speed differs1G10G
    • In the entry with IPv4 49.213.56.178: set IPv6 to 2001:df5:7880:0:2:5357:0:1 (now empty); set Speed to 10000 (10G) (now 1000).
  2. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::2f6
    • In the entry with IPv4 123.108.10.230: set IPv6 to 2001:7fa:2:5::2f6 (now empty).

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

  3. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2404:c8:0:a:0:15:2407:1
    Port speed differs10G1G
    • In the entry with IPv4 119.11.186.174: set IPv6 to 2404:c8:0:a:0:15:2407:1 (now empty); set Speed to 1000 (1G) (now 10000).

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