asn.dev

Observed topology

AS11996 LOBOIS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11996: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6216
AS6461Zayo BandwidthTransitIPv4 IPv639
AS3356Level 3 Parent, LLCTransitIPv4 IPv627
AS174Cogent Communications, LLCTransitIPv4 IPv615
AS40498New Mexico Lambda Rail, Inc.UnclassifiedIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS10381Southwest Cyberport, Inc.UnclassifiedIPv4369
AS54143i9 TechnologiesUnclassifiedIPv4 IPv6125
AS33201Tilver Enterprises, LLCUnclassifiedIPv4 IPv6102
AS14818Cyber Mesa Computer Systems, IncorporatedUnclassifiedIPv4 IPv682

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6832
AS10381Southwest Cyberport, Inc.UnclassifiedIPv4369
AS33201Tilver Enterprises, LLCUnclassifiedIPv4 IPv6189
AS6461Zayo BandwidthTransitIPv4 IPv6127
AS54143i9 TechnologiesUnclassifiedIPv4 IPv6125
AS14818Cyber Mesa Computer Systems, IncorporatedUnclassifiedIPv4 IPv682
AS174Cogent Communications, LLCTransitIPv4 IPv660
AS3356Level 3 Parent, LLCTransitIPv4 IPv641
AS40498New Mexico Lambda Rail, Inc.UnclassifiedIPv4 IPv67

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.