Network · data from 2026-11-12
AS209929 AWMLT AWM LAB LTD
Registry name: AWMLT AWM LAB LTD, VG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209929, 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.
| 109.206.224.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 2a0e:2900::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0e:2901::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0e:2902::/32 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS209929 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.
- ROA: none4
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.206.224.0/22 | No ROA covers it. Add a ROA for AS209929, maxLength 22. |
| ROA: none | 2a0e:2900::/32 | No ROA covers it. Add a ROA for AS209929, maxLength 32. |
| ROA: none | 2a0e:2901::/32 | No ROA covers it. Add a ROA for AS209929, maxLength 32. |
| ROA: none | 2a0e:2902::/32 | No ROA covers it. Add a ROA for AS209929, maxLength 32. |
Route objects not announced
Route objects with origin AS209929 whose prefix no peer sees AS209929 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0e:2903::/32 | RIPE | No ROA |
| 2a0e:2904::/32 | RIPE | No ROA |
| 2a0e:2905::/32 | RIPE | No ROA |
| 2a0e:2906::/32 | RIPE | No ROA |
| 2a0e:2907::/32 | 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.