EVOLINK EAD: PeeringDB fix list

AS8262 · peeringdb.com/net/2961

PeeringDB

5 things to fix in EVOLINK EAD's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on EVOLINK EAD'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 (5)

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. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.169.198.101 193.169.198.123193.169.198.101 193.169.198.108 193.169.198.123
    • In the entry with IPv4 193.169.198.123: set IPv4 to 193.169.198.108 (now 193.169.198.123).
    • Add an entry: IPv4 193.169.198.123, IPv6 –.
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB80.81.194.8880.81.194.88 80.81.194.223
    IPv6 address missing from PeeringDB2001:7f8::2046:0:12001:7f8::2046:0:1 2001:7f8::2046:0:2
    Port speed differs10G2 × 10G
    • Add an entry: IPv4 80.81.194.223, IPv6 2001:7f8::2046:0:2, speed 10000 (10G), RS peer yes.
  3. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 206.82.104.79: set Speed to 10000 (10G) (now 1000).
  4. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

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

  5. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2G1G
    • In the entry with IPv4 195.66.226.235: set Speed to 1000 (1G) (now 2000).

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