Observed topology

AS39668 AS-INTERSAT_CT Ion Ratiu nr.33

Residential RIPE

Upstreams 4 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39668: 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
AS12310	iNES GROUP SRL	Unclassified	IPv4	220
AS9050	Orange Romania S.A.	Residential	IPv4	158
AS24482	SG.GS	Hosting	IPv4	5
AS24745	Orange Romania S.A.	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS42280	WebNet Solutions SRL	Unclassified	IPv4	109
AS49256	INDUSTRIA MUNDUM S.R.L.	Unclassified	IPv4	65
AS208475	NRG Evolution srl	Unclassified	IPv4	52

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12310	iNES GROUP SRL	Unclassified	IPv4	375
AS9050	Orange Romania S.A.	Residential	IPv4	226
AS42280	WebNet Solutions SRL	Unclassified	IPv4	109
AS49256	INDUSTRIA MUNDUM S.R.L.	Unclassified	IPv4	65
AS208475	NRG Evolution srl	Unclassified	IPv4	52
AS24482	SG.GS	Hosting	IPv4	8
AS24745	Orange Romania S.A.	Unclassified	IPv4	1

Provenance

Where this comes from

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