asn.dev

Routing security

AS50891 MOVIEMENT-ND

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 AS50891 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
178.22.184.0/21No ROAIRR52
194.247.28.0/23No ROAIRR52

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS50891 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

3 objects · 1 not announced

Route objects naming AS50891 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
178.22.186.0/23RIPESupportMNT-NORDATA2010-09-13Not announced
178.22.184.0/21RIPEASMNT-NORDATA2016-02-12Announced
194.247.28.0/23RIPE—MOVIEMENT-MNT2017-01-05Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-FASTWEBRIPELists AS50891 as a direct member
AS-INFOSTRADARIPELists AS50891 as a direct member
AS-NICEBLUERIPELists AS50891 as a direct member
AS-NTRNET-SETRIPELists AS50891 as a direct member
AS-RETELITRIPELists AS50891 as a direct member
AS-WINDTRERIPELists AS50891 as a direct member

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