asn.dev

Observed topology

AS23930 VITROINC-AS-AP VITRO INC.

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23930: 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
AS76295F L.V. Locsin BldgUnclassifiedIPv4 IPv64,418
AS6939Hurricane Electric LLCTransitIPv4 IPv6868
AS17639Converge ICT Solutions Inc.UnclassifiedIPv493
AS24482SG.GSHostingIPv4 IPv683
AS15412Flag Telecom UK LimitedUnclassifiedIPv4 IPv632
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv612
AS4637Telstra GlobalUnclassifiedIPv43
AS9304HGC Global Communications LimitedHostingIPv61
AS9505Taiwan Internet GatewayUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132209VITRO INC.UnclassifiedIPv4136
AS206804Realcloud OUUnclassifiedIPv4121
AS76295F L.V. Locsin BldgUnclassifiedIPv630
AS38491VITRO INC.UnclassifiedIPv42

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS76295F L.V. Locsin BldgUnclassifiedIPv4 IPv64,670
AS6939Hurricane Electric LLCTransitIPv4 IPv6900
AS132209VITRO INC.UnclassifiedIPv4136
AS206804Realcloud OUUnclassifiedIPv4121
AS17639Converge ICT Solutions Inc.UnclassifiedIPv497
AS24482SG.GSHostingIPv4 IPv688
AS15412Flag Telecom UK LimitedUnclassifiedIPv4 IPv656
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv612
AS4637Telstra GlobalUnclassifiedIPv44
AS9304HGC Global Communications LimitedHostingIPv63

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.