bgpreport

Network · data from 2026-11-12

AS19739 COUNTY-SANBERNARDINO - County of San Bernardino

Registry name: COUNTY-SANBERNARDINO - County of San Bernardino, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19739, 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.

170.164.0.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.10.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.11.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.14.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.40.0/23 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.42.0/23 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.44.0/23 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.50.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.60.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.70.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.75.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.84.0/23 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.87.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.97.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.101.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.116.0/22 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.124.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.125.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.165.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.239.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.240.0/21 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.248.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.249.0/24 No ROA Nonecovered by 170.164.0.0/16 673 100% 67
170.164.20.0/24 No ROA Nonecovered by 170.164.0.0/16 672 100% 67
170.164.21.0/24 No ROA Nonecovered by 170.164.0.0/16 672 100% 67
170.164.71.0/24 No ROA Nonecovered by 170.164.0.0/16 672 100% 67
170.164.107.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS19739 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 57 are in fix.csv.

  • ROA: none27
  • Route object: none26
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none170.164.0.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.0.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.10.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.10.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.11.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.11.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.14.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.14.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.40.0/23No ROA covers it. Add a ROA for AS19739, maxLength 23.673 of 673
Route object: none170.164.40.0/23No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.42.0/23No ROA covers it. Add a ROA for AS19739, maxLength 23.673 of 673
Route object: none170.164.42.0/23No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.44.0/23No ROA covers it. Add a ROA for AS19739, maxLength 23.673 of 673
Route object: none170.164.44.0/23No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.50.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.50.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.60.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.60.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.70.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.70.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.75.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.75.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.84.0/23No ROA covers it. Add a ROA for AS19739, maxLength 23.673 of 673
Route object: none170.164.84.0/23No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.87.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.87.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.97.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.97.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.101.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.101.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.116.0/22No ROA covers it. Add a ROA for AS19739, maxLength 22.673 of 673
Route object: none170.164.116.0/22No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.124.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.124.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.125.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.125.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.165.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.165.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.239.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.239.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.240.0/21No ROA covers it. Add a ROA for AS19739, maxLength 21.673 of 673
Route object: none170.164.240.0/21No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.248.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.248.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.249.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.673 of 673
Route object: none170.164.249.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.673 of 673
ROA: none170.164.20.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.672 of 673
Route object: none170.164.20.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.672 of 673
ROA: none170.164.21.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.672 of 673
Route object: none170.164.21.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.672 of 673
ROA: none170.164.71.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.672 of 673
Route object: none170.164.71.0/24No route object for it. A route object for 170.164.0.0/16 with origin AS19739 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19739 in the RIR database for the space.672 of 673
ROA: none170.164.107.0/24No ROA covers it. Add a ROA for AS19739, maxLength 24.671 of 673
Route object: RIR170.164.107.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 AS19739 whose prefix no peer sees AS19739 announce. Many are kept on purpose (backup routes, space announced only in some places).

170.164.0.0/16RADBNo ROA
170.164.120.0/24RADBNo ROA
192.138.233.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.