Network · data from 2026-11-12
AS31922 DATTO-ENT - Datto, LLC
Registry name: DATTO-ENT - Datto, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31922, 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.
| 8.12.58.0/24 | No ROA | Other origin only | 673 100% |
| 8.41.72.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS31922 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 8 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.12.58.0/24 | No ROA covers it. Add a ROA for AS31922, maxLength 24. |
| Route object: none | 8.12.58.0/24 | Route objects for it name AS40917. Add a route object with origin AS31922 in the RIR database for the space. |
| ROA: none | 8.41.72.0/24 | No ROA covers it. Add a ROA for AS31922, maxLength 24. |
| Route object: RIR | 8.41.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31922 whose prefix no peer sees AS31922 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.180.113.0/24 | NTTCOM | No ROA |
| 63.110.16.0/24 | NTTCOM | No ROA |
| 2620:125:1005::/48 | RADB | No ROA |
| 2620:125:1007::/48 | 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.