AS53184 VERO S.A
🇧🇷Org handle: 330814
LACNICallocated
Announced Prefixes (BGP)
118total
105 IPv413 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)49,920
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.6×10²⁹
Announced Prefixes
(BGP)118|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 |
1-10 of 118
1 / 12
All 118 announced prefixes of AS53184 →
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS53184 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS53184 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 AS53184 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/53184Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/53184" | jq