asn.dev

Routing security

AS46609

Hosting ARIN

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

Announcements

What this network originates

0 observed

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

No announcements from this network were observed in the routing snapshot.

RPKI · ROAs

Route origin authorisations

0 ROAs

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

Route objects naming AS46609 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
206.125.164.0/22RADBDataweb SolutionsMAINT-AS466092023-11-13Not announced
216.252.64.0/19RADBPeer1 Route ObjectMAINT-AS137682026-06-30Not announced
2607:fc10::/32RADBDataweb SolutionsMAINT-AS466092023-11-13Not announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-NLAYER-CUSTOMERSALTDBLists AS46609 as a direct member
AS-TAIPAN-CPOC-6RADBLists AS46609 as a direct member
AS13768:AS-CUSTOMERSRADBLists AS46609 as a direct member
AS4470:AS-QIX-PEERSRADBLists AS46609 as a direct member
AS46609:AS-CONERADBLists AS46609 as a direct member

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