Virgin Media: PeeringDB fix list

AS5089 · peeringdb.com/net/1412

PeeringDB

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

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

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 LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::13e1:1 2001:7f8:4::13e1:2
    Port speed differs2 × 100G2 × 200G
    • In the entry with IPv4 195.66.224.22: set IPv6 to 2001:7f8:4::13e1:2 (now empty); set Speed to 200000 (200G) (now 100000).
    • In the entry with IPv4 195.66.224.23: set IPv6 to 2001:7f8:4::13e1:1 (now empty); set Speed to 200000 (200G) (now 100000).
  2. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:2::13e1:1
    Port speed differs100G200G
    • In the entry with IPv4 195.66.244.33: set IPv6 to 2001:7f8:4:2::13e1:1 (now empty); set Speed to 200000 (200G) (now 100000).

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