asn.dev

Routing security

AS319 DNIC-ASBLK-00306-00371

Unclassified ARIN

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

Announcements

What this network originates

9 observed

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

PrefixRPKIIRRVantage points
55.26.0.0/16No ROANo IRR53
55.26.52.0/22No ROANo IRR53
55.26.68.0/24No ROANo IRR53
55.26.163.0/24No ROANo IRR53
55.26.164.0/24No ROANo IRR53
55.26.166.0/24No ROANo IRR53
55.26.167.0/24No ROANo IRR53
55.26.168.0/24No ROANo IRR53
2608:14b:2900::/40No ROANo IRR31

RPKI · ROAs

Route origin authorisations

0 ROAs

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

0 objects · 0 not announced

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

AS-setWhereRelationship
AS199746:AS-BLACKLISTRIPELists AS319 as a direct member
AS204464:AS-BLACKLISTRIPELists AS319 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.