AS212250 HORIZON-SCOPE Horizon Scope Mobile Telecom WLL
🇮🇶Org handle: ORG-HSMT1-RIPE
HORIZON-SCOPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
0 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0b:1880::/48 | 🇮🇶 IQ | RIPE | assigned |
| 2a0b:1880:ffff::/48 | 🇮🇶 IQ | RIPE | assigned |
All 2 announced prefixes of AS212250 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS212250 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS212250 passes on: usually its customers.
Other adjacent networks (7)
Adjacent to AS212250 in the transit part of AS paths: peers, providers or customers.
ASPA
No ASPA
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
- ASPA explainedWhy AS212250 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/212250Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/212250" | jq