asn.dev

Routing security

AS209752

Unclassified RIPE

RPKI valid — 0 of 0 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered — 0 missing · 0 other origin
ROAs 2 authorising this AS

Announcements

What this network originates

0 observed

Every prefix observed with AS209752 as its origin, checked against RPKI and the IRR. Problems sort first.

No announcements from this network were observed in the routing snapshot.

RPKI · ROAs

Route origin authorisations

2 ROAs

Signed statements by address holders that AS209752 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
77.69.248.0/24/24RIPENCC
2001:1a40:10::/64/64RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

2 objects · 2 not announced

Route objects naming AS209752 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

PrefixSourceDescriptionMaintainerChangedRouting
77.69.248.0/24RIPE—AS5416-MNT2021-11-09Not announced
2001:1a40:10::/64RIPE—AS5416-MNT2021-11-09Not announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS209752 directly show who expects to carry it.

AS-setWhereRelationship
AS-VIVA-BHRIPELists AS209752 as a direct member

RPKI from rpki-client, validated 2026-10-16 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-16. Cross-check on bgp.he.net.