AS266185 Spin Telecomunicacoes
🇧🇷Org handle: 139684
LACNICallocated
Announced Prefixes (BGP)
7total
7 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-11 | |
| No ROA | Other IRR | 2026-10-11 | |
| No ROA | Other IRR | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | Other IRR | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.6.96.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:3c04::/32 | 🇧🇷 BR | LACNIC | allocated |
All 7 announced prefixes of AS266185 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS266185 hands its own prefixes to: transit providers, or peers at an exchange.
- AS11432Telium Telecomunicacoes Ltda7
Downstreams (2)
Networks whose own prefixes AS266185 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS266185 in the transit part of AS paths: peers, providers or customers.
- AS40850UPIX NETWORKS INTERNATIONAL3
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 AS266185 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/266185Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/266185" | jq