AS28161
LACNICreserved
Announced Prefixes (BGP)
2total
0 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.5×10²⁶
Routing hygiene
Score 90/100 · High riskRPKI ROA coverage
0%
2 prefixes RPKI invalid
IRR route objects
0%
2 prefixes registered for another origin
Hijack signals
2
2 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (2 of 2) have no valid ROA, 2 of them RPKI invalid
- Announces 2 prefixes that RPKI assigns to another network (possible hijack or misconfiguration)
- 100% of announced prefixes (2 of 2) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-20). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Invalid | - | 2026-10-25 | |
| Invalid | - | 2026-10-25 |
All 2 announced prefixes of AS28161 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS28161 hands its own prefixes to: transit providers, or peers at an exchange.
- AS61832DB3 SERVICOS DE TELECOMUNICACOES S.A2
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 AS28161 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/28161Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/28161" | jq