asn.dev

Observed topology

AS11714 NETWORK NEBRASKA

Education ARIN

Upstreams 4 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 2
Upstream graph Who carries AS11714, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS11714 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11714: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,446
AS15108Allo Communications LLCResidentialIPv4387
AS7029Windstream Communications LLCResidentialIPv4254
AS7896The Board of Regents of the University of NebraskaEducationIPv4 IPv6163

Transit

Downstream networks

inferred

Networks for which AS11714 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS30569Creighton UniversityUnclassifiedIPv42,668
AS54072Central Community CollegeUnclassifiedIPv4139
AS13691Metropolitan Community CollegeUnclassifiedIPv4136
AS40716DOT.CommUnclassifiedIPv442
AS395896Southeast Community CollegeUnclassifiedIPv421

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS11714 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,976
AS30569Creighton UniversityUnclassifiedIPv42,668
AS15108Allo Communications LLCResidentialIPv4490
AS7896The Board of Regents of the University of NebraskaEducationIPv4 IPv6418
AS7029Windstream Communications LLCResidentialIPv4372
AS54072Central Community CollegeUnclassifiedIPv4139
AS13691Metropolitan Community CollegeUnclassifiedIPv4136
AS40716DOT.CommUnclassifiedIPv442
AS395896Southeast Community CollegeUnclassifiedIPv421

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.