Ninja-IX Las Vegas: operator report
Las Vegas, United States · PeeringDB 1488 · ixreport.com/ix/1488/report/
Members of Ninja-IX Las Vegas that PeeringDB has wrong, from its IX-F export (10 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 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 (3)
These networks could add Ninja-IX Las Vegas to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS112 DNS-OARC-112 | IX-F | 206.71.8.12 2001:504:68::12 10G |
Technical: email address (needs JavaScript) |
| AS25152 RIPE NCC K-Root Operations | IX-F | 206.71.8.19 2001:504:68::19 10G |
No public contact |
| AS47065 Columbia/UFMG PEERING Research Testbed | IX-F | 206.71.8.17 2001:504:68::17 10G |
No public contact |
Addresses or port speeds that differ (2)
PeeringDB against your IX-F export, for the 7 networks in both. Either the network's PeeringDB record or the export is out of date.
In PeeringDB, not on your lists (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.