bgpreport

Network · data from 2026-11-12

AS22391 BCIS-BEXAR-COUNTY-INFORMATION-SERVICES - Bexar County - Information Technology

Registry name: BCIS-BEXAR-COUNTY-INFORMATION-SERVICES - Bexar County - Information Technology, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22391, 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.
208.83.179.0/24 No ROA Nonecovered by 208.83.178.0/23 673 100% 67
208.83.176.0/24 No ROA Nonecovered by 208.83.176.0/23 671 100% 67
208.83.178.0/24 No ROA Nonecovered by 208.83.178.0/23 671 100% 67
208.83.183.0/24 No ROA Nonecovered by 208.83.182.0/23 671 100% 67
208.83.176.0/23 No ROA Other IRR onlyRADB 672 100% 67
208.83.180.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS22391 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 15 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none208.83.179.0/24No ROA covers it. Add a ROA for AS22391, maxLength 24.673 of 673
Route object: none208.83.179.0/24No route object for it. A route object for 208.83.178.0/23 with origin AS22391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22391 in the RIR database for the space.673 of 673
ROA: none208.83.176.0/24No ROA covers it. Add a ROA for AS22391, maxLength 24.671 of 673
Route object: none208.83.176.0/24No route object for it. A route object for 208.83.176.0/23 with origin AS22391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22391 in the RIR database for the space.671 of 673
ROA: none208.83.178.0/24No ROA covers it. Add a ROA for AS22391, maxLength 24.671 of 673
Route object: none208.83.178.0/24No route object for it. A route object for 208.83.178.0/23 with origin AS22391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22391 in the RIR database for the space.671 of 673
ROA: none208.83.183.0/24No ROA covers it. Add a ROA for AS22391, maxLength 24.671 of 673
Route object: none208.83.183.0/24No route object for it. A route object for 208.83.182.0/23 with origin AS22391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22391 in the RIR database for the space.671 of 673
ROA: none208.83.176.0/23No ROA covers it. Add a ROA for AS22391, maxLength 23.672 of 673
Route object: RIR208.83.176.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.83.180.0/24No ROA covers it. Add a ROA for AS22391, maxLength 24.672 of 673
Route object: RIR208.83.180.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

208.83.176.0/21ARINNo ROA
208.83.178.0/23RADBNo ROA
208.83.182.0/23RADBNo 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.