asn.dev

Observed topology

AS7393 CYBERCON - CYBERCON, INC.

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7393: 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
AS1299Arelion Sweden ABTransitIPv4 IPv65,432
AS174Cogent Communications, LLCTransitIPv4 IPv62,777

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33755Valor Holdings LLCHostingIPv4 IPv6809
AS35916MULTACOM CORPORATIONHostingIPv458
AS25928Wisper ISP, LLCUnclassifiedIPv49

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv66,124
AS174Cogent Communications, LLCTransitIPv4 IPv63,023
AS33755Valor Holdings LLCHostingIPv4 IPv6872
AS35916MULTACOM CORPORATIONHostingIPv458
AS25928Wisper ISP, LLCUnclassifiedIPv49
AS2914NTT America, Inc.TransitIPv41

Provenance

Where this comes from

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