AS269139 AN TELECOM
🇧🇷Org handle: 250615
LACNICallocated
Announced Prefixes (BGP)
8total
7 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)8|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | - | 2026-10-10 | |
| Valid | Other IRR | 2026-10-10 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.180.84.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:6000::/32 | 🇧🇷 BR | LACNIC | allocated |
All 8 announced prefixes of AS269139 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS269139 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS269139 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS269139 in the transit part of AS paths: peers, providers or customers.
- AS268199Rios Network1
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 AS269139 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/269139Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/269139" | jq