asn.dev

Routing security

AS203138 VANBERKELLANDSCHAPENINFRA-AS

Unclassified RIPE

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

PrefixRPKIIRRVantage points
150.237.120.0/24RPKI validIRR52
2001:678:116c::/48RPKI validIRR33

RPKI · ROAs

Route origin authorisations

2 ROAs

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

PrefixMax lengthTrust anchor
150.237.120.0/24/24RIPENCC
2001:678:116c::/48/48RIPENCC

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 AS203138 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
150.237.120.0/24RIPE—VAN-BERKEL-MNT2026-10-09Announced
2001:678:116c::/48RIPE—VAN-BERKEL-MNT2025-12-05Announced

IRR

AS-sets

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

AS-setWhereRelationship
AS203138:AS-VANBERKELPeeringDBDeclared by the operator as its own set
AS-HURRICANEV6RADBLists AS203138 as a direct member
AS203138:AS-VANBERKELRIPELists AS203138 as a direct member
AS20473:AS-VULTRRADBLists AS203138 as a direct member
AS35661:AS-AMS01NLRIPELists AS203138 as a direct member

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