Observed topology

AS48614 ITSOFT-AS

Unclassified RIPE

Upstreams 14 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 13

Adjacent (IPv6) 4

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS48614: 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
AS49063	Data Storage Center JSC	Unclassified	IPv4 IPv6	602
AS20764	CJSC RASCOM	Unclassified	IPv4	355
AS59692	IQWeb FZ-LLC	Unclassified	IPv4	112
AS57304	JSC "RetnNet"	Unclassified	IPv4	80
AS50673	Serverius Holding B.V.	Unclassified	IPv4	30
AS6939	Hurricane Electric LLC	Transit	IPv6	20
AS24482	SG.GS	Hosting	IPv4 IPv6	20
AS9002	RETN Limited	Unclassified	IPv4	16
AS49673	Truenetwork LLC	Unclassified	IPv4	16
AS37721	Virtual Technologies & Solutions	Residential	IPv4	15

All 14 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS213506	VKUSVILL JSC	Unclassified	IPv4	59

Adjacency

Adjacent networks

All 15

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

AS	Network	Type	Families	Paths seen
AS49063	Data Storage Center JSC	Unclassified	IPv4 IPv6	661
AS20764	CJSC RASCOM	Unclassified	IPv4	355
AS59692	IQWeb FZ-LLC	Unclassified	IPv4	112
AS57304	JSC "RetnNet"	Unclassified	IPv4	80
AS213506	VKUSVILL JSC	Unclassified	IPv4	59
AS50673	Serverius Holding B.V.	Unclassified	IPv4	30
AS6939	Hurricane Electric LLC	Transit	IPv6	20
AS24482	SG.GS	Hosting	IPv4 IPv6	20
AS9002	RETN Limited	Unclassified	IPv4	16
AS49673	Truenetwork LLC	Unclassified	IPv4	16

All 15 adjacent →

Provenance

Where this comes from

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