asn.dev

Observed topology

AS56690 VNET-LLC-AS

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS56690: 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 LLCUnclassifiedIPv4 IPv6759
AS31500Global Network Management IncUnclassifiedIPv4 IPv6315
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv680
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv418
AS49673Truenetwork LLCUnclassifiedIPv417
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv417

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200722Cube-Telecom LLCUnclassifiedIPv49

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6759
AS31500Global Network Management IncUnclassifiedIPv4 IPv6321
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv680
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv419
AS49673Truenetwork LLCUnclassifiedIPv418
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv418
AS200722Cube-Telecom LLCUnclassifiedIPv49

Provenance

Where this comes from

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