asn.dev

Observed topology

AS13765 NEDELCO

Unclassified ARIN

Upstreams 4 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 6
Upstream graph Who carries AS13765, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS13765 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13765: 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
AS16851NebraskaLinkResidentialIPv4186
AS3356Level 3 Parent, LLCTransitIPv4 IPv661
AS174Cogent Communications, LLCTransitIPv4 IPv636
AS6939Hurricane Electric LLCTransitIPv615

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS6621Hughes Network Systems, LLCResidentialIPv4 IPv62,776
AS11949COZAD TELEPHONE COMPANYResidentialIPv469
AS21818BWTelcomUnclassifiedIPv4 IPv643
AS16954Three River TelcoUnclassifiedIPv45

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6621Hughes Network Systems, LLCResidentialIPv4 IPv63,922
AS174Cogent Communications, LLCTransitIPv4 IPv62,526
AS6939Hurricane Electric LLCTransitIPv4 IPv6777
AS3356Level 3 Parent, LLCTransitIPv4 IPv6774
AS16851NebraskaLinkResidentialIPv4 IPv6260
AS11949COZAD TELEPHONE COMPANYResidentialIPv469
AS21818BWTelcomUnclassifiedIPv4 IPv643
AS16954Three River TelcoUnclassifiedIPv45

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.