asn.dev

Observed topology

AS57393 VIVA-AS

Unclassified RIPE

Upstreams 9 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 0
Upstream graph Who carries AS57393, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS57393 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57393: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4426
AS31500Global Network Management IncUnclassifiedIPv463
AS62255BiMajLink d.o.o.UnclassifiedIPv457
AS50673Serverius Holding B.V.UnclassifiedIPv412
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46
AS34927iFog GmbHHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201469Concept Ltd.UnclassifiedIPv4132

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4538
AS201469Concept Ltd.UnclassifiedIPv4132
AS62255BiMajLink d.o.o.UnclassifiedIPv477
AS31500Global Network Management IncUnclassifiedIPv463
AS50673Serverius Holding B.V.UnclassifiedIPv412
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS49673Truenetwork LLCUnclassifiedIPv46
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46
AS34927iFog GmbHHostingIPv42

Provenance

Where this comes from

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