asn.dev

Routing security

AS42064

Unclassified RIPE Route Server

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 AS42064 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 AS42064 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

1 declared

This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.

ASNetworkASPARouting paths
AS0unnamedDeclarednot observed

An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.

IRR

Registered route objects

0 objects · 0 not announced

Route objects naming AS42064 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 AS42064 directly show who expects to carry it.

AS-setWhereRelationship
AS42064:AS-MEMBERSPeeringDBDeclared by the operator as its own set
AS-DCENTERRIPELists AS42064 as a direct member
AS-RIS-RRC21RIPELists AS42064 as a direct member
AS25091:AS-ROUTESERVERSRIPELists AS42064 as a direct member
AS5617:AS-PLRIPELists AS42064 as a direct member
AS8298:AS-PEERSRIPELists AS42064 as a direct member

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