asn.dev

Routing security

AS47300 INRS-AS

Unclassified RIPE

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

Announcements

What this network originates

3 observed

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

PrefixRPKIIRRVantage points
193.203.108.0/23No ROAIRR52
193.203.108.0/24No ROAIRR56
193.203.109.0/24No ROAIRR54

RPKI · ROAs

Route origin authorisations

0 ROAs

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

Route objects naming AS47300 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
193.203.108.0/23RIPEInstitut National de la Recherche en Securite INRSRMI-MNT2018-07-27Announced
193.203.108.0/24RIPEInstitut National de la Recherche en Securite INRSRMI-MNT2018-07-27Announced
193.203.109.0/24RIPEInstitut National de la Recherche en Securite INRSRMI-MNT2018-07-27Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-ADISTA-DOWNSTREAMRIPELists AS47300 as a direct member
AS-RENATERRIPELists AS47300 as a direct member
AS-RMIRIPELists AS47300 as a direct member

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