York Data Services: PeeringDB fix list

AS43013 · peeringdb.com/net/3132

PeeringDB

3 things to fix in York Data Services's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on York Data Services'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 (1)

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

  1. United Kingdom IXLeeds Leeds / Western Yorkshire, United Kingdom · PeeringDB 435From its IX-F export and website members list
    IPv491.217.231.13
    IPv62001:7f8:67::a805:1
    SpeedNot published
    RS peerNot published

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If York Data Services has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.225.139
    IPv62001:7f8:4::a805:1
    Speed10000 Mbps (10G)
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53Not on its IX-F export
    IPv45.57.81.208
    IPv62001:7f8:17::a805:1
    Speed10000 Mbps (10G)

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