asn.dev

Observed topology

AS43404 UCARU-AS

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS43404: 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 RostelecomResidentialIPv458
AS20485Joint Stock Company TransTeleComUnclassifiedIPv444
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv611
AS8732JSC ComcorUnclassifiedIPv44
AS50673Serverius Holding B.V.UnclassifiedIPv44
AS9002RETN LimitedUnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS49673Truenetwork LLCUnclassifiedIPv42

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51410Fastnet LLCUnclassifiedIPv4 IPv674
AS34687Fastnet LLCUnclassifiedIPv460
AS35780Logix Telecom LLCUnclassifiedIPv460
AS209228MP-Nedvizhimost LLCUnclassifiedIPv460

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4160
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv691
AS51410Fastnet LLCUnclassifiedIPv4 IPv674
AS34687Fastnet LLCUnclassifiedIPv460
AS35780Logix Telecom LLCUnclassifiedIPv460
AS209228MP-Nedvizhimost LLCUnclassifiedIPv460
AS12389PJSC RostelecomResidentialIPv458
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS8732JSC ComcorUnclassifiedIPv414
AS24482SG.GSHostingIPv4 IPv68

All 18 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 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.