Network · data from 2026-11-12
AS63016 RENOWN-HEALTH-RENO-NV - Renown Health
Registry name: RENOWN-HEALTH-RENO-NV - Renown Health, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63016, 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.
| 204.115.216.0/22 | No ROA | None | 673 100% |
| 2620:127:7001::/48 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
AS63016 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 | 204.115.216.0/22 | No ROA covers it. Add a ROA for AS63016, maxLength 22. |
| Route object: none | 204.115.216.0/22 | No route object for it. Add a route object with origin AS63016 in the RIR database for the space. |
| ROA: none | 2620:127:7001::/48 | No ROA covers it. Add a ROA for AS63016, maxLength 48. |
| Route object: RIR | 2620:127:7001::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63016 whose prefix no peer sees AS63016 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.115.220.0/23 | RADB | No ROA |
| 204.115.222.0/23 | RADB | No ROA |
| 2620:127:700e::/48 | RADB | No ROA |
| 2620:127:700f::/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.