Juniper Solutions: PeeringDB fix list

AS37398 · peeringdb.com/net/18447

PeeringDB

2 things to fix in Juniper Solutions's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Juniper Solutions'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. Nigeria AMS-IX Lagos Lagos, Nigeria · PeeringDB 2381
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:43f8:11f0::9216:12001:43f8:11f0::a503:7398:1
    • In the entry with IPv4 196.60.58.15: set IPv6 to 2001:43f8:11f0::a503:7398:1 (now 2001:43f8:11f0::9216:1).

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

  2. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:43f8:bb1::63none
    Port speed differs100M1G
    • In the entry with IPv4 196.216.148.63: set IPv6 to (empty) (now 2001:43f8:bb1::63); set Speed to 1000 (1G) (now 100).

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