Network · data from 2026-11-12
AS273234 AS273234 - ACCESS DIGITAL SAS
Registry name: AS273234 - ACCESS DIGITAL SAS, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273234, 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.
| 2803:7e50::/32 | Invalid: origin | None | 75 12% |
| 38.156.224.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
AS-SET
AS273234 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 5 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2803:7e50::/32 | ROAs covering it name AS262589, AS263195, not AS273234. If AS273234 should announce it, add a ROA for AS273234. |
| Route object: none | 2803:7e50::/32 | No route object for it. Add a route object with origin AS273234 in the RIR database for the space. |
| ROA: none | 38.156.224.0/24 | No ROA covers it. Add a ROA for AS273234, maxLength 24. |
| Route object: RIR | 38.156.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273234 whose prefix no peer sees AS273234 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.156.224.0/27 | RADB | 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.