asn.dev

Routing security

AS204252 REYGERS-AS Reygers Systemhaus GmbH

Unclassified APNIC

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

Announcements

What this network originates

2 observed

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

PrefixRPKIIRRVantage points
45.134.232.0/22RPKI validIRR53
185.109.180.0/22RPKI validIRR53

RPKI · ROAs

Route origin authorisations

2 ROAs

Signed statements by address holders that AS204252 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
45.134.232.0/22/22RIPENCC
185.109.180.0/22/22RIPENCC

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 AS204252 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
45.134.232.0/22RIPEReygers Systemhaus GmbHDE-REYGERS-1-MNT2019-07-29Announced
185.109.180.0/22RIPEReygers Systemhaus GmbHDE-REYGERS-1-MNT2015-07-31Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS-DGWRIPELists AS204252 as a direct member
AS-KOMDSL-OUTRIPELists AS204252 as a direct member
AS-SW-RHEDERIPELists AS204252 as a direct member
AS198726:AS-WEMACONNECTRIPELists AS204252 as a direct member

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