asn.dev

Routing security

AS214589 SMOEN-AS

Unclassified RIPE

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

Announcements

What this network originates

7 observed

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

PrefixRPKIIRRVantage points
149.232.236.0/24No ROAIRR covering52
149.232.237.0/24No ROAIRR covering52
149.232.238.0/24No ROAIRR covering52
195.189.36.0/24RPKI validIRR covering52
195.189.37.0/24RPKI validIRR covering52
195.189.38.0/24RPKI validIRR covering52
195.189.39.0/24RPKI validIRR covering52

RPKI · ROAs

Route origin authorisations

1 ROAs

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

PrefixMax lengthTrust anchor
195.189.36.0/22/24RIPENCC

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

Route objects naming AS214589 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
149.232.236.0/22RIPE—JAGUAR-MNT2026-09-28Not announced
195.189.36.0/22RIPE—JAGUAR-MNT2024-07-02Not announced
2001:67c:ef0::/48RIPE—JAGUAR-MNT2024-07-03Not announced

IRR

AS-sets

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

AS-setWhereRelationship
AS30781:AS-JAGUAR-CUST-FRRIPELists AS214589 as a direct member

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