asn.dev

Observed topology

AS21211 PENKI-AS LT-01115, Vilnius

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21211: 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
AS9002RETN LimitedUnclassifiedIPv4941
AS13194UAB "Bite Lietuva"UnclassifiedIPv4 IPv6562
AS6939Hurricane Electric LLCTransitIPv4270
AS3303Swisscom (Schweiz) AGResidentialIPv431

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198009Ashburn International Ltd.UnclassifiedIPv459
AS211336UAB Penki kontinentaiUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv41,016
AS13194UAB "Bite Lietuva"UnclassifiedIPv4 IPv6595
AS6939Hurricane Electric LLCTransitIPv4279
AS198009Ashburn International Ltd.UnclassifiedIPv459
AS211336UAB Penki kontinentaiUnclassifiedIPv459
AS3303Swisscom (Schweiz) AGResidentialIPv432

Provenance

Where this comes from

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