AS270013 AS270013 - J AND J SPA (INFOFRACTAL)
🇨🇱Org handle: 312794
LACNICallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Routing hygiene
Score 10/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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
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 | Other IRRRIPE | 2026-10-25 | |
| Valid | LACNICOther IRR | 2026-10-25 | |
| Valid | LACNIC | 2026-10-25 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 151.242.242.0/24 | 🇨🇱 CL | RIPE | assigned |
| 200.14.81.0/24 | 🇨🇱 CL | LACNIC | allocated |
| 2803:29e0::/32 | 🇨🇱 CL | LACNIC | allocated |
All 3 announced prefixes of AS270013 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS214675 | 🇯🇵Starlamp Hidenori Matsuo |
BGP Neighbours
(seen in AS paths)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/270013Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/270013" | jq