AS56430 CHROOT Chroot Network SRL
🇷🇴Org handle: ORG-CNS26-RIPE
Bucharest / ROMANIA, EU
RIPE NCCallocated
Announced Prefixes (BGP)
19total
13 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)4,608
Announced (BGP)4,608
IPv6 Addresses
Allocated (RIR)2.6×10³⁰
Announced (BGP)2.6×10³⁰
Routing hygiene
Score 3/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
4
diversity 73/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 19 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)19|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
1-10 of 19
1 / 2
Allocated Prefixes
(RIR)19Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.81.64.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 86.105.152.0/23 | 🇷🇴 RO | RIPENCC | allocated |
| 86.105.155.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 89.36.18.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 89.36.93.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 89.40.214.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 89.42.42.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 89.43.174.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 91.193.53.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 185.82.172.0/22 | 🇷🇴 RO | RIPENCC | allocated |
1-10 of 19
1 / 2
All 19 announced prefixes of AS56430 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS9053 | 🇨🇿VSHOSTING-CDN VSHosting s.r.o. |
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS56430 hands its own prefixes to: transit providers, or peers at an exchange.
Abuse Contact
+31205354444
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/56430Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56430" | jq