NSPA: PeeringDB fix list
AS210872 · peeringdb.com/net/27794
3 things to fix in NSPA's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 20:58 UTC.
Make the changes on NSPA'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 (3)
On the exchange's own member list, but not in NSPA's PeeringDB record. Add one entry per connection with these values.
-
IPv4 193.189.83.217 IPv6 2001:7f8:33::a121:872:1 Speed 100 Mbps (100M) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 – IPv6 2a0e:46c4:102::210:872:1 Speed 100 Mbps (100M) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
UNM-Exch Canada-West Vancouver, Canada · PeeringDB 2452From its IX-F export and website members list2 connections, so 2 entries:
IPv4 192.34.27.75 IPv6 – Speed Not published RS peer Not published IPv4 – IPv6 2602:ffb1:200:0:192:34:27:75 Speed Not published RS peer Not published PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/210872/: 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.