AS203888 USKVM - USKVM LLC
πΊπΈARINassignedASPA Published
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.9Γ10Β²β΅
Announced (BGP)1.9Γ10Β²β΅
Routing hygiene
Score 20/100 Β· Low riskRPKI ROA coverage
50%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 50/100
- 50% of announced prefixes (1 of 2) have no valid ROA
Based on 2 announced prefixes, updated daily (2026-10-23). How the score works Β· RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | Other IRR | 2026-10-26 | |
| Valid | Other IRRRIPE | 2026-10-26 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0c:9a40:84c0::/44 | π©πͺ DE | RIPE | assigned |
All 2 announced prefixes of AS203888 β
BGP Neighbours
(seen in AS paths)Transfer History
Registry transfers of AS203888 between organisations.
- AS203888inter-RIRTransfer Β·
- AS203888Transfer Β·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS203888inter-RIR | Yu Li | USKVM LLC | Transfer | |
| AS203888 | Ing. Petr Martincik | CadcaNet plus, s.r.o. | Transfer |
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 ARIN 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/203888Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203888" | jq