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