bgpreport

Network · data from 2026-11-12

AS57148 TBSH-CLIENT-TRISTAR-BYTEHOUSE Bytehouse Ltd

Registry name: TBSH-CLIENT-TRISTAR-BYTEHOUSE Bytehouse Ltd, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57148, 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.
188.191.152.0/22 No ROA None 673 100% 67
188.191.154.0/23 No ROA None 673 100% 67
188.191.158.0/23 No ROA Nonecovered by 188.191.156.0/22 673 100% 67
188.191.156.0/23 No ROA Nonecovered by 188.191.156.0/22 672 100% 67
188.191.156.0/22 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS57148 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 13 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none188.191.152.0/22No ROA covers it. Add a ROA for AS57148, maxLength 22.673 of 673
Route object: none188.191.152.0/22No route object for it. Add a route object with origin AS57148 in the RIR database for the space.673 of 673
ROA: none188.191.154.0/23No ROA covers it. Add a ROA for AS57148, maxLength 23.673 of 673
Route object: none188.191.154.0/23No route object for it. Add a route object with origin AS57148 in the RIR database for the space.673 of 673
ROA: none188.191.158.0/23No ROA covers it. Add a ROA for AS57148, maxLength 23.673 of 673
Route object: none188.191.158.0/23No route object for it. A route object for 188.191.156.0/22 with origin AS57148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57148 in the RIR database for the space.673 of 673
ROA: none188.191.156.0/23No ROA covers it. Add a ROA for AS57148, maxLength 23.672 of 673
Route object: none188.191.156.0/23No route object for it. A route object for 188.191.156.0/22 with origin AS57148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57148 in the RIR database for the space.672 of 673
ROA: none188.191.156.0/22No ROA covers it. Add a ROA for AS57148, maxLength 22.673 of 673

Route objects not announced

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

188.191.152.0/24RIPENo ROA
188.191.153.0/24RIPENo ROA
188.191.154.0/24RIPENo ROA
188.191.155.0/24RIPENo 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.