Network · data from 2026-11-12
AS211321 NLnet Labs
Registry name: NLnetLabs Stichting NLnet Labs, NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211321, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2a04:b906::/48 | Invalid: origin | None | 48 8%low visibility |
| 185.49.142.0/24 | Invalid: maxLength | RIR databaseRIPE | 77 11% |
| 2a04:b907::/48 | Invalid: maxLength | RIR databaseRIPE | 62 10%low visibility |
| 185.49.142.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 2a04:b907::/47 | Valid | Other IRR onlyRADB | 636 100% |
| 2a04:b904::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:b904:7200::/40 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS211321's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.
- ROA: origin1
- ROA: maxLength2
- Route object: none1
- Route object: RIR2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a04:b906::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS211321 should announce it, add a ROA for AS211321. |
| Route object: none | 2a04:b906::/48 | No route object for it. Add a route object with origin AS211321 in the RIR database for the space. |
| ROA: maxLength | 185.49.142.0/24 | ROA 185.49.142.0/23 AS211321 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 185.49.142.0/24. |
| ROA: maxLength | 2a04:b907::/48 | ROA 2a04:b907::/47 AS211321 has maxLength 47; the route is a /48. Raise the maxLength, or add a ROA for 2a04:b907::/48. |
| Route object: RIR | 185.49.142.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a04:b907::/47 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS211321 whose prefix no peer sees AS211321 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.228.88.0/23 | ARIN | Valid |
| 192.228.91.0/24 | ARIN | Valid |
| 203.119.21.0/24 | APNIC | No ROA |
| 203.119.22.0/23 | APNIC, RADB | No ROA |
| 2001:ddb::/48 | APNIC, RADB | No ROA |
| 2a04:b905::/32 | RADB | No ROA |
| 2a04:b907:4::/47 | RADB, RIPE | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.