asn.dev

Observed topology

AS8708 RCS-RDS 73-75 Dr. Staicovici

Mobile RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8708: 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
AS6910DIGI ROMANIA S.A.ResidentialIPv4 IPv68,099

Transit

Downstream networks

All 372

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

ASNetworkTypeFamiliesPaths seen
AS57269DIGI SPAIN TELECOM S.AUnclassifiedIPv4 IPv6599
AS31102TV Adler-Trading SRLUnclassifiedIPv4570
AS33911Tennet Telecom SRLUnclassifiedIPv4470
AS211462Andrei Tiberiu HoltUnclassifiedIPv4 IPv6459
AS49645Soft Expert SRLUnclassifiedIPv4 IPv6407
AS39347STYLISH BY A&L SRLHostingIPv4401
AS57050DreamServer S.R.L.UnclassifiedIPv4 IPv6376
AS218560AITEST SRLUnclassifiedIPv4 IPv6375
AS5606GTS Telecom SRLUnclassifiedIPv4 IPv6346
AS8930EX MEDIA SAUnclassifiedIPv4228

All 372 downstreams →

Adjacency

Adjacent networks

All 375

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

ASNetworkTypeFamiliesPaths seen
AS6910DIGI ROMANIA S.A.ResidentialIPv4 IPv629,788
AS5606GTS Telecom SRLUnclassifiedIPv4 IPv6812
AS57269DIGI SPAIN TELECOM S.AUnclassifiedIPv4 IPv6779
AS31102TV Adler-Trading SRLUnclassifiedIPv4570
AS41151Digital IT Consulting SRLHostingIPv4 IPv6547
AS33911Tennet Telecom SRLUnclassifiedIPv4470
AS57050DreamServer S.R.L.UnclassifiedIPv4 IPv6462
AS211462Andrei Tiberiu HoltUnclassifiedIPv4 IPv6459
AS49645Soft Expert SRLUnclassifiedIPv4 IPv6407
AS39347STYLISH BY A&L SRLHostingIPv4401

All 375 adjacent →

Provenance

Where this comes from

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