asn.dev

Observed topology

AS42905 LIMANET LTD LIMANET

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42905: 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 LimitedUnclassifiedIPv4 IPv6230
AS6939Hurricane Electric LLCTransitIPv4 IPv6181
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv699
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv659
AS3303Swisscom (Schweiz) AGResidentialIPv424
AS24482SG.GSHostingIPv4 IPv617
AS34927iFog GmbHHostingIPv48
AS50629LWLcom GmbHUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44800BELNET LTDUnclassifiedIPv4118
AS52128Gigabait+ LLCUnclassifiedIPv499
AS202483PP Teleradiocompany "KRAFT"UnclassifiedIPv459
AS56401PE "MIRTELEKOM"UnclassifiedIPv448
AS43384State University of Intelligent Technologies and TelecommunicationsUnclassifiedIPv41

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6365
AS6939Hurricane Electric LLCTransitIPv4 IPv6237
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv6167
AS44800BELNET LTDUnclassifiedIPv4118
AS52128Gigabait+ LLCUnclassifiedIPv499
AS35320Eurotranstelecom LtdUnclassifiedIPv4 IPv694
AS202483PP Teleradiocompany "KRAFT"UnclassifiedIPv459
AS56401PE "MIRTELEKOM"UnclassifiedIPv448
AS3303Swisscom (Schweiz) AGResidentialIPv431
AS24482SG.GSHostingIPv4 IPv623

Provenance

Where this comes from

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