AS208365 shamstelecom Shams Telecom Networks and Internet Service Ltd
🇮🇶Org handle: ORG-STNA3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
7total
7 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)1,792
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.223.186.0/24 | 🇮🇶 IQ | RIPENCC | allocated |
| 45.151.76.0/22 | 🇮🇶 IQ | RIPENCC | allocated |
| 81.22.32.0/22 | 🇮🇶 IQ | RIPENCC | allocated |
| 2a0e:d840::/29 | 🇮🇶 IQ | RIPENCC | allocated |
All 7 announced prefixes of AS208365 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS208365 hands its own prefixes to: transit providers, or peers at an exchange.
- AS203214HulumTele Hulum Almustakbal Company For Communication Engineering And Services7
Downstreams (1)
Networks whose own prefixes AS208365 passes on: usually its customers.
- AS203257Nexus Layth Zuhair Zahid1
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 AS208365 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/208365Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/208365" | jq