asn.dev

Observed topology

AS133527 HTIL-AS-AP - HuaBo Technology International Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS133527: 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
AS2914NTT America, Inc.TransitIPv4 IPv6125
AS10103HK Broadband Network Ltd.ResidentialIPv4 IPv696
AS174Cogent Communications, LLCTransitIPv4 IPv680
AS6939Hurricane Electric LLCTransitIPv424
AS9002RETN LimitedUnclassifiedIPv44
AS24482SG.GSHostingIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63620ShenZhen HuaBo Technology Develop Co., Ltd.UnclassifiedIPv4 IPv6154

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS10103HK Broadband Network Ltd.ResidentialIPv4 IPv6166
AS2914NTT America, Inc.TransitIPv4 IPv6154
AS63620ShenZhen HuaBo Technology Develop Co., Ltd.UnclassifiedIPv4 IPv6154
AS174Cogent Communications, LLCTransitIPv4 IPv6115
AS6939Hurricane Electric LLCTransitIPv440
AS9002RETN LimitedUnclassifiedIPv46
AS24482SG.GSHostingIPv4 IPv66

Provenance

Where this comes from

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