bgpreport

Network · data from 2026-11-12

AS89 NNIC AS89

Registry name: DNIC-AS-00089 - Navy Network Information Center (NNIC), US · PeeringDB

6IPv4 routes 0.0% RPKI valid · 83.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS89, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS89, 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.
129.190.0.0/16 No ROA Other origin only 671 100% 70
164.223.0.0/16 No ROA Other IRR onlyRADB 671 100% 69
198.97.81.0/24 No ROA Other IRR onlyRADB 671 100% 69
198.97.82.0/23 No ROA Other IRR onlyRADB 671 100% 69
198.97.84.0/22 No ROA Other IRR onlyRADB 671 100% 69
198.97.88.0/24 No ROA Other IRR onlyRADB 671 100% 69
2001:480:540::/48 Valid RIR databaseARIN 635 100% 70

AS-SET

AS89's PeeringDB record names no 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 18 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none129.190.0.0/16No ROA covers it. Add a ROA for AS89, maxLength 16.671 of 673
Route object: none129.190.0.0/16Route objects for it name AS668. Add a route object with origin AS89 in the RIR database for the space.671 of 673
ROA: none164.223.0.0/16No ROA covers it. Add a ROA for AS89, maxLength 16.671 of 673
Route object: RIR164.223.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.97.81.0/24No ROA covers it. Add a ROA for AS89, maxLength 24.671 of 673
Route object: RIR198.97.81.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.97.82.0/23No ROA covers it. Add a ROA for AS89, maxLength 23.671 of 673
Route object: RIR198.97.82.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.97.84.0/22No ROA covers it. Add a ROA for AS89, maxLength 22.671 of 673
Route object: RIR198.97.84.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.97.88.0/24No ROA covers it. Add a ROA for AS89, maxLength 24.671 of 673
Route object: RIR198.97.88.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS89 whose prefix no peer sees AS89 announce. Many are kept on purpose (backup routes, space announced only in some places).

164.223.1.0/24RADBNo ROA
164.223.10.0/24RADBNo ROA
164.223.71.0/24RADBNo ROA
164.223.73.0/24RADBNo ROA
164.223.239.0/24RADBNo ROA
164.223.250.0/24RADBNo 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.