Observed topology
AS50384 iHome LLC
Unclassified RIPE NSP
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS50384 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS30855 | Tele-plus LLC | Unclassified | IPv4 | 52 |
| AS3226 | OOO "NI" | Unclassified | IPv4 | 48 |
| AS57045 | Panin Kirill Evgenyevich | Unclassified | IPv4 | 44 |
| AS2854 | LLC Orange Business Services | Unclassified | IPv4 IPv6 | 38 |
| AS8369 | Intersvyaz-2 JSC | Residential | IPv4 | 33 |
| AS50766 | Roman Eduardovich Zamkov | Hosting | IPv4 IPv6 | 25 |
| AS48642 | Joint stock company "For" | Unclassified | IPv4 | 24 |
| AS197078 | Yarnet Ltd | Unclassified | IPv4 | 18 |
| AS5429 | Telecommunications center UMOS, LLC | Unclassified | IPv4 | 14 |
| AS205638 | "TBANK" JSC | Unclassified | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50384 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 151 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 111 |
| AS57045 | Panin Kirill Evgenyevich | Unclassified | IPv4 | 67 |
| AS2854 | LLC Orange Business Services | Unclassified | IPv4 IPv6 | 62 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 59 |
| AS30855 | Tele-plus LLC | Unclassified | IPv4 | 52 |
| AS42708 | Glesys AB | Unclassified | IPv4 | 49 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 49 |
| AS3226 | OOO "NI" | Unclassified | IPv4 | 48 |
| AS25549 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 38 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.