asn.dev

Routing security

AS206709 THUASNE

Unclassified RIPE

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

Announcements

What this network originates

5 observed

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

PrefixRPKIIRRVantage points
185.178.132.0/22No ROAIRR52
185.178.132.0/24No ROAIRR covering52
185.178.133.0/24No ROAIRR covering52
185.178.134.0/24No ROAIRR covering52
185.178.135.0/24No ROAIRR covering52

RPKI · ROAs

Route origin authorisations

0 ROAs

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

2 objects · 1 not announced

Route objects naming AS206709 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
2a0a:6180::/29RIPETHUASNE NETWORKMNT-THUASNE2016-11-21Not announced
185.178.132.0/22RIPETHUASNE NETWORKMNT-THUASNE2016-11-21Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-ADISTA-DOWNSTREAMRIPELists AS206709 as a direct member
AS-RAINRIPELists AS206709 as a direct member
AS-RMIRIPELists AS206709 as a direct member
AS-THUASNERIPELists AS206709 as a direct member

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