Network · data from 2026-11-12
AS393441 NIOBRARA-RD - NIOBRARA RESEARCH AND DEVELOPMENT CORPORATION
Registry name: NIOBRARA-RD - NIOBRARA RESEARCH AND DEVELOPMENT CORPORATION, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393441, 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.
| 206.223.51.0/24 | No ROA | None | 673 100% |
AS-SET
AS393441 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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.223.51.0/24 | No ROA covers it. Add a ROA for AS393441, maxLength 24. |
| Route object: none | 206.223.51.0/24 | No route object for it. Add a route object with origin AS393441 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393441 whose prefix no peer sees AS393441 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.36.48.0/21 | RADB | No ROA |
| 104.36.48.0/22 | RADB | No ROA |
| 208.50.252.0/24 | RADB | No ROA |
| 2606:a480::/32 | 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.