AS200213 TAPCOM TAPCOM TECHNOLOGY LIMITED
ππ°Org handle: ORG-TTL68-RIPE
-----BEGIN TOKEN-----98117f46c54308b145a57bfd0665611c53903e9fce0ccbf910604071ce8e83e5d19ff3970b4d23832673b7e4adfc10fd587aab2b09bb3864e8f836b33eebd90c-----END TOKEN-----
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)2.4Γ10Β²β΄
Announced (BGP)1.2Γ10Β²β΄
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
ππ° HKRIR
RIPE NCCStatus
allocated
Allocated
2026-03-10
Routing hygiene
Score 18/100 Β· Low riskRPKI ROA coverage
83.3%
1 prefix RPKI invalid
IRR route objects
83.3%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 44/100
- 17% of announced prefixes (1 of 6) have no valid ROA, 1 of them RPKI invalid
- 17% of announced prefixes (1 of 6) have no IRR route object for this ASN
Based on 6 announced prefixes, updated daily (2026-10-24). How the score works Β· RPKI explained
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | - | |
| Valid | Other IRRRIPE | - | |
82.24.25.0/24MOAS | Invalid | - | - |
| Valid | Other IRR | - | |
| Valid | Other IRRRIPE | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.236.196.0/24 | ππ° HK | RIPE | assigned |
| 78.105.154.0/24 | πͺπΊ EU | RIPE | assigned |
| 82.24.25.0/24 | ππ° HK | RIPE | assigned |
| 154.193.128.0/24 | π©πͺ DE | AFRINIC | assigned |
| 154.222.79.0/24 | π©πͺ DE | AFRINIC | assigned |
| 177.29.248.0/24 | π©πͺ DE | RIPE | assigned |
| 2a0c:9a40:8e90::/48 | π©πͺ DE | RIPE | assigned |
| 2a13:9500:155::/48 | ππ° HK | RIPE | assigned |
All 6 announced prefixes of AS200213 β
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS62610 | πΊπΈZEN-DPS - Zenlayer Inc |
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/200213Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200213" | jq