Ninja-IX Raleigh: operator report
Raleigh, NC, United States · PeeringDB 3445 · ixreport.com/ix/3445/report/
Members of Ninja-IX Raleigh that PeeringDB has wrong, from its IX-F export (6 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 5 networks to follow up.
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 Ninja-IX Raleigh to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS13649 Flexential Internet Services | IX-F | 206.80.232.10 2001:504:67::10 10G |
No public contact |
| AS25152 RIPE NCC K-Root Operations | IX-F | 206.80.232.19 2001:504:67::19 10G |
No public contact |
| AS47065 Columbia/UFMG PEERING Research Testbed | IX-F | 206.80.232.17 2001:504:67::17 10G |
No public contact |
| AS99999 ISC-FROOT-RDU | IX-F | 206.80.232.18 2001:504:67::18 10G |
No PeeringDB record |
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 2 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS23064 Ninja-IX Raleigh Route Servers | IPv4 address in PeeringDB, not in the export | 206.80.232.5 206.80.232.6 | 206.80.232.5 | No public contact |
| IPv6 address in PeeringDB, not in the export | 2001:504:67::5 2001:504:67::6 | 2001:504:67::5 | ||
| Port speed differs | 2 × 10G | 10G |
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.