asn.dev

Routing security

AS18604 AIHOST

Unclassified ARIN

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
23.133.212.0/24No ROANo IRR52
65.181.108.0/23No ROANo IRR52
69.94.0.0/23No ROANo IRR52

RPKI · ROAs

Route origin authorisations

1 ROAs

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

PrefixMax lengthTrust anchor
204.245.225.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

0 objects · 0 not announced

Route objects naming AS18604 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.

No route objects name this AS as origin.

IRR

AS-sets

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

AS-setWhereRelationship
AS-GPIEXARINLists AS18604 as a direct member
AS-WLISARINLists AS18604 as a direct member
AS35280:AS-DEFENSERIPELists AS18604 as a direct member

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