asn.dev

Routing security

AS42327 KERNEL-TRADE-AS

Unclassified RIPE

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
193.33.44.0/23No ROAIRR52
193.33.44.0/24No ROAIRR52
193.33.45.0/24No ROAIRR52

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS42327 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 · 0 not announced

Route objects naming AS42327 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
193.33.44.0/23RIPEKernel Trade GroupKERNEL-UA-MNT2007-02-02Announced
193.33.44.0/24RIPE—KERNEL-UA-MNT2022-02-08Announced
193.33.45.0/24RIPE—KERNEL-UA-MNT2022-02-09Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-GGTRIPELists AS42327 as a direct member
AS-NEWLINERIPELists AS42327 as a direct member
AS-RETN-ACTUAL-V4RIPELists AS42327 as a direct member
AS-UMC-CUSTOMERSRIPELists AS42327 as a direct member
AS3326:AS-CLIENTSRIPELists AS42327 as a direct member

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