AS203534 On1x Erik Omarov
🇰🇿Org handle: ORG-EO82-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 6/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 38/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 4 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
89.144.34.0/24MOAS | Valid | RIPE | 2026-10-26 |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.231.223.0/24 | 🇩🇪 DE | RIPE | assigned |
| 2a0b:4e07:be::/48 | 🇩🇪 DE | RIPE | assigned |
| 2a0d:d940:2009::/48 | 🇷🇺 RU | RIPE | assigned |
All 4 announced prefixes of AS203534 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS203534 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS203534 passes on: usually its customers.
- AS209057LICENNETWORK Vyacheslav Golubtsov2
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 AS203534 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/203534Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203534" | jq