AS271612 LOGO Telecom
🇧🇷Org handle: 321350
LACNICallocated
Announced Prefixes (BGP)
20total
10 IPv410 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)3,584
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)8.1×10²⁸
Announced Prefixes
(BGP)20|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| 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 | |
| No ROA | Other IRR | 2026-10-10 | |
| No ROA | Other IRR | 2026-10-10 | |
| No ROA | Other IRR | 2026-10-10 | |
| Valid | ARIN | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 |
1-10 of 20
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 179.63.92.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:7e40::/32 | 🇧🇷 BR | LACNIC | allocated |
All 20 announced prefixes of AS271612 →
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS271612 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS271612 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/271612Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/271612" | jq