asn.dev

Routing security

AS208661

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 5 authorising this AS

Announcements

What this network originates

0 observed

Every prefix observed with AS208661 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

5 ROAs

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

PrefixMax lengthTrust anchor
2a0c:b6c3::/32/32RIPENCC
2a0c:b6c4::/32/32RIPENCC
2a0c:b6c5::/32/32RIPENCC
2a0c:b6c6::/32/32RIPENCC
2a0c:b6c7::/32/32RIPENCC

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

5 objects · 5 not announced

Route objects naming AS208661 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
45.90.84.0/22RIPE—MNT-PS-NETZONE-12019-07-09Not announced
2a0c:b6c3::/32RIPE—MNT-PS-NETZONE-12022-02-03Not announced
2a0c:b6c4::/32RIPE—MNT-PS-NETZONE-12022-02-03Not announced
2a0c:b6c5::/32RIPE—MNT-PS-NETZONE-12022-02-03Not announced
2a0c:b6c6::/32RIPE—MNT-PS-NETZONE-12022-02-03Not announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-PALTELRIPELists AS208661 as a direct member
AS-PSIXRIPELists AS208661 as a direct member

RPKI from rpki-client, validated 2026-11-03 13:02 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-03. Cross-check on bgp.he.net.