asn.dev

Routing security

AS206379 ANILIS

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 AS206379 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
91.220.27.0/24No ROAIRR52
185.43.240.0/23No ROAIRR covering52
185.43.242.0/23No ROAIRR covering52

RPKI · ROAs

Route origin authorisations

0 ROAs

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

Route objects naming AS206379 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
185.43.240.0/22RIPE—MNT-ANILIS2017-04-07Not announced
2a04:7e40::/29RIPE—MNT-ANILIS2017-04-07Not announced
91.220.27.0/24RIPE—MNT-ANILIS2017-04-07Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-ANILRIPELists AS206379 as a direct member

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