asn.dev

Observed topology

AS11588 LAMBDA-BB - Lambda

Hosting ARIN

Upstreams 8 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 8
Upstream graph Who carries AS11588, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS11588 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11588: 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.

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv6122
AS1299Arelion Sweden ABTransitIPv4 IPv670
AS3356Level 3 Parent, LLCTransitIPv4 IPv648
AS174Cogent Communications, LLCTransitIPv421
AS6939Hurricane Electric LLCTransitIPv4 IPv616
AS2914NTT America, Inc.TransitIPv4 IPv613
AS1403EBOXResidentialIPv4 IPv64
AS34927iFog GmbHHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398090LambdaHostingIPv4 IPv6329

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS398090LambdaHostingIPv4 IPv6329
AS1299Arelion Sweden ABTransitIPv4 IPv6273
AS6461Zayo BandwidthTransitIPv4 IPv6173
AS3356Level 3 Parent, LLCTransitIPv4 IPv683
AS2914NTT America, Inc.TransitIPv4 IPv641
AS6939Hurricane Electric LLCTransitIPv4 IPv625
AS174Cogent Communications, LLCTransitIPv421
AS1403EBOXResidentialIPv4 IPv66
AS34927iFog GmbHHostingIPv62

Provenance

Where this comes from

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