ixreport

Telavox: PeeringDB fix list

AS44123 · peeringdb.com/net/4301

PeeringDB

4 things to fix in Telavox's PeeringDB record, from what its exchanges publish: 2 to add, 2 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Telavox'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 Telavox'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.247
    IPv62001:7f8:4::ac5b:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321From its IX-F export and website members list
    IPv4195.66.236.121
    IPv62001:7f8:4:1::ac5b:1
    Speed10000 Mbps (10G)
    RS peerYes

Check these entries (2)

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

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.232
    IPv62001:7f8:d:fe::232
    Speed100 Mbps (100M)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.232
    IPv62001:7f8:d:ff::232
    Speed100 Mbps (100M)

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