Afilias: PeeringDB fix list

AS12041 · peeringdb.com/net/1855

PeeringDB

9 things to fix in Afilias's PeeringDB record, from what its exchanges publish: 1 to add, 8 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Afilias's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

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

  1. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488From its IX-F export
    IPv4196.216.148.58
    IPv6–
    Speed1000 Mbps (1G)
    RS peerYes

Correct these entries (8)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 80.81.194.2: set Speed to 100000 (100G) (now 1000).
  2. Australia IX Australia Adelaide (SA-IX) Adelaide, Australia · PeeringDB 691
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 218.100.54.34: set Speed to 10000 (10G) (now 1000).

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

  3. Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 218.100.78.107: set Speed to 10000 (10G) (now 1000).

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

  4. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 218.100.52.82: set Speed to 10000 (10G) (now 1000).

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

  5. South Africa JINX Johannesburg, South Africa · PeeringDB 129
    ProblemPeeringDB hasThe export has
    IPv4 address differs196.223.14.120196.60.96.120
    • In the entry with IPv4 196.223.14.120: set IPv4 to 196.60.96.120 (now 196.223.14.120).

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

  6. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 217.29.66.124: set Speed to 10000 (10G) (now 1000).
  7. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs1G1T
    • In the entry with IPv4 194.68.128.189: set Speed to 1000000 (1T) (now 1000).
  8. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs1G1T
    • In the entry with IPv4 194.68.123.189: set Speed to 1000000 (1T) (now 1000).

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