asn.dev

Observed topology

AS48614 ITSOFT-AS ITSOFT LLC

Unclassified RIPE

Upstreams 15 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 15
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 15

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.

ASNetworkTypeFamiliesPaths seen
AS49063Data Storage Center JSCUnclassifiedIPv4 IPv6626
AS20764CJSC RASCOMUnclassifiedIPv4450
AS59692IQWeb FZ-LLCUnclassifiedIPv4168
AS50673Serverius Holding B.V.UnclassifiedIPv430
AS6939Hurricane Electric LLCTransitIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv620
AS57304JSC "RetnNet"UnclassifiedIPv418
AS49673Truenetwork LLCUnclassifiedIPv416
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv415

All 15 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.

ASNetworkTypeFamiliesPaths seen
AS213506VKUSVILL JSCUnclassifiedIPv459

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS49063Data Storage Center JSCUnclassifiedIPv4 IPv6685
AS20764CJSC RASCOMUnclassifiedIPv4450
AS59692IQWeb FZ-LLCUnclassifiedIPv4168
AS213506VKUSVILL JSCUnclassifiedIPv459
AS50673Serverius Holding B.V.UnclassifiedIPv430
AS6939Hurricane Electric LLCTransitIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv620
AS57304JSC "RetnNet"UnclassifiedIPv418
AS49673Truenetwork LLCUnclassifiedIPv416
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv416

All 16 adjacent →

Provenance

Where this comes from

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