asn.dev

Observed topology

AS133929 TWOWINCOLIMITED-AS-AP - TWOWIN CO., LIMITED

Hosting APNIC Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133929: 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
AS13335Cloudflare, Inc.HostingIPv42,039
AS6939Hurricane Electric LLCTransitIPv4 IPv61,110
AS21859Zenlayer IncHostingIPv4636
AS135391AOFEI DATA INTERNATIONAL COMPANY LIMITEDHostingIPv4 IPv6549
AS8220COLT Technology Services Group LimitedHostingIPv4115
AS9304HGC Global Communications LimitedHostingIPv459
AS9729iAdvantage LimitedHostingIPv459
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS133107FNETLINK CO .,LIMITEDUnclassifiedIPv4990

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv42,039
AS6939Hurricane Electric LLCTransitIPv4 IPv61,343
AS135391AOFEI DATA INTERNATIONAL COMPANY LIMITEDHostingIPv4 IPv61,121
AS133107FNETLINK CO .,LIMITEDUnclassifiedIPv4990
AS21859Zenlayer IncHostingIPv4761
AS8220COLT Technology Services Group LimitedHostingIPv4126
AS9304HGC Global Communications LimitedHostingIPv4100
AS9729iAdvantage LimitedHostingIPv459
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv64

Provenance

Where this comes from

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