bgpreport

Network · data from 2026-11-12

AS22750 BCSGroup

Registry name: BCS Group (BCSNet) - BCS Group (BCSNet), ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22750, 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.
196.44.64.0/19 No ROA Other IRR onlyRADB, RIPE-NONAUTH 672 100% 67
196.44.224.0/20 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 672 100% 67

AS-SET

AS22750's PeeringDB record names no 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 35 are in fix.csv.

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none196.44.64.0/19No ROA covers it. Add a ROA for AS22750, maxLength 19.672 of 673
Route object: RIR196.44.64.0/19Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none196.44.224.0/20No ROA covers it. Add a ROA for AS22750, maxLength 20.672 of 673

Route objects not announced

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

41.57.0.0/18RIPE-NONAUTHNo ROA
41.57.0.0/20RIPE-NONAUTHNo ROA
41.57.16.0/21RIPE-NONAUTHNo ROA
41.57.24.0/24RIPE-NONAUTHNo ROA
41.57.25.0/24RIPE-NONAUTHNo ROA
41.57.27.0/24RIPE-NONAUTHNo ROA
41.57.30.0/24RIPE-NONAUTHNo ROA
41.57.63.0/24RIPE-NONAUTHNo ROA
41.57.128.0/18RIPE-NONAUTHNo ROA
41.57.131.0/24RIPE-NONAUTHNo ROA
41.57.145.0/24RIPE-NONAUTHNo ROA
41.66.64.0/18RIPE-NONAUTHValid
160.226.180.0/24RIPE-NONAUTHNo ROA
192.96.139.0/24RIPE-NONAUTHNo ROA
196.44.64.0/24RIPE-NONAUTHNo ROA
196.44.65.0/24RIPE-NONAUTHNo ROA
196.44.66.0/24RADB, RIPE-NONAUTHNo ROA
196.44.75.0/24RIPE-NONAUTHNo ROA
196.44.76.0/24RIPE-NONAUTHNo ROA
196.44.78.0/24RIPE-NONAUTHNo ROA
196.44.80.0/24RIPE-NONAUTHNo ROA
196.44.84.0/24RIPE-NONAUTHNo ROA
196.44.90.0/24RADB, RIPE-NONAUTHNo ROA
196.44.91.0/24RADB, RIPE-NONAUTHNo ROA
196.44.92.0/24RIPE-NONAUTHNo ROA
196.44.93.0/24RIPE-NONAUTHNo ROA
196.44.94.0/24RIPE-NONAUTHNo ROA
196.44.226.0/24RIPE-NONAUTHNo ROA
196.44.227.0/24RADB, RIPE-NONAUTHNo ROA
196.44.236.0/24RIPE-NONAUTHNo ROA
196.44.239.0/24RADB, RIPE-NONAUTHNo ROA
197.211.128.0/18RIPE-NONAUTHValid

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.