NNENIX: operator report
Portland, United States · PeeringDB 1679 · ixreport.com/ix/1679/report/
Members of NNENIX that PeeringDB has wrong, from its website members list (13 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 5 networks to follow up; 1 with a public PeeringDB contact.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
On your lists, missing from PeeringDB (4)
These networks could add NNENIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
Addresses or port speeds that differ (0)
NNENIX publishes no IX-F export we could read, so addresses and port speeds can't be compared.
In PeeringDB, not on your lists (1)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
| Network | In PeeringDB | Contact |
|---|---|---|
| AS396180 NNENIX Route Servers | 206.71.140.11 206.71.140.12 2001:504:76:1020::b 2001:504:76:1020::c 2 × 2G |
NOC: email address (needs JavaScript) |