AS199018 ASXKRME Xkrme Network LLC
🇺🇸Org handle: ORG-XNL2-RIPE
OCITOKEN::199018:f521310840098e2a9bbcd2855a2c3f6242c3e2f9a4caa877249c7218a9353d54
RIPE NCCallocated
Announced Prefixes (BGP)
16total
0 IPv416 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)1.1×10²⁷
Announced (BGP)2.3×10²⁶
Announced Prefixes
(BGP)16|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
1-10 of 16
1 / 2
Allocated Prefixes
(RIR)15Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0f:1cc5:300::/40 | 🇺🇸 US | RIPE | assigned |
| 2a0f:1cc5:300::/44 | 🇺🇸 US | RIPE | assigned |
| 2a0f:1cc5:310::/46 | 🇹🇼 TW | RIPE | assigned |
| 2a0f:1cc5:318::/46 | 🇨🇳 CN | RIPE | assigned |
| 2a0f:1cc5:31c::/46 | 🇨🇳 CN | RIPE | assigned |
| 2a0f:1cc5:320::/44 | 🇯🇵 JP | RIPE | assigned |
| 2a0f:1cc5:330::/44 | 🇸🇬 SG | RIPE | assigned |
| 2a0f:1cc5:350::/44 | 🇯🇵 JP | RIPE | assigned |
| 2a0f:1cc5:360::/44 | 🇦🇺 AU | RIPE | assigned |
| 2a14:67c1:900::/40 | 🇭🇰 HK | RIPE | assigned |
1-10 of 15
1 / 2
All 16 announced prefixes of AS199018 →
BGP Neighbours
(seen in AS paths)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 AS199018 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/199018Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/199018" | jq