subnet.im

AS64013Yancy Limited

Hong Kong SAR ChinaRegistryAPNIC

As of 10th November 2026, AS64013 (Yancy Limited), a network registered in Hong Kong SAR China with APNIC, originates 7 IPv4 prefixes covering 1.8k addresses. By IPv4 address space that makes it the 30,392nd-largest of the 80,733 networks we see originating IPv4, and the 367th-largest of 760 in Hong Kong SAR China. It is seen behind 2 upstream networks, most often AS13335 (Cloudflare, Inc.) and AS138415 (Yancy Limited). Every one of its announcements has a valid RPKI ROA, and none are RPKI-invalid. 86% of its routes reach at least 90% of full-feed peers, and 1 prefix is also originated by another network.

At a glance

IPv4 prefixes

7

IPv6 prefixes

0

IPv4 addresses

1.8k

IPv6 /64s

0

Upstream graph

The networks AS64013 is seen behind, one and two hops out, drawn from real AS paths.

AS64013Toward the internet core
Upstream graph for AS64013: 6 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS64013Yancy LimitedThis networkAS13335Cloudflare, Inc.AS138415Yancy LimitedAS2914NTT America, Inc.AS3356Lumen (Level 3)AS3491PCCW Global (HK) …AS17476CloudRadium (HK) …

Networks observed one and two hops upstream of AS64013 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

4

adjacent networks

Upstreams
250%
Peers
250%
Downstreams
00%

Networks carrying this one's traffic toward the rest of the internet.

Upstreams of AS64013
NetworkCountryRelationshipPathsVantage pts
AS13335Cloudflare, Inc.USPeer38176
AS138415Yancy LimitedHKPeer7575

Prefixes

The largest blocks AS64013 originates, widest first.

Largest prefixes originated by AS64013
PrefixAddressesVisibility
23.235.165.0/2425675/76
156.234.168.0/2425676/76
156.234.170.0/2425676/76
156.247.32.0/2425676/76
156.247.33.0/242561/76
156.247.43.0/2425676/76
156.247.51.0/2425676/76

Routing health

How AS64013's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.

RPKI origin validation

  • Valid100.0%7
  • Invalid0.0%0
  • No ROA0.0%0

Propagation

  • Globally propagated90% of full-feed peers or more85.7%6
  • Partially propagated40% to 90%0.0%0
  • Seen by few peersUnder 40%14.3%1

Prefix sizes

IPv4 — 7 prefixes

Recent changes

Announcements that started or stopped since 12th Oct 2026.

  • Announced156.247.33.0/2429th Oct 2026
  • Announced23.235.165.0/2429th Oct 2026
  • Withdrawn23.235.165.0/2427th Oct 2026
  • Withdrawn156.234.133.0/2413th Oct 2026
  • Withdrawn156.234.175.0/2413th Oct 2026
  • Withdrawn156.234.211.0/2413th Oct 2026
  • Withdrawn156.234.62.0/2413th Oct 2026
  • Withdrawn156.234.95.0/2413th Oct 2026
  • Withdrawn156.247.33.0/2413th Oct 2026
  • Withdrawn156.247.34.0/2413th Oct 2026
  • Withdrawn156.247.35.0/2413th Oct 2026
  • Withdrawn23.235.164.0/2413th Oct 2026

11 announced and 10 withdrawn in all; the most recent are shown.

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.