Ninja-IX Dallas: operator report

Dallas, United States · PeeringDB 2318 · ixreport.com/ix/2318/report/

Download CSV

Members of Ninja-IX Dallas 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; 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 Dallas to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS112 DNS-OARC-112 PeeringDBIX-F 206.71.139.12
2001:504:75::12
10G		 Technical: email address (needs JavaScript)
AS47065 Columbia/UFMG PEERING Research Testbed PeeringDBIX-F 206.71.139.17
2001:504:75::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.

NetworkProblemPeeringDB hasYour export hasContact
AS12233 Ninja-Cache PeeringDB IPv6 address in PeeringDB, not in the export2001:504:75::8none No public contact
AS22454 Ninja-IX Dallas Route Servers PeeringDB Port speed differs2 × 1G2 × 10G No public contact

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.