ixreport

IONET: PeeringDB fix list

AS152376 · peeringdb.com/net/35958

PeeringDB

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

Make the changes on IONET'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 (2)

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 AIX Tapos, Depok, Indonesia · PeeringDB 4449
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:91e0:31::152:376:1
    • In the entry with IPv4 43.254.83.91: set IPv6 to 2401:91e0:31::152:376:1 (now empty).

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

  2. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::2dc
    Port speed differs10G1G
    • In the entry with IPv4 123.108.10.204: set IPv6 to 2001:7fa:2:5::2dc (now empty); set Speed to 1000 (1G) (now 10000).

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

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