asn.dev

Routing security

AS16563 NEXUM-ASN

Unclassified ARIN

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

Announcements

What this network originates

1 observed

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

PrefixRPKIIRRVantage points
208.86.96.0/23RPKI validIRR52

RPKI · ROAs

Route origin authorisations

3 ROAs

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

PrefixMax lengthTrust anchor
208.86.96.0/23/23ARIN
208.86.96.0/24/24ARIN
208.86.97.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

4 objects · 3 not announced

Route objects naming AS16563 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
69.8.123.160/28RADB—MAINT-AS165632026-06-10Not announced
208.86.96.0/24RADB—MAINT-AS165632024-07-10Not announced
208.86.97.0/24RADB—MAINT-AS165632024-07-08Not announced
208.86.96.0/23RADB—MAINT-AS165632024-07-10Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-COMCAST-EDIARADBLists AS16563 as a direct member
AS-DATA393-INV01RADBLists AS16563 as a direct member
AS-DATABANKRADBLists AS16563 as a direct member
AS16563:AS-CONERADBLists AS16563 as a direct member

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