AS21485 FOILHAT IP Excess AB
🇸🇪Org handle: ORG-IEA17-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
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-27). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-28 | |
| Valid | RIPE | 2026-10-28 | |
| Valid | RIPE | 2026-10-28 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.231.153.0/24 | 🇸🇪 SE | RIPENCC | assigned |
| 2001:67c:15ec::/48 | 🇸🇪 SE | RIPENCC | assigned |
| 2a0a:3500::/32 | 🇸🇪 SE | RIPE | assigned |
All 3 announced prefixes of AS21485 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS214503 | 🇸🇪QUXLABS QuxLabs AB |
BGP Neighbours
(seen in AS paths)Transfer History
Registry transfers of AS21485 between organisations.
- AS21485Transfer ·
- AS21485Transfer ·
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/21485Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/21485" | jq