AS57175 SAKURA-AS Tianhai InfoTech Limited

🇭🇰

Org handle: ORG-THIT2-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

2total

0 IPv42 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)0

IPv6 Addresses

Allocated (RIR)4.9×10²⁷

Announced (BGP)2×10²⁵

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇭🇰 HK

RIR

RIPE NCC

Status

allocated

Allocated

2023-02-22

Announced Prefixes

(BGP)2

Prefix	RPKI	IRR	Last Seen
2a13:1802:c001::/48	Valid	-	2026-10-10
2a13:1802:c010::/44	No ROA	-	2026-10-10

Allocated Prefixes

(RIR)2

Prefix	Country	RIR	Status
2a13:1802:c000::/36	🇭🇰 HK	RIPE	assigned
2a13:1802:c001::/48	🇮🇪 IE	RIPE	assigned

All 2 announced prefixes of AS57175 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS4842Tianhai InfoTech1
AS16509Amazon.Com1

Transfer History

Registry transfers of AS57175 between organisations.

AS57175Transfer · 2025-03-07
SAKURA LTD.
RIPE NCC
→
Tianhai InfoTech Limited
RIPE NCC

Date	Resource	From	To	Type
2025-03-07	AS57175	SAKURA LTD. RIPE NCC	Tianhai InfoTech Limited RIPE NCC	Transfer

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

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 AS57175 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/57175

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

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