InterNexa: PeeringDB fix list

AS18678 · peeringdb.com/net/3171

PeeringDB

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

  1. United States CIX-ATL Atlanta, United States · PeeringDB 1668From its IX-F export and website members list
    IPv4206.71.12.87
    IPv62001:504:40:12::1:87
    Speed100000 Mbps (100G)
    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 States CIX-ATL Atlanta, United States · PeeringDB 1668
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.71.12.87 is AS399055 Southeast Networks206.71.12.87

    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/18678/: 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.