asn.dev

Routing security

AS26071 LAKEHEAD

Unclassified ARIN

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

Announcements

What this network originates

1 observed

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

PrefixRPKIIRRVantage points
65.39.0.0/18No ROAIRR54

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS26071 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

1 objects · 0 not announced

Route objects naming AS26071 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
65.39.0.0/18RADBAS26071 proxy-registered route by CogentMAINT-AS1742023-11-13Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-549-AS-CUSTOMERSARINLists AS26071 as a direct member
AS-BIGPIPERADBLists AS26071 as a direct member
AS-NEXICOMRADBLists AS26071 as a direct member
AS26677:AS-GIGAPOPRADBLists AS26071 as a direct member
AS26677:AS-GIGAPOP-PEERINGARINLists AS26071 as a direct member
AS26677:AS-GIGAPOP4RPKIMONARINLists AS26071 as a direct member
AS26677:AS-ROGARINLists AS26071 as a direct member

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