asn.dev

Observed topology

AS50384 iHome LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50384: 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
AS12552GlobalConnect ABUnclassifiedIPv41

Transit

Downstream networks

All 36

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

ASNetworkTypeFamiliesPaths seen
AS30855Tele-plus LLCUnclassifiedIPv460
AS3226OOO "NI"UnclassifiedIPv459
AS8369Intersvyaz-2 JSCResidentialIPv456
AS57045Panin Kirill EvgenyevichUnclassifiedIPv448
AS2854LLC Orange Business ServicesUnclassifiedIPv4 IPv637
AS197078Yarnet LtdUnclassifiedIPv437
AS50766Roman Eduardovich ZamkovHostingIPv4 IPv625
AS5429Telecommunications center UMOS, LLCUnclassifiedIPv414
AS205638"TBANK" JSCUnclassifiedIPv414
AS47481Lime HD LLCHostingIPv413

Adjacency

Adjacent networks

All 70

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

ASNetworkTypeFamiliesPaths seen
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6148
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv6112
AS42708Glesys Sweden ABUnclassifiedIPv4112
AS52091Level-MSK Ltd.UnclassifiedIPv478
AS57045Panin Kirill EvgenyevichUnclassifiedIPv471
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv661
AS2854LLC Orange Business ServicesUnclassifiedIPv4 IPv660
AS30855Tele-plus LLCUnclassifiedIPv460
AS3226OOO "NI"UnclassifiedIPv459
AS8369Intersvyaz-2 JSCResidentialIPv456

Provenance

Where this comes from

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