asn.dev

Observed topology

AS205495 LT-AS OOO "L-Telecom"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205495: 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
AS12389PJSC RostelecomResidentialIPv4272
AS35598INETCOM CARRIER LLCUnclassifiedIPv4159
AS57304JSC "RetnNet"UnclassifiedIPv496
AS1299Arelion Sweden ABTransitIPv488
AS62255BiMajLink d.o.o.UnclassifiedIPv430
AS29076Citytelecom LLCHostingIPv424
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS25227JSC "ER-Telecom Holding"UnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207473OOO "ZVI Telecom"UnclassifiedIPv431

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4303
AS35598INETCOM CARRIER LLCUnclassifiedIPv4159
AS57304JSC "RetnNet"UnclassifiedIPv496
AS1299Arelion Sweden ABTransitIPv488
AS207473OOO "ZVI Telecom"UnclassifiedIPv431
AS62255BiMajLink d.o.o.UnclassifiedIPv430
AS29076Citytelecom LLCHostingIPv424
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS25227JSC "ER-Telecom Holding"UnclassifiedIPv43

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.