asn.dev

Observed topology

AS48571 EFECTRO-As efectRO SRL

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48571: 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
AS12302Vodafone Romania S.A.ResidentialIPv4 IPv6167
AS48161NEXTGEN COMMUNICATIONS SRLUnclassifiedIPv4146
AS8708DIGI ROMANIA S.A.MobileIPv4 IPv668

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34601Viewpoint Photo SRLUnclassifiedIPv4 IPv665
AS34951POLICOLOR SAUnclassifiedIPv458
AS49171Hypermedia SRLUnclassifiedIPv457
AS204221ATP-EXODUS SRLUnclassifiedIPv457
AS62322YONDER SRLUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12302Vodafone Romania S.A.ResidentialIPv4 IPv6278
AS48161NEXTGEN COMMUNICATIONS SRLUnclassifiedIPv4229
AS8708DIGI ROMANIA S.A.MobileIPv4 IPv6124
AS34601Viewpoint Photo SRLUnclassifiedIPv4 IPv665
AS34951POLICOLOR SAUnclassifiedIPv458
AS49171Hypermedia SRLUnclassifiedIPv457
AS204221ATP-EXODUS SRLUnclassifiedIPv457
AS62322YONDER SRLUnclassifiedIPv413

Provenance

Where this comes from

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