Network · data from 2026-11-12
AS29527 ASTUTIUM-AS Astutium Limited
Registry name: ASTUTIUM-AS Astutium Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29527, 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.
| 193.84.0.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.108.221.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.203.20.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.203.21.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 80.76.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.76.216.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 83.243.96.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.227.124.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 95.128.48.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 194.150.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.148.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 2001:4bf0:1::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS29527 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 4 are in fix.csv.
- ROA: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.84.0.0/24 | No ROA covers it. Add a ROA for AS29527, maxLength 24. |
| ROA: none | 193.108.221.0/24 | No ROA covers it. Add a ROA for AS29527, maxLength 24. |
| ROA: none | 193.203.20.0/24 | No ROA covers it. Add a ROA for AS29527, maxLength 24. |
| ROA: none | 193.203.21.0/24 | No ROA covers it. Add a ROA for AS29527, maxLength 24. |
Route objects not announced
Every route object with origin AS29527 is announced.
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.