AS203900 faraertebatmabna Fara Ertebat Mabna PJS
🇮🇷Org handle: ORG-FEMP1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
109.122.241.0/24MOAS | Valid | RIPE | 2026-10-11 |
109.122.242.0/24MOAS | Valid | RIPE | 2026-10-11 |
109.122.243.0/24MOAS | Valid | RIPE | 2026-10-11 |
193.104.29.0/24MOAS | Invalid | - | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 109.122.242.0/24 | 🇮🇷 IR | RIPE | assigned |
| 109.122.243.0/24 | 🇮🇷 IR | RIPE | assigned |
| 193.104.29.0/24 | 🇮🇷 IR | RIPENCC | allocated |
All 4 announced prefixes of AS203900 →
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 AS203900 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/203900Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203900" | jq