AS214111 TAPHIP TapHip Limited
🇭🇰Org handle: ORG-TL934-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)1.9×10²⁵
Announced (BGP)1.9×10²⁵
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | Other IRR | 2026-10-11 | |
| No ROA | Other IRR | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.208.109.0/24 | 🇺🇸 US | RIPENCC | allocated |
| 2a14:67c1:a170::/44 | 🇭🇰 HK | RIPE | assigned |
All 4 announced prefixes of AS214111 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS214111 hands its own prefixes to: transit providers, or peers at an exchange.
- AS932XNNET4
ASPA
No ASPA
Abuse Contact
External Links
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 AS214111 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 https://api.ipctl.io/v1/asn/214111Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214111" | jq