AS263611 ZUM TELECOM LTDA- ME
🇧🇷Org handle: 149729
LACNICallocated
Announced Prefixes (BGP)
24total
21 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)4,096
Announced (BGP)9,472
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)6.9×10²⁸
Announced Prefixes
(BGP)24|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 |
1-10 of 24
1 / 3
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 179.124.16.0/20 | 🇧🇷 BR | LACNIC | allocated |
| 2804:ff8::/32 | 🇧🇷 BR | LACNIC | allocated |
All 24 announced prefixes of AS263611 →
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS263611 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 AS263611 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/263611Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/263611" | jq