Ninja-IX Richmond: operator report
Richmond, United States · PeeringDB 1490 · ixreport.com/ix/1490/report/
Members of Ninja-IX Richmond that PeeringDB has wrong, from its IX-F export (9 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 4 networks to follow up; 2 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 Richmond 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.9.12 2001:504:79::12 10G |
Technical: email address (needs JavaScript) |
| AS1828 Unitas Global | IX-F | 206.71.9.14 2001:504:79::14 10G |
Policy: email address (needs JavaScript) |
Addresses or port speeds that differ (1)
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.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS12233 Ninja-Cache | IPv6 address in PeeringDB, not in the export | 2001:504:79::8 | none | No public contact |
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 |
|---|---|---|
| AS30025 Richmond-IX Transit | 206.71.9.10 2001:504:79::10 10G |
No public contact |