AS219394 Red-Seek-Limited Red Seek Limited
🇭🇰Org handle: ORG-RSL46-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Routing hygiene
Score 95/100 · High riskRPKI ROA coverage
0%
4 prefixes RPKI invalid
IRR route objects
0%
4 prefixes registered for another origin
Hijack signals
6
4 announced against others' ROAs, 2 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (4 of 4) have no valid ROA, 4 of them RPKI invalid
- Announces 4 prefixes that RPKI assigns to another network (possible hijack or misconfiguration)
- 100% of announced prefixes (4 of 4) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
- 2 prefixes of this ASN announced by another network against its ROAs
Based on 4 announced prefixes, updated daily (2026-10-20). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
82.152.60.0/24MOAS | Invalid | - | 2026-10-20 |
82.152.69.0/24MOAS | Invalid | - | 2026-10-20 |
87.82.213.0/24MOAS | Invalid | - | 2026-10-20 |
87.84.218.0/24MOAS | Invalid | - | 2026-10-20 |
All 4 announced prefixes of AS219394 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS219394 hands its own prefixes to: transit providers, or peers at an exchange.
- AS62610Zenlayer4
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 AS219394 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/219394Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/219394" | jq