ixreport

AVR Group: PeeringDB fix list

AS42009 · peeringdb.com/net/17174

PeeringDB

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

Make the changes on AVR Group'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 (2)

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

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.231.130
    IPv62001:7f8:4::a419:1
    Speed1000 Mbps (1G)
    RS peerNo
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321From its IX-F export and website members list
    IPv4195.66.236.78
    IPv62001:7f8:4:1::a419:1
    Speed1000 Mbps (1G)
    RS peerNo

Correct these entries (1)

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. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs1G2G + 100M
    • In the entry with IPv4 195.66.244.109: set Speed to 2000 (2G) (now 1000).

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