TNS-Plus Core: PeeringDB fix list

AS35168 · peeringdb.com/net/18412

PeeringDB

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

Make the changes on TNS-Plus Core'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 TNS-Plus Core's PeeringDB record. Add one entry per connection with these values.

  1. Hong Kong HKIX Hong Kong, Hong Kong · PeeringDB 42From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Check these entries (1)

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

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31Not on its IX-F export or website members list
    IPv480.81.192.220
    IPv62001:7f8::8960:0:1
    Speed100000 Mbps (100G)

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