SupraNet Communications: PeeringDB fix list

AS4150 · peeringdb.com/net/464

PeeringDB

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

  1. United States KCIX Kansas City, United States · PeeringDB 249From its IX-F export and website members list
    IPv4206.51.7.119
    IPv62001:504:1b:1::119
    Speed10000 Mbps (10G)
    RS peerNot published

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 States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.51.7.119 is AS397898 Power to Grow Services206.51.7.119
    Address belongs to another network in PeeringDB2001:504:1b:1::119 is AS397898 Power to Grow Services2001:504:1b:1::119

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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