Network · data from 2026-11-12
AS37907 DIGIROCK - DigiRock, Inc.
Registry name: DIGIROCK - DigiRock, Inc., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37907, 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.
| 183.90.182.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 183.90.183.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 183.90.176.0/21 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 202.172.24.0/21 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 103.242.28.0/22 | No ROA | Other IRR onlyJPIRR, RADB | 670 100% |
AS-SET
AS37907 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 28 are in fix.csv.
- ROA: none5
- Route object: RIR5
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 183.90.182.0/24 | No ROA covers it. Add a ROA for AS37907, maxLength 24. |
| Route object: RIR | 183.90.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 183.90.183.0/24 | No ROA covers it. Add a ROA for AS37907, maxLength 24. |
| Route object: RIR | 183.90.183.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 183.90.176.0/21 | No ROA covers it. Add a ROA for AS37907, maxLength 21. |
| Route object: RIR | 183.90.176.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.172.24.0/21 | No ROA covers it. Add a ROA for AS37907, maxLength 21. |
| Route object: RIR | 202.172.24.0/21 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.242.28.0/22 | No ROA covers it. Add a ROA for AS37907, maxLength 22. |
| Route object: RIR | 103.242.28.0/22 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS37907 whose prefix no peer sees AS37907 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.242.28.0/24 | RADB | No ROA |
| 103.242.29.0/24 | RADB | No ROA |
| 103.242.30.0/24 | RADB | No ROA |
| 103.242.31.0/24 | RADB | No ROA |
| 183.90.176.0/24 | RADB | No ROA |
| 183.90.177.0/24 | RADB | No ROA |
| 183.90.178.0/24 | RADB | No ROA |
| 183.90.179.0/24 | RADB | No ROA |
| 183.90.180.0/24 | RADB | No ROA |
| 183.90.181.0/24 | RADB | No ROA |
| 202.172.24.0/24 | RADB | No ROA |
| 202.172.25.0/24 | RADB | No ROA |
| 202.172.26.0/24 | RADB | No ROA |
| 202.172.27.0/24 | RADB | No ROA |
| 202.172.28.0/24 | RADB | No ROA |
| 202.172.29.0/24 | RADB | No ROA |
| 202.172.30.0/24 | RADB | No ROA |
| 202.172.31.0/24 | 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.