asn.dev

Observed topology

AS27373 DOUGLAS-COUNTY-COMMUNITY-NETWORK

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS27373: 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
AS16713Northwest Open Access NetworkUnclassifiedIPv4 IPv6467
AS20055Wholesail networks LLCResidentialIPv4 IPv624

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33677509fiberUnclassifiedIPv4 IPv6101
AS11665North RidgeUnclassifiedIPv4 IPv697
AS19800Grant County Public Utility DistrictUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16713Northwest Open Access NetworkUnclassifiedIPv4 IPv6675
AS33677509fiberUnclassifiedIPv4 IPv6101
AS11665North RidgeUnclassifiedIPv4 IPv697
AS20055Wholesail networks LLCResidentialIPv4 IPv678
AS19800Grant County Public Utility DistrictUnclassifiedIPv465
AS3Massachusetts Institute of TechnologyEducationIPv41

Provenance

Where this comes from

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