AS204115 Pro0101 Khaleel Abu Kaff
🇮🇱Org handle: ORG-KK248-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 20/100 · Low riskRPKI ROA coverage
66.7%
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
- 33% of announced prefixes (1 of 3) have no valid ROA
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
62.106.84.0/24MOAS | Valid | RIPE | 2026-10-26 |
| Valid | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 201.3.123.0/24 | 🇮🇱 IL | RIPE | assigned |
| 2a0f:6dc0::/29 | 🇮🇱 IL | RIPENCC | allocated |
All 3 announced prefixes of AS204115 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS204115 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8551BEZEQ INTERNATIONAL Bezeq International3
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 AS204115 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/204115Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/204115" | jq