bgpreport

Network · data from 2026-11-12

AS11302 BSTAR - Brightstar Global Solutions Corporation

Registry name: BSTAR - Brightstar Global Solutions Corporation, US · not in PeeringDB

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

Announced routes

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

192.156.100.0/24 No ROA Nonecovered by 192.156.100.0/22 672 100% 67
192.156.101.0/24 No ROA Other origin onlycovered by 192.156.100.0/22 672 100% 67
192.156.109.0/24 No ROA Nonecovered by 192.156.104.0/21 672 100% 67
192.156.110.0/24 No ROA Nonecovered by 192.156.104.0/21 672 100% 67
192.156.111.0/24 No ROA Other origin onlycovered by 192.156.104.0/21 672 100% 67
192.156.114.0/24 No ROA Nonecovered by 192.156.112.0/20 672 100% 67
192.156.122.0/24 No ROA Nonecovered by 192.156.112.0/20 672 100% 67
192.156.124.0/24 No ROA Nonecovered by 192.156.112.0/20 672 100% 67
192.156.106.0/24 No ROA Nonecovered by 192.156.104.0/21 671 100% 67

AS-SET

AS11302 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 24 are in fix.csv.

  • ROA: none9
  • Route object: none9
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none192.156.100.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.100.0/24No route object for it. A route object for 192.156.100.0/22 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.101.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.101.0/24Route objects for it name AS3300. A route object for 192.156.100.0/22 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.109.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.109.0/24No route object for it. A route object for 192.156.104.0/21 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.110.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.110.0/24No route object for it. A route object for 192.156.104.0/21 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.111.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.111.0/24Route objects for it name AS46887. A route object for 192.156.104.0/21 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.114.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.114.0/24No route object for it. A route object for 192.156.112.0/20 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.122.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.122.0/24No route object for it. A route object for 192.156.112.0/20 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.124.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.672 of 673
Route object: none192.156.124.0/24No route object for it. A route object for 192.156.112.0/20 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.672 of 673
ROA: none192.156.106.0/24No ROA covers it. Add a ROA for AS11302, maxLength 24.671 of 673
Route object: none192.156.106.0/24No route object for it. A route object for 192.156.104.0/21 with origin AS11302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11302 in the RIR database for the space.671 of 673

Route objects not announced

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

192.156.99.0/24RADBNo ROA
192.156.100.0/22RADBNo ROA
192.156.104.0/21RADBNo ROA
192.156.112.0/20RADBNo ROA
192.156.128.0/23RADBNo ROA
192.156.130.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.