ixreport

Netskope: PeeringDB fix list

AS55256 · peeringdb.com/net/10670

PeeringDB

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

Make the changes on Netskope'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 (3)

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

  1. New Zealand AKL-IX (Auckland NZ) Auckland, New Zealand · PeeringDB 977From its IX-F export
    IPv443.243.21.30
    IPv62001:7fa:11:6:0:d7d8:0:1
    Speed100000 Mbps (100G)
    RS peerYes

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

  2. India Extreme IX Pune Pune, India · PeeringDB 4805From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587From its IX-F export
    IPv4185.1.8.129
    IPv62001:7f8:73::d7d8:0:1
    Speed200000 Mbps (200G)
    RS peerYes

Correct these entries (7)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB80.249.208.143 80.249.211.101 80.249.213.1180.249.208.143 80.249.211.97 80.249.211.101 80.249.212.27 80.249.213.11
    IPv6 address missing from PeeringDB2001:7f8:1::a505:5256:1 2001:7f8:1::a505:5256:3 2001:7f8:1::a505:5256:42001:7f8:1::a505:5256:1 2001:7f8:1::a505:5256:2 2001:7f8:1::a505:5256:3 2001:7f8:1::a505:5256:4
    Port speed differs3 × 100G3 × 100G + 20G + 10G
    • Add an entry: IPv4 80.249.211.97, IPv6 –, speed 10000 (10G), RS peer yes.
    • Add an entry: IPv4 80.249.212.27, IPv6 2001:7f8:1::a505:5256:2, speed 20000 (20G), RS peer yes.

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

  2. Switzerland CIXP Geneva, Switzerland · PeeringDB 33
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 192.65.185.199: set Speed to 10000 (10G) (now 100000).
  3. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:43f8:bb1::121none
    • In the entry with IPv4 196.216.148.121: set IPv6 to (empty) (now 2001:43f8:bb1::121).
  4. United States MASS-IX Boston, United States · PeeringDB 1086
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 206.53.143.76: set Speed to 10000 (10G) (now 100000).
  5. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.26.71.119 103.26.71.130103.26.71.100 103.26.71.119 103.26.71.130
    IPv6 address missing from PeeringDB2001:dea:0:30::77 2001:dea:0:30::822001:dea:0:30::64 2001:dea:0:30::77 2001:dea:0:30::82
    • Add an entry: IPv4 103.26.71.100, IPv6 2001:dea:0:30::64, RS peer no.

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

  6. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.116.95 193.239.117.93 193.239.117.201 193.239.118.97 193.239.118.142193.239.116.95 193.239.117.93 193.239.117.201 193.239.118.97 193.239.118.142 193.239.119.61
    IPv6 address missing from PeeringDB2001:7f8:13::a505:5256:1 2001:7f8:13::a505:5256:2 2001:7f8:13::a505:5256:3 2001:7f8:13::a505:5256:4 2001:7f8:13::a505:5256:52001:7f8:13::a505:5256:1 2001:7f8:13::a505:5256:2 2001:7f8:13::a505:5256:3 2001:7f8:13::a505:5256:4 2001:7f8:13::a505:5256:5 2001:7f8:13::a505:5256:6
    • Add an entry: IPv4 193.239.119.61, IPv6 2001:7f8:13::a505:5256:6, RS peer yes.

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

  7. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.21.24: set Speed to 12500 (12.5G) (now 100000).

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