bgpreport

Network · data from 2026-11-12

AS22803 NOV-AS - National Oilwell Varco, Inc.

Registry name: NOV-AS - National Oilwell Varco, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22803, 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.235.0/24 Valid Nonecovered by 199.59.234.0/23 673 100% 70
199.59.234.0/24 Valid Other IRR onlyNTTCOM 673 100% 70
208.92.228.0/24 Valid Other IRR onlyNTTCOM 673 100% 70
208.92.229.0/24 Valid Other IRR onlyNTTCOM 673 100% 70
208.92.230.0/24 Valid Other IRR onlyNTTCOM 673 100% 70
208.92.231.0/24 Valid Other IRR onlyNTTCOM 673 100% 70

AS-SET

AS22803 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 10 are in fix.csv.

  • Route object: none1
  • Route object: RIR5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none199.59.235.0/24No route object for it. A route object for 199.59.234.0/23 with origin AS22803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22803 in the RIR database for the space.673 of 673
Route object: RIR199.59.234.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR208.92.228.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR208.92.229.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR208.92.230.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR208.92.231.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

199.59.234.0/23ARINValid
208.92.228.0/22ARINValid
2001:470:5c5::/48ARINValid
2620:33::/48ARINValid

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.