AS273517 RUPI Telecom
🇧🇷Org handle: 345890
LACNICallocated
Announced Prefixes (BGP)
13total
8 IPv45 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)4,608
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)1.5×10²⁹
Announced Prefixes
(BGP)13|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
45.161.72.0/22MOAS | Valid | - | 2026-10-11 |
45.161.72.0/23MOAS | Valid | - | 2026-10-11 |
| Valid | - | 2026-10-11 | |
45.161.74.0/23MOAS | Valid | - | 2026-10-11 |
| Valid | - | 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 |
1-10 of 13
1 / 2
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 168.0.192.0/22 | 🇧🇷 BR | LACNIC | allocated |
| 2804:8fdc::/32 | 🇧🇷 BR | LACNIC | allocated |
All 13 announced prefixes of AS273517 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS273517 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (8)
Networks whose own prefixes AS273517 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 AS273517 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/273517Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/273517" | jq