Observed topology

AS35584 RO-BMSITGROUP-AS

Unclassified RIPE

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

Upstream graph Who carries AS35584, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS35584 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35584: 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
AS39737	Prime Telecom srl	Unclassified	IPv4	86
AS6939	Hurricane Electric LLC	Transit	IPv4	16
AS41494	Asociatia Interlan	Unclassified	IPv4	12
AS20764	CJSC RASCOM	Unclassified	IPv4	2
AS24482	SG.GS	Hosting	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS206431	AC&CA Consulting Services SRL	Unclassified	IPv4	118
AS56553	REVEL BUSINESS GROUP SRL	Unclassified	IPv4	116
AS39888	TRUST MOTORS SRL	Unclassified	IPv4	10

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS39737	Prime Telecom srl	Unclassified	IPv4	268
AS206431	AC&CA Consulting Services SRL	Unclassified	IPv4	118
AS56553	REVEL BUSINESS GROUP SRL	Unclassified	IPv4	116
AS6939	Hurricane Electric LLC	Transit	IPv4	52
AS41494	Asociatia Interlan	Unclassified	IPv4	30
AS39888	TRUST MOTORS SRL	Unclassified	IPv4	10
AS20764	CJSC RASCOM	Unclassified	IPv4	6
AS24482	SG.GS	Hosting	IPv4	6

Provenance

Where this comes from

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