bgpreport

Network · data from 2026-11-12

AS29902 COMPLETE-COMPUTERS - Complete Computers

Registry name: COMPLETE-COMPUTERS - Complete Computers, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29902, 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.
66.20.212.0/24 No ROA None 673 100% 67
66.20.213.0/24 No ROA None 673 100% 67
74.174.194.0/24 No ROA None 672 100% 67
74.174.195.0/24 No ROA None 672 100% 67
74.174.196.0/24 No ROA None 672 100% 67
74.174.197.0/24 No ROA None 672 100% 67
74.174.198.0/24 No ROA None 672 100% 67
74.174.199.0/24 No ROA None 672 100% 67
70.158.10.0/24 No ROA Other IRR onlyALTDB 673 100% 67
209.65.64.0/21 No ROA Other IRR onlyALTDB 673 100% 67
74.174.200.0/24 No ROA Other IRR onlyALTDB 672 100% 67

AS-SET

AS29902 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 22 are in fix.csv.

  • ROA: none11
  • Route object: none8
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none66.20.212.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.673 of 673
Route object: none66.20.212.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.673 of 673
ROA: none66.20.213.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.673 of 673
Route object: none66.20.213.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.673 of 673
ROA: none74.174.194.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: none74.174.194.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.672 of 673
ROA: none74.174.195.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: none74.174.195.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.672 of 673
ROA: none74.174.196.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: none74.174.196.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.672 of 673
ROA: none74.174.197.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: none74.174.197.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.672 of 673
ROA: none74.174.198.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: none74.174.198.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.672 of 673
ROA: none74.174.199.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: none74.174.199.0/24No route object for it. Add a route object with origin AS29902 in the RIR database for the space.672 of 673
ROA: none70.158.10.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.673 of 673
Route object: RIR70.158.10.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none209.65.64.0/21No ROA covers it. Add a ROA for AS29902, maxLength 21.673 of 673
Route object: RIR209.65.64.0/21Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none74.174.200.0/24No ROA covers it. Add a ROA for AS29902, maxLength 24.672 of 673
Route object: RIR74.174.200.0/24Route object only in ALTDB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS29902 is announced.

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.