bgpreport

Network · data from 2026-11-12

AS42228 Brightstar

Registry name: Brightstar Brightstar Limited, GB · PeeringDB

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

Announced routes

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

2001:550:109::/48 No ROA None 605 95% 67
193.178.173.0/24 No ROA RIR databaseRIPE 673 100% 66
38.108.97.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
38.109.65.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
38.125.5.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
38.125.20.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
38.125.41.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
38.125.60.0/24 No ROA RIR databaseARIN, RADB 671 100% 67
77.108.160.0/24 Valid Other IRR onlyRADB 672 100% 67
45.137.48.0/22 Valid RIR databaseRIPE 673 100% 66
77.108.128.0/18 Valid RIR databaseRIPE 673 100% 66
2a00:6300::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS42228: AS-BRIGHTSTAR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS42228 isn't in the set, or no route object for AS42228 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS42228 in itNot covered
AS-BRIGHTSTAR RIPE 1111 Yes 1

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.

  • ROA: none8
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2001:550:109::/48No ROA covers it. Add a ROA for AS42228, maxLength 48.605 of 636
Route object: none2001:550:109::/48No route object for it. Add a route object with origin AS42228 in the RIR database for the space.605 of 636
ROA: none193.178.173.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.673 of 673
ROA: none38.108.97.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.672 of 673
ROA: none38.109.65.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.672 of 673
ROA: none38.125.5.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.672 of 673
ROA: none38.125.20.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.672 of 673
ROA: none38.125.41.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.672 of 673
ROA: none38.125.60.0/24No ROA covers it. Add a ROA for AS42228, maxLength 24.671 of 673
Route object: RIR77.108.160.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS42228 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.