Nationwide Telephone Assistance Ltd: PeeringDB fix list

AS41379 · peeringdb.com/net/12029

PeeringDB

2 things to fix in Nationwide Telephone Assistance Ltd's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Nationwide Telephone Assistance Ltd'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 Nationwide Telephone Assistance Ltd's PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321From its IX-F export and website members list
    IPv4195.66.239.32
    IPv62001:7f8:4:1::a1a3:1
    Speed1000 Mbps (1G)
    RS peerYes

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 LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::a1a3:1
    • In the entry with IPv4 195.66.227.32: set IPv6 to 2001:7f8:4::a1a3:1 (now empty).

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