ixreport

AVR Group

AS42009 · National Monitoring

AVR Group Limited

3Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
2Using the route servers
3To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with AVR Group? · Where should AVR Group peer next? · Compare AVR Group with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in AVR Group's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-11-19 12:40 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).

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where AVR Group's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 3.1G across 3 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.231.130
195.66.252.17
2001:7f8:4::a419:1 1G + 100M Yes Not in PeeringDB
United Kingdom LINX LON2 London, United Kingdom 195.66.236.78 2001:7f8:4:1::a419:1 1G Not in PeeringDB
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.109 2001:7f8:4:2::a419:1 1G 4 routes Both Speed differs

Exchanges in its buildings that it isn't on (2)

These exchanges have a switch in a facility where AVR Group lists itself in PeeringDB, but don't have AVR Group as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United Kingdom IXLeedsLeeds / Western Yorkshire, United Kingdom 22 aql DC2
United Kingdom Equinix ManchesterManchester, United Kingdom 19 Equinix MA1 - Manchester, Williams/Kilburn
Facilities (3)

The buildings AVR Group lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Equinix MA1 - Manchester, Williams/KilburnManchester 1 of 2
United Kingdom aql DC2Leeds 0 of 1
United Kingdom Volta ManchesterManchester 1 of 1