Network · data from 2026-11-12
AS29152 Decknet
Registry name: DECKNET-AS Decknet SARL, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29152, 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.
| 94.126.112.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 185.89.68.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 8.12.112.0/24 | No ROA | RIR databaseARIN | 664 99% |
| 195.80.152.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.80.153.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.80.154.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.80.155.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.80.156.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.80.157.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.80.159.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a00:1b11:116::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS29152'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 6 are in fix.csv.
- ROA: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.126.112.0/21 | No ROA covers it. Add a ROA for AS29152, maxLength 21. |
| ROA: none | 185.89.68.0/22 | No ROA covers it. Add a ROA for AS29152, maxLength 22. |
| ROA: none | 8.12.112.0/24 | No ROA covers it. Add a ROA for AS29152, maxLength 24. |
Route objects not announced
Route objects with origin AS29152 whose prefix no peer sees AS29152 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:1b10::/32 | RIPE | No ROA |
| 2a00:1b11:113::/48 | RIPE | No ROA |
| 2a00:1b11:115::/48 | RIPE | Valid |
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.