Observed topology

AS40511 FIRELINE

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40511: 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	1,486
AS6461	Zayo Bandwidth	Transit	IPv4	418
AS174	Cogent Communications, LLC	Transit	IPv4	244
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	34
AS24482	SG.GS	Hosting	IPv4	34
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS32576	1-800LoanMart	Unclassified	IPv4	36

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,523
AS6461	Zayo Bandwidth	Transit	IPv4	419
AS174	Cogent Communications, LLC	Transit	IPv4	246
AS24482	SG.GS	Hosting	IPv4	36
AS32576	1-800LoanMart	Unclassified	IPv4	36
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4	34
AS7575	Australian Academic and Research Network (AARNet)	Education	IPv4	3

Provenance

Where this comes from

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