Routing security

AS63778 BGPNAP2 - Border Gateway Protocol Network Analysis Project

Unclassified APNIC Non-Profit

RPKI valid 100% 31 of 31 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 0% 31 missing · 0 other origin

ROAs 1 authorising this AS

Announcements

What this network originates

31 observed

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

Prefix	RPKI	IRR	Vantage points
2401:7641::/32	RPKI valid	No IRR	32
2401:7641::/33	RPKI valid	No IRR	32
2401:7641::/34	RPKI valid	No IRR	32
2401:7641::/35	RPKI valid	No IRR	32
2401:7641::/36	RPKI valid	No IRR	32
2401:7641:1000::/36	RPKI valid	No IRR	32
2401:7641:2000::/35	RPKI valid	No IRR	32
2401:7641:2000::/36	RPKI valid	No IRR	32
2401:7641:3000::/36	RPKI valid	No IRR	32
2401:7641:4000::/34	RPKI valid	No IRR	32
2401:7641:4000::/35	RPKI valid	No IRR	32
2401:7641:4000::/36	RPKI valid	No IRR	32
2401:7641:5000::/36	RPKI valid	No IRR	32
2401:7641:6000::/35	RPKI valid	No IRR	32
2401:7641:6000::/36	RPKI valid	No IRR	32
2401:7641:7000::/36	RPKI valid	No IRR	32
2401:7641:8000::/33	RPKI valid	No IRR	32
2401:7641:8000::/34	RPKI valid	No IRR	32
2401:7641:8000::/35	RPKI valid	No IRR	32
2401:7641:8000::/36	RPKI valid	No IRR	32
2401:7641:9000::/36	RPKI valid	No IRR	32
2401:7641:a000::/35	RPKI valid	No IRR	32
2401:7641:a000::/36	RPKI valid	No IRR	32
2401:7641:b000::/36	RPKI valid	No IRR	32
2401:7641:c000::/34	RPKI valid	No IRR	32
2401:7641:c000::/35	RPKI valid	No IRR	32
2401:7641:c000::/36	RPKI valid	No IRR	32
2401:7641:d000::/36	RPKI valid	No IRR	32
2401:7641:e000::/35	RPKI valid	No IRR	32
2401:7641:e000::/36	RPKI valid	No IRR	32
2401:7641:f000::/36	RPKI valid	No IRR	32

RPKI · ROAs

Route origin authorisations

1 ROAs

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

Prefix	Max length	Trust anchor
2401:7641::/32	/48	APNIC

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

0 objects · 0 not announced

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

AS-set	Where	Relationship
`AS-BBIX-T-V6`	RADB	Lists AS63778 as a direct member
`AS-GCTR-JP`	RADB	Lists AS63778 as a direct member
`AS-GIGAINFRA-V6`	RADB	Lists AS63778 as a direct member
`AS-HURRICANEV6`	RADB	Lists AS63778 as a direct member
`AS-IIJ`	RADB	Lists AS63778 as a direct member
`AS-IIJ6`	RADB	Lists AS63778 as a direct member
`AS-KDD`	RADB	Lists AS63778 as a direct member
`AS-KDDI6`	RADB	Lists AS63778 as a direct member
`AS-MESH-CUSTOMER:AS59105`	RADB	Lists AS63778 as a direct member
`AS-PNAPTOK`	RADB	Lists AS63778 as a direct member
`AS-SAKURA`	RADB	Lists AS63778 as a direct member
`AS2497:AS-IIJ`	RADB	Lists AS63778 as a direct member
`AS2497:AS-IIJ6`	RADB	Lists AS63778 as a direct member

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