AS61922 CNX TELECOM
🇧🇷Org handle: 193785
LACNICallocated
Announced Prefixes (BGP)
6total
4 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)9.9×10²⁸
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | Other IRR | 2026-10-11 | |
| Valid | - | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 200.7.8.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:1830::/32 | 🇧🇷 BR | LACNIC | allocated |
All 6 announced prefixes of AS61922 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS274506 | 🇧🇷Netcom servicos de telecomunicacoes |
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS61922 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS61922 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS61922 in the transit part of AS paths: peers, providers or customers.
- AS16735ALGAR TELECOM15
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/61922Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/61922" | jq