asn.dev

Observed topology

AS150289 SUNYZ-AS-AP Sun Yanzheng

Unclassified APNIC NSP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS150289: 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
AS6939Hurricane Electric LLCTransitIPv6134
AS7720Skywolf Technology LLCUnclassifiedIPv671
AS34927iFog GmbHHostingIPv642
AS27523Kawaii Networks LLCUnclassifiedIPv634
AS17433Hytron Network Services LimitedResidentialIPv619
AS20473The Constant Company, LLCHostingIPv64
AS24482SG.GSHostingIPv64
AS205794JINZE YANGUnclassifiedIPv63
AS9002RETN LimitedUnclassifiedIPv62
AS357084b42 UGUnclassifiedIPv62

All 12 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6134
AS7720Skywolf Technology LLCUnclassifiedIPv671
AS34927iFog GmbHHostingIPv642
AS27523Kawaii Networks LLCUnclassifiedIPv634
AS17433Hytron Network Services LimitedResidentialIPv619
AS20473The Constant Company, LLCHostingIPv64
AS24482SG.GSHostingIPv64
AS205794JINZE YANGUnclassifiedIPv63
AS9002RETN LimitedUnclassifiedIPv62
AS357084b42 UGUnclassifiedIPv62

All 12 adjacent →

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.