asn.dev

Routing security

AS26016 -Reserved AS-

Unclassified ARIN

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

Announcements

What this network originates

2 observed

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

PrefixRPKIIRRVantage points
64.238.134.0/24No ROAIRR53
74.217.164.0/24No ROAIRR54

RPKI · ROAs

Route origin authorisations

0 ROAs

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

Route objects naming AS26016 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
216.223.14.0/24RADBSpartan Tech-AS26016(added by MAINT-AS3257)MAINT-AS32572023-11-13Not announced
64.238.134.0/24RADBERR_AS_NAME_NOT_FOUNDMAINT-AS275062025-09-03Announced
74.217.164.0/24RADBPNAP-NYMMAINT-AS18282023-11-13Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-CCFRADBLists AS26016 as a direct member
AS-CCF-TESTRADBLists AS26016 as a direct member
AS-PNAPNYCRADBLists AS26016 as a direct member
AS-PNAPNYMRADBLists AS26016 as a direct member
AS-XO-BARINLists AS26016 as a direct member

RPKI from rpki-client, validated 2026-11-13 13:05 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-13. Cross-check on bgp.he.net.