Observed topology

AS34358 CYBER_FOLKS-RO-DC_FLO

Hosting RIPE

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34358: 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
AS5606	GTS Telecom SRL	Unclassified	IPv4	1,932
AS174	Cogent Communications, LLC	Transit	IPv4	591
AS8953	Orange Romania S.A.	Residential	IPv4	172
AS8708	DIGI ROMANIA S.A.	Mobile	IPv4	98
AS32787	Akamai Technologies, Inc.	Hosting	IPv4	60

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS35775	ACTIVE SOFT SRL	Unclassified	IPv4	171
AS43927	HOSTERION SRL	Unclassified	IPv4	57
AS56514	Sprint Telecom SRL	Unclassified	IPv4	57

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS5606	GTS Telecom SRL	Unclassified	IPv4	2,130
AS174	Cogent Communications, LLC	Transit	IPv4	656
AS8953	Orange Romania S.A.	Residential	IPv4	183
AS35775	ACTIVE SOFT SRL	Unclassified	IPv4	171
AS8708	DIGI ROMANIA S.A.	Mobile	IPv4	109
AS32787	Akamai Technologies, Inc.	Hosting	IPv4	60
AS43927	HOSTERION SRL	Unclassified	IPv4	57
AS56514	Sprint Telecom SRL	Unclassified	IPv4	57

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.