ixreport

SAINT: PeeringDB fix list

AS328146 · peeringdb.com/net/13454

PeeringDB

5 things to fix in SAINT's PeeringDB record, from what its exchanges publish: 4 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on SAINT'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 (4)

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. South Africa DINX Durban, South Africa · PeeringDB 610
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:1f2::132
    • In the entry with IPv4 196.223.30.132: set IPv6 to 2001:43f8:1f2::132 (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. South Africa JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:1f0::132
    Port speed differs10G1G
    • In the entry with IPv4 196.60.96.132: set IPv6 to 2001:43f8:1f0::132 (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.

  3. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d2::38
    • In the entry with IPv4 196.10.141.38: set IPv6 to 2001:43f8:6d2::38 (now empty).

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

  4. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::9:41
    • In the entry with IPv4 196.60.9.41: set IPv6 to 2001:43f8:6d0::9:41 (now empty).

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If SAINT has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.225.235
    IPv6–
    Speed1000 Mbps (1G)

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