ixreport

Netnod: PeeringDB fix list

AS8674 · peeringdb.com/net/2971

PeeringDB

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

Make the changes on Netnod'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 Netnod's PeeringDB record. Add one entry per connection with these values.

  1. Czechia NIX.CZ Prague, Czechia · PeeringDB 71From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (11)

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. Switzerland CIXP Geneva, Switzerland · PeeringDB 33
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export192.65.185.235 192.65.185.236192.65.185.235
    IPv6 address in PeeringDB, not in the export2001:7f8:1c:24a::21e2:1 2001:7f8:1c:24a::21e2:22001:7f8:1c:24a::21e2:1
    Port speed differs2 × 1G1G
    • The entry with IPv4 192.65.185.236, IPv6 2001:7f8:1c:24a::21e2:2 isn't in the export: delete it if that connection is gone.
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB80.81.192.16080.81.192.160 80.81.193.160
    IPv6 address missing from PeeringDB2001:7f8::21e2:0:12001:7f8::21e2:0:1 2001:7f8::21e2:0:2
    Port speed differs1G2 × 1G
    • Add an entry: IPv4 80.81.193.160, IPv6 2001:7f8::21e2:0:2, speed 1000 (1G), RS peer yes.
  3. United States HOUIX Houston, United States · PeeringDB 2835
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 206.83.136.15: set Speed to 1000 (1G) (now 10000).
  4. Australia IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 27.106.192.67: set Speed to 100000 (100G) (now 20000).

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

  5. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 218.100.52.147: set Speed to 100000 (100G) (now 20000).

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

  6. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:43f8:6d0::9:160none
    • In the entry with IPv4 196.60.9.160: set IPv6 to (empty) (now 2001:43f8:6d0::9:160).

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

  7. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export212.237.192.74 212.237.192.75212.237.192.75
    IPv6 address in PeeringDB, not in the export2001:7f8:d:202::74 2001:7f8:d:202::752001:7f8:d:202::75
    • The entry with IPv4 212.237.192.74, IPv6 2001:7f8:d:202::74 isn't in the export: delete it if that connection is gone.
  8. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export212.237.193.74 212.237.193.75212.237.193.75
    IPv6 address in PeeringDB, not in the export2001:7f8:d:203::74 2001:7f8:d:203::752001:7f8:d:203::75
    • The entry with IPv4 212.237.193.74, IPv6 2001:7f8:d:203::74 isn't in the export: delete it if that connection is gone.
  9. Sweden Netnod Gothenburg -- MTU1500 Gothenburg, Sweden · PeeringDB 192
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB194.68.130.72 is AS39871 Netnod Gothenburg194.68.130.72
    Address belongs to another network in PeeringDB2001:7f8:d:100::72 is AS39871 Netnod Gothenburg2001:7f8:d:100::72
    IPv4 address in PeeringDB, not in the export194.68.130.74194.68.130.72
    IPv6 address in PeeringDB, not in the export2001:7f8:d:100::742001:7f8:d:100::72

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 194.68.130.74: set IPv4 to (empty) (now 194.68.130.74); set IPv6 to (empty) (now 2001:7f8:d:100::74).
  10. Sweden Netnod Gothenburg -- MTU4470 Gothenburg, Sweden · PeeringDB 2865
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB195.69.116.72 is AS39871 Netnod Gothenburg195.69.116.72
    Address belongs to another network in PeeringDB2001:7f8:d:101::72 is AS39871 Netnod Gothenburg2001:7f8:d:101::72
    IPv4 address in PeeringDB, not in the export195.69.116.74195.69.116.72
    IPv6 address in PeeringDB, not in the export2001:7f8:d:101::742001:7f8:d:101::72

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 195.69.116.74: set IPv4 to (empty) (now 195.69.116.74); set IPv6 to (empty) (now 2001:7f8:d:101::74).
  11. Sweden Netnod Lulea -- MTU9K Lulea, Sweden · PeeringDB 257
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB194.68.131.72 is AS20943 Netnod Lulea194.68.131.72
    Address belongs to another network in PeeringDB2001:7f8:d:400::72 is AS20943 Netnod Lulea2001:7f8:d:400::72
    IPv4 address in PeeringDB, not in the export194.68.131.74194.68.131.72
    IPv6 address in PeeringDB, not in the export2001:7f8:d:400::742001:7f8:d:400::72

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv4 194.68.131.74: set IPv4 to (empty) (now 194.68.131.74); set IPv6 to (empty) (now 2001:7f8:d:400::74).

Check these entries (4)

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

  1. Armenia ArmIX Yerevan, Armenia · PeeringDB 851Not on its website members list
    IPv491.218.7.105
    IPv62001:7f8:94::105
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  2. Malaysia MyIX Kuala Lumpur, Malaysia · PeeringDB 250Not on its website members list
    IPv4218.100.44.132
    IPv62001:de8:10::25
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  3. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.172
    IPv62001:7f8:d:fe::172
    Speed100000 Mbps (100G)
  4. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847Not on its IX-F export
    IPv4195.69.119.172
    IPv62001:7f8:d:fb::172
    Speed100000 Mbps (100G)

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