AS219267 BO-AS Bilotserkovets Oleksandr
πΊπ¦Org handle: ORG-BO107-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
1total
0 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.2Γ10Β²β΄
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
πΊπ¦ UARIR
RIPE NCCStatus
allocated
Allocated
2026-07-07
Routing hygiene
Score 33/100 Β· Medium riskRPKI ROA coverage
50%
no RPKI invalid prefixes
IRR route objects
50%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 50% of announced prefixes (1 of 2) have no valid ROA
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
Based on 2 announced prefixes, updated daily (2026-10-22). How the score works Β· RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-26 |
All 1 announced prefix of AS219267 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS219267 hands its own prefixes to: transit providers, or peers at an exchange.
- AS201279AWAS Loginov Vladislav2
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/219267Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/219267" | jq