asn.dev

Observed topology

AS47272 HYEHOST - HYEHOST LLC

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47272: 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
AS204208Peravix Group LTDUnclassifiedIPv4 IPv62,422

Transit

Downstream networks

All 81

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

ASNetworkTypeFamiliesPaths seen
AS219412Lewis BrownUnclassifiedIPv6305
AS210738Peng ChenUnclassifiedIPv6269
AS212708Victor Lourme trading as PCKT.SHUnclassifiedIPv6256
AS47509Wai-Wah TangUnclassifiedIPv6222
AS218839ZONEK TELECOM LTDUnclassifiedIPv6218
AS218890Yuri Systems LLCUnclassifiedIPv6185
AS23026SETEC ASTRONOMY INCUnclassifiedIPv6136
AS214420Conor LewisUnclassifiedIPv6108
AS218939ahmad abuhatabUnclassifiedIPv6108
AS136535Yang MengqiUnclassifiedIPv6105

All 81 downstreams →

Adjacency

Adjacent networks

All 82

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

ASNetworkTypeFamiliesPaths seen
AS204208Peravix Group LTDUnclassifiedIPv4 IPv66,954
AS219412Lewis BrownUnclassifiedIPv6305
AS218839ZONEK TELECOM LTDUnclassifiedIPv6292
AS210738Peng ChenUnclassifiedIPv6269
AS212708Victor Lourme trading as PCKT.SHUnclassifiedIPv6256
AS47509Wai-Wah TangUnclassifiedIPv6222
AS218890Yuri Systems LLCUnclassifiedIPv6185
AS218776FULLFIBER LTDUnclassifiedIPv6146
AS23026SETEC ASTRONOMY INCUnclassifiedIPv6136
AS214420Conor LewisUnclassifiedIPv6108

All 82 adjacent →

Provenance

Where this comes from

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