AS268737 CONECT TELECOM COMUNICACAO LTDA
🇧🇷Org handle: 294719
LACNICallocated
Announced Prefixes (BGP)
6total
3 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)1.5×10²⁹
Announced Prefixes
(BGP)6|
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 | - | 2026-10-11 | |
| Valid | - | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.171.252.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:59f8::/32 | 🇧🇷 BR | LACNIC | allocated |
All 6 announced prefixes of AS268737 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS268737 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS268737 passes on: usually its customers.
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 AS268737 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/268737Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/268737" | jq