Network · data from 2026-11-12
AS36056 ALASK-15 - Alaska Native Medical Center
Registry name: ALASK-15 - Alaska Native Medical Center, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36056, 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.
| 199.59.216.0/22 | No ROA | Other origin onlycovered by 199.59.216.0/21 | 671 100% |
AS-SET
AS36056 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 3 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.59.216.0/22 | No ROA covers it. Add a ROA for AS36056, maxLength 22. |
| Route object: none | 199.59.216.0/22 | Route objects for it name AS8047. A route object for 199.59.216.0/21 with origin AS36056 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36056 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36056 whose prefix no peer sees AS36056 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.59.216.0/21 | 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.