AS201156 obiz offek h&o ltd
🇮🇱Org handle: ORG-OHL6-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Routing hygiene
Score 40/100 · Medium riskRPKI ROA coverage
0%
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
- 100% of announced prefixes (3 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-12). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 | |
| No ROA | - | 2026-10-12 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.83.220.0/22 | 🇮🇱 IL | RIPENCC | allocated |
| 185.83.222.0/24 | 🇮🇱 IL | RIPE | assigned |
| 2a05:9e00::/29 | 🇮🇱 IL | RIPENCC | allocated |
All 3 announced prefixes of AS201156 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201156 hands its own prefixes to: transit providers, or peers at an exchange.
- AS1680Cellcom Fixed Line Communication L.P3
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 AS201156 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/201156Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201156" | jq