asn.dev

Observed topology

AS55350 VSCGT-HK - Virtual Switching Consultancy Limited (C/O VXRoutes Ltd)

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55350: 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
AS9304HGC Global Communications LimitedHostingIPv4201
AS6939Hurricane Electric LLCTransitIPv4 IPv667
AS40676Psychz NetworksHostingIPv458
AS24482SG.GSHostingIPv4 IPv64
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv43
AS8359MTS PJSCMobileIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135552Shinetown Telecommunication LimitedUnclassifiedIPv457

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9304HGC Global Communications LimitedHostingIPv4245
AS6939Hurricane Electric LLCTransitIPv4 IPv676
AS40676Psychz NetworksHostingIPv458
AS135552Shinetown Telecommunication LimitedUnclassifiedIPv457
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv45
AS24482SG.GSHostingIPv4 IPv65
AS8359MTS PJSCMobileIPv44

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-06 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.