asn.dev

Routing security

AS401807 INTUITY

Unclassified ARIN

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

Announcements

What this network originates

2 observed

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

PrefixRPKIIRRVantage points
69.166.192.0/24RPKI validIRR covering52
69.166.193.0/24RPKI validIRR covering52

RPKI · ROAs

Route origin authorisations

3 ROAs

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

PrefixMax lengthTrust anchor
69.166.192.0/23/23ARIN
69.166.192.0/24/24ARIN
69.166.193.0/24/24ARIN

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

Route objects naming AS401807 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
69.166.192.0/23ARINUsed by EndUserMNT-DCL-5772025-07-18Not announced
69.166.192.0/23RADBautogenMAINT-AS8342025-07-18Not announced

IRR

AS-sets

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

No as-set lists this AS directly.

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