OmahaIX: operator report

Omaha, United States · PeeringDB 809 · ixreport.com/ix/809/report/

Download CSV

Members of OmahaIX that PeeringDB has wrong, from its website members list (47 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 9 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 OmahaIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS27005 Pinpoint Communications PeeringDBwebsite 206.126.235.19
2001:504:33::13
No public contact
AS30081 CacheFly PeeringDBwebsite 206.126.235.58
2001:504:33::58
No public contact

Addresses or port speeds that differ (0)

OmahaIX publishes no IX-F export we could read, so addresses and port speeds can't be compared.

In PeeringDB, not on your lists (7)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

NetworkIn PeeringDBContact
AS8075 Microsoft PeeringDB 206.126.235.65
206.126.235.66
2001:504:33::65
2001:504:33::66
2 × 100G
Policy: email address (needs JavaScript)
AS11796 WIN Technology PeeringDB 206.126.235.29
2001:504:33::23
20G
No public contact
AS26451 FUTURE WIRELESS TECHNOLOGIES OF NEBRASKA PeeringDB 206.126.235.10
10G
No public contact
AS32261 Subspace PeeringDB 206.126.235.43
2001:504:33::37
10G
No public contact
AS54578 FiberComm PeeringDB 206.126.235.34
100G
No public contact
AS62818 Spiral Communications PeeringDB 206.126.235.19
2001:504:33::13
10G
No public contact
AS212232 BGP.Tools Route Collector PeeringDB 206.126.235.37
2001:504:33::31
1G
No public contact