AS52511 IRONSERVERS E.I.R.L
🇨🇱Org handle: 240384
LACNICallocated
Announced Prefixes (BGP)
13total
6 IPv47 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)13|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | LACNICOther IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 | |
| No ROA | Other IRR | 2026-10-10 | |
| Valid | LACNIC | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 |
1-10 of 13
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 138.186.8.0/22 | 🇨🇱 CL | LACNIC | allocated |
| 2803:8240::/32 | 🇨🇱 CL | LACNIC | allocated |
All 13 announced prefixes of AS52511 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS52511 hands its own prefixes to: transit providers, or peers at an exchange.
- AS263702GRUPO ZGH SPA13
ASPA
No ASPA
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 AS52511 should publish an ASPA object
- IPv4 transfers in the LACNIC 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/52511Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/52511" | jq