Observed topology

AS36295 FLORIDA-HIGH-SPEED-INTERNET

Residential ARIN

Upstreams 4 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36295: 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 IPv6	2,858
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	682
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	480
AS3356	Level 3 Parent, LLC	Transit	IPv4	67

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS903	Unified Communications Technologies, LLC	Unclassified	IPv4	648
AS16896	NCN	Unclassified	IPv4	132
AS10851	St Johns County BOCC	Unclassified	IPv6	37

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	3,628
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	712
AS903	Unified Communications Technologies, LLC	Unclassified	IPv4	648
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	563
AS16896	NCN	Unclassified	IPv4	132
AS3356	Level 3 Parent, LLC	Transit	IPv4	67
AS27626	Joytel	Unclassified	IPv4	66
AS10851	St Johns County BOCC	Unclassified	IPv6	37

Provenance

Where this comes from

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