Ninja-IX Sacramento: operator report
Sacramento, United States · PeeringDB 2032 · ixreport.com/ix/2032/report/
Members of Ninja-IX Sacramento that PeeringDB has wrong, from its IX-F export (7 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 (2)
These networks could add Ninja-IX Sacramento 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.13.12 2001:504:70::12 10G |
Technical: email address (needs JavaScript) |
| AS47065 Columbia/UFMG PEERING Research Testbed | IX-F | 206.71.13.17 2001:504:70::17 10G |
No public contact |
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 5 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS26175 Ninja-IX Sacramento Route Servers | Port speed differs | 2 × 1G | 2 × 10G | No public contact |
In PeeringDB, not on your lists (2)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.