asn.dev

Routing security

AS216150 NITRIN

Unclassified RIPE

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
191.217.214.0/24RPKI validNo IRR53
89.125.226.0/24RPKI validIRR53
217.60.24.0/24RPKI validIRR53

RPKI · ROAs

Route origin authorisations

4 ROAs

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

PrefixMax lengthTrust anchor
89.125.226.0/24/24RIPENCC
191.217.214.0/24/24RIPENCC
217.60.24.0/24/24RIPENCC
2a0c:b641:b90::/44/128RIPENCC

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 AS216150 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
2a0c:b641:b90::/44RIPE—SERVPERSO-MNT2026-05-13Not announced
89.125.226.0/24RIPE—INTERLIR-MNT2026-09-01Announced
217.60.24.0/24RIPEEternityCloudLIR-AE-GOLDIP-1-MNT2026-05-18Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-RETN-ACTUAL-V4RIPELists AS216150 as a direct member
AS-TUBERIPELists AS216150 as a direct member
AS202413:AS-PRONKINRIPELists AS216150 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.