asn.dev

Routing security

AS210673 VIRTUASYS-DE

Unclassified RIPE NCC

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

PrefixRPKIIRRVantage points
2a0d:2a80::/29No ROAIRR30
2a0d:2a80::/32No ROAIRR covering30
132.243.80.0/20No ROAIRR52

RPKI · ROAs

Route origin authorisations

0 ROAs

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

Route objects naming AS210673 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
132.243.80.0/20RIPEYango TechnologyLIR-RS-YANGOTECH-1-MNT2026-06-16Announced
2a0d:2a80::/29RIPEYango TechnologyLIR-RS-YANGOTECH-1-MNT2026-02-24Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS210673:AS-YANGORIPELists AS210673 as a direct member

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