AS210111 netcraftsolutions Netcraft Solutions s.r.o.
🇨🇿Org handle: ORG-NSS35-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
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
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 2 announced prefixes, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-12 | |
| Valid | RIPE | 2026-10-12 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.88.72.0/22 | 🇨🇿 CZ | RIPENCC | allocated |
| 2a0d:b0c0::/29 | 🇨🇿 CZ | RIPENCC | allocated |
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 AS210111 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/210111Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/210111" | jq