Core Transit 1097: PeeringDB fix list

AS1097 · peeringdb.com/net/35161

PeeringDB

2 things to fix in Core Transit 1097'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 Core Transit 1097'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 Core Transit 1097's PeeringDB record. Add one entry per connection with these values.

  1. United States PaducahIX Paducah, United States · PeeringDB 3407From its website members list
    IPv4149.112.114.24
    IPv62001:505:140::24
    SpeedNot published
    RS peerNot published

Check these entries (1)

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

  1. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249Not on its IX-F export or website members list
    IPv4206.53.202.69
    IPv62001:504:61::372b:0:1
    Speed10000 Mbps (10G)

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