Observed topology

AS36443 AUNALYTICS-INC

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36443: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	435
AS174	Cogent Communications, LLC	Transit	IPv4	431
AS30517	Great Lakes Comnet, Inc.	Unclassified	IPv4	223
AS33491	Comcast Cable Communications, LLC	Unclassified	IPv4	48
AS22974	Charter Communications LLC	Unclassified	IPv4	28
AS20205	Amplex Electric, Inc.	Residential	IPv4	14

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS402128	PeakFiber Broadband LLC	Unclassified	IPv4	65
AS400739	City of Mishawaka	Unclassified	IPv4	62
AS11980	BDO USA	Unclassified	IPv4	57
AS54069	Aunalytics, Inc	Unclassified	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	509
AS174	Cogent Communications, LLC	Transit	IPv4	490
AS30517	Great Lakes Comnet, Inc.	Unclassified	IPv4	247
AS402128	PeakFiber Broadband LLC	Unclassified	IPv4	65
AS400739	City of Mishawaka	Unclassified	IPv4	62
AS11980	BDO USA	Unclassified	IPv4	57
AS33491	Comcast Cable Communications, LLC	Unclassified	IPv4	55
AS22974	Charter Communications LLC	Unclassified	IPv4	53
AS20205	Amplex Electric, Inc.	Residential	IPv4	14
AS54069	Aunalytics, Inc	Unclassified	IPv4	5

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.