AS63838 CT-HUNAN-HENGYANG-IDC Hengyang

🇨🇳

Org handle: A914EAE4

Hengyang

APNICallocated

Announced Prefixes (BGP)

28total

21 IPv47 IPv6

IPv4 Addresses

Allocated (RIR)1,280

Announced (BGP)55,040

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)1×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2014-10-15

Announced Prefixes

(BGP)28

Prefix	RPKI	IRR	Last Seen
113.219.128.0/18	Valid	-	2026-10-11
113.219.166.0/23	Valid	-	2026-10-11
113.219.170.0/23	Valid	-	2026-10-11
113.219.172.0/23	Valid	-	2026-10-11
113.219.174.0/23	Valid	-	2026-10-11
113.219.176.0/23	Valid	-	2026-10-11
175.4.0.0/18	Valid	-	2026-10-11
175.4.24.0/22	Valid	-	2026-10-11
175.6.192.0/20	Valid	-	2026-10-11
175.6.208.0/21	Valid	-	2026-10-11

1-10 of 28

1 / 3

(RIR)2

Prefix	Country	RIR	Status
203.56.216.0/24	🇨🇳 CN	APNIC	allocated
218.77.32.0/22	🇨🇳 CN	APNIC	assigned

(seen in AS paths)

Networks AS63838 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS63838 should publish an ASPA object
IPv4 transfers in the APNIC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/63838" | jq