asn.dev

Observed topology

AS29031 LTC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29031: 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
AS201776Miranda-Media LtdUnclassifiedIPv4650
AS39728Likhno Dmitriy trading as LuganetUnclassifiedIPv435
AS43201Telematika LLCUnclassifiedIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49444Lutacom LLCUnclassifiedIPv4422
AS209747Osipenko Alexander NikolaevichUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS201776Miranda-Media LtdUnclassifiedIPv41,142
AS49444Lutacom LLCUnclassifiedIPv4422
AS43201Telematika LLCUnclassifiedIPv4199
AS58271Tyatkova Oksana ValerievnaUnclassifiedIPv4183
AS209747Osipenko Alexander NikolaevichUnclassifiedIPv462
AS39728Likhno Dmitriy trading as LuganetUnclassifiedIPv439

Provenance

Where this comes from

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