Observed topology

AS8103 STATE-OF-FLA

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8103: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	31,471
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	16,132

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS394126	The School District of Escambia County	Unclassified	IPv4	2,527
AS36514	Florida Legislature	Unclassified	IPv4	885
AS36300	Pinellas County Schools	Unclassified	IPv4	640
AS31898	Oracle Corporation	Hosting	IPv4	59
AS7202	Florida A & M University	Education	IPv4	23
AS54248	School Board of Gadsden County	Unclassified	IPv4	4

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	33,576
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	18,165
AS394126	The School District of Escambia County	Unclassified	IPv4	2,527
AS36514	Florida Legislature	Unclassified	IPv4	885
AS36300	Pinellas County Schools	Unclassified	IPv4	640
AS31898	Oracle Corporation	Hosting	IPv4	59
AS7202	Florida A & M University	Education	IPv4	23
AS54248	School Board of Gadsden County	Unclassified	IPv4	4

Provenance

Where this comes from

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