RPKI check

Validate the ROA authorisation between a Prefix and Origin ASN. Leave ASN empty to use the currently observed BGP origin.

2a0e:ec00::/32

ValidIPv6

Checked Prefix

RPKI validates route-origin authorisation only. It does not validate AS_PATH, network ownership or reachability, and no ROA does not mean a route is malicious.

Checked at11/8/2026, 02:44:50CHA.LA route-origin snapshot

Prefix profile BGP routes BGP history

Route Prefix2a0e:ec00::/32Observed in local BGP

Current origins1AS209968

Validated origins1AS209968

ROA evidence3Covering this Prefix

Checked OriginAS209968

Valid

Validation basis: A covering ROA authorises this Origin and its maxLength permits the current prefix length.
Validator: RPKI validator
Snapshot time: 11/8/2026, 02:06:16
Data state: Live refresh

Authorisations covering this route

3 records

Checked ASN	ROA authorised ASN	ROA Prefix	maxLength	Result
AS209968	AS209968	2a0e:ec00::/30	/48	Valid
AS209968	AS52042	2a0e:ec00::/30	/48	ASN mismatch
AS209968	AS56849	2a0e:ec00::/30	/48	ASN mismatch

CHA.LA RPKI validation snapshotValidation is served from CHA.LA's normalized route-origin snapshots.CHA.LA route-origin snapshot