Observed topology

AS40111 PARKERFIBERNET-AS-ROUTE

Unclassified ARIN Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40111: 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
AS6461	Zayo Bandwidth	Transit	IPv4	343
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	289
AS3356	Level 3 Parent, LLC	Transit	IPv4	255
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	151
AS19151	BroadbandONE, LLC	Hosting	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS55260	Polk School District	Unclassified	IPv4	836
AS11128	Berry College	Education	IPv4	118
AS15357	HARBIN CLINIC, LLC	Unclassified	IPv4	59
AS17296	Pioneer Broadband	Unclassified	IPv4	40

Adjacency

Adjacent networks

All 12

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

AS	Network	Type	Families	Paths seen
AS55260	Polk School District	Unclassified	IPv4	836
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	825
AS6461	Zayo Bandwidth	Transit	IPv4	797
AS3356	Level 3 Parent, LLC	Transit	IPv4	301
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	203
AS11128	Berry College	Education	IPv4	118
AS15357	HARBIN CLINIC, LLC	Unclassified	IPv4	59
AS17296	Pioneer Broadband	Unclassified	IPv4	40
AS40463	Alabama Fiber Network	Residential	IPv6	29
AS10490	Georgia Institute of Technology	Education	IPv4	8

All 12 adjacent →

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.