asn.dev

Observed topology

AS50084 RAPID-LINK-AS Gh. Asachi 717

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS50084: 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
AS5606GTS Telecom SRLUnclassifiedIPv4 IPv6329
AS9002RETN LimitedUnclassifiedIPv4 IPv6129

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60405Radeon Service S.R.L.UnclassifiedIPv480
AS43818S.C."LOGIGRUP" SRLUnclassifiedIPv460
AS203693EBS INTEGRATOR SRLUnclassifiedIPv459
AS41712Satelit Vizual s.r.l.UnclassifiedIPv43
AS19197Stefanini, Inc.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5606GTS Telecom SRLUnclassifiedIPv4 IPv6486
AS9002RETN LimitedUnclassifiedIPv4 IPv6304
AS60405Radeon Service S.R.L.UnclassifiedIPv481
AS43818S.C."LOGIGRUP" SRLUnclassifiedIPv460
AS203693EBS INTEGRATOR SRLUnclassifiedIPv459
AS41712Satelit Vizual s.r.l.UnclassifiedIPv43
AS19197Stefanini, Inc.UnclassifiedIPv41

Provenance

Where this comes from

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