Observed topology

AS393442 UNITED-FIBER - United Electric Cooperative

Residential ARIN Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

Upstream graph Who carries AS393442, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS393442 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS393442: 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.

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	4,352
AS6939	Hurricane Electric LLC	Transit	IPv4	3,176
AS395129	United Electric Cooperative	Unclassified	IPv4	336
AS17303	Disaster Networks, LLC	Unclassified	IPv4	120
AS52025	ParadoxNetworks Limited	Unclassified	IPv4	7

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS395129	United Electric Cooperative	Unclassified	IPv4	321
AS398903	Double K Technologies, LLC	Unclassified	IPv4	58
AS19866	News-Press & Gazette Company	Unclassified	IPv4	26

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	4,740
AS6939	Hurricane Electric LLC	Transit	IPv4	3,195
AS395129	United Electric Cooperative	Unclassified	IPv4	657
AS17303	Disaster Networks, LLC	Unclassified	IPv4	120
AS398903	Double K Technologies, LLC	Unclassified	IPv4	58
AS19866	News-Press & Gazette Company	Unclassified	IPv4	26
AS52025	ParadoxNetworks Limited	Unclassified	IPv4	7
AS62943	Missouri Network Alliance, LLC	Unclassified	IPv4	2

Provenance

Where this comes from

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