AS201922 amccomp-turany mapnet IT services s.r.o.
🇨🇿Org handle: ORG-MISS3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 10/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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a02:6c20:3::/48 | 🇨🇿 CZ | RIPE | assigned |
All 3 announced prefixes of AS201922 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201922 hands its own prefixes to: transit providers, or peers at an exchange.
- AS207167Amccomp Master Brno Mapnet IT Services S.R.O3
Downstreams (1)
Networks whose own prefixes AS201922 passes on: usually its customers.
- AS208143Amccomp Unin Mapnet IT Services S.R.O2
Other adjacent networks (1)
Adjacent to AS201922 in the transit part of AS paths: peers, providers or customers.
- AS16019VODAFONE CZ Vodafone Czech Republic A.S2
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 AS201922 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/201922Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201922" | jq