AS16116 Pelephone Communications Ltd.
🇮🇱Org handle: ORG-PCL4-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
210total
88 IPv4122 IPv6
IPv4 Addresses
Allocated (RIR)44,544
Announced (BGP)48,896
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)2.2×10²⁶
Prefix Limit (IPv4)
200
Prefix Limit (IPv6)
500
Country
🇮🇱 ILRIR
RIPE NCCStatus
allocated
Allocated
2000-12-27
Routing hygiene
Score 28/100 · Medium riskRPKI ROA coverage
38.9%
no RPKI invalid prefixes
IRR route objects
99.5%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 6/100
- 61% of announced prefixes (129 of 211) have no valid ROA
- Routes concentrated on one upstream (97% of routes)
Based on 211 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Listed on the threat map (2026-10-21)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)210|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | - | 2026-10-26 |
1-10 of 210
1 / 21
Allocated Prefixes
(RIR)49Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.25.32.0/21 | 🇮🇱 IL | RIPENCC | allocated |
| 46.19.80.0/21 | 🇮🇱 IL | RIPENCC | allocated |
| 46.19.83.0/24 | 🇮🇱 IL | RIPE | assigned |
| 46.19.86.0/24 | 🇮🇱 IL | RIPE | assigned |
| 62.112.0.0/22 | 🇮🇱 IL | RIPENCC | allocated |
| 64.226.196.0/22 | 🇮🇱 IL | RIPENCC | allocated |
| 84.111.136.0/21 | 🇮🇱 IL | RIPENCC | allocated |
| 84.111.208.0/21 | 🇮🇱 IL | RIPENCC | allocated |
| 85.159.160.0/21 | 🇮🇱 IL | RIPENCC | allocated |
| 85.159.164.0/24 | 🇮🇱 IL | RIPE | assigned |
1-10 of 49
1 / 5
All 210 announced prefixes of AS16116 →
BGP Neighbours
(seen in AS paths)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 AS16116 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/16116Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16116" | jq