ixreport

Verizon - EMEA: PeeringDB fix list

AS702 · peeringdb.com/net/341

PeeringDB

8 things to fix in Verizon - EMEA's PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct. As of 2026-10-08 18:53 UTC.

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

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

  1. Finland FICIX 2 (Helsinki) Helsinki, Finland · PeeringDB 98From 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.

  2. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.81
    IPv62001:7f8:d:fe::81
    SpeedNot published
    RS peerNo
  3. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.81
    IPv62001:7f8:d:fb::81
    SpeedNot published
    RS peerNo
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.81
    IPv62001:7f8:d:fc::81
    SpeedNot published
    RS peerNo

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. Belgium BNIX Brussels, Belgium · PeeringDB 59
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:26::a500:702:1
    • In the entry with IPv4 194.53.172.78: set IPv6 to 2001:7f8:26::a500:702:1 (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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 80.81.193.1: set Speed to 200000 (200G) (now 100000).
  3. Greece GR-IX::Athens Athens, Greece · PeeringDB 347
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:6e::12none
    Port speed differs300M1G
    • In the entry with IPv4 176.126.38.12: set IPv6 to (empty) (now 2001:7f8:6e::12); set Speed to 1000 (1G) (now 300).

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

  4. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:14::66:1
    • In the entry with IPv4 91.210.16.25: set IPv6 to 2001:7f8:14::66:1 (now empty).

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