ixreport

iMobility: PeeringDB fix list

AS329443

One thing to fix in iMobility's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 22:13 UTC.

AS329443 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (1)

On the exchange's own member list, but not in iMobility's PeeringDB record. Add one entry per connection with these values.

  1. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4196.60.9.81
    IPv62001:43f8:6d0::9:81
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4196.60.9.82
    IPv62001:43f8:6d0::9:82
    Speed10000 Mbps (10G)
    RS peerYes

    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/329443/: 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.