asn.dev

Routing security

AS209515 MOHGROUP-AS

Unclassified RIPE

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

Announcements

What this network originates

2 observed

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

PrefixRPKIIRRVantage points
91.132.16.0/22No ROAIRR52
91.132.17.0/24No ROAIRR57

RPKI · ROAs

Route origin authorisations

0 ROAs

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

No ROA names this AS as an authorised origin.

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 · 0 not announced

Route objects naming AS209515 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
91.132.16.0/22RIPE—MNT-GR-MOH-12019-04-22Announced
91.132.17.0/24RIPE—MNT-GR-MOH-12024-01-16Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-DRTRIPELists AS209515 as a direct member
AS-HURRICANERADBLists AS209515 as a direct member
AS-OTENETRIPELists AS209515 as a direct member
AS-OTENET-TESTRIPELists AS209515 as a direct member
AS-TRANSROUTE-SPECRIPELists AS209515 as a direct member
AS-UDOSRADBLists AS209515 as a direct member
AS56910:AS-CUSTOMERSRIPELists AS209515 as a direct member

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