AS205232 EvilNET Felix Alcantara
🇺🇸Org handle: ORG-FA1198-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
0 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)9.2×10²⁶
Announced (BGP)9.2×10²⁶
Routing hygiene
Score 3/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
3
diversity 67/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 3 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0a:6040:9c00::/40 | 🇺🇸 US | RIPE | assigned |
| 2a0a:6040:a000::/40 | 🇺🇸 US | RIPE | assigned |
| 2a0a:6040:f800::/40 | 🇺🇸 US | RIPE | assigned |
ASPA
No ASPA
Abuse Contact
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 AS205232 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/205232Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205232" | jq