AS203118 EZERDI Ezerdi LLC
🇷🇺Org handle: ORG-EL497-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 84.38.2.0/24 | 🇷🇺 RU | RIPENCC | assigned |
| 194.165.57.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 2001:67c:e08::/48 | 🇷🇺 RU | RIPENCC | assigned |
All 3 announced prefixes of AS203118 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS203118 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS203118 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS203118 in the transit part of AS paths: peers, providers or customers.
- AS20764RASCOM CJSC RASCOM1
Transfer History
Registry transfers of AS203118 between organisations.
- AS203118Transfer ·
- AS203118M&A ·
- AS203118Transfer ·
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 AS203118 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/203118Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203118" | jq