AS266260 ITOP TELECOM LTDA - ME
🇧🇷Org handle: 276451
LACNICallocated
Announced Prefixes (BGP)
14total
7 IPv47 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)14|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | Other IRR | 2026-10-10 | |
| No ROA | - | 2026-10-10 | |
| No ROA | - | 2026-10-10 |
1-10 of 14
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 192.140.88.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:3d34::/32 | 🇧🇷 BR | LACNIC | allocated |
All 14 announced prefixes of AS266260 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS266260 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 AS266260 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/266260Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/266260" | jq