bgpreport

Network · data from 2026-11-12

AS37012 Comsys (GH) Limited - Comsys (GH) Limited

Registry name: Comsys (GH) Limited - Comsys (GH) Limited, GH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37012, 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.61.32.0/20 No ROA RIR databaseAFRINIC 672 100% 68
197.159.128.0/20 No ROA RIR databaseAFRINIC, RADB 672 100% 68
196.61.42.0/24 Valid Other origin onlycovered by 196.61.32.0/20 669 99% 68
196.61.43.0/24 Valid Other origin onlycovered by 196.61.32.0/20 669 99% 68
196.61.44.0/24 Valid Other origin onlycovered by 196.61.32.0/20 669 99% 68
196.61.45.0/24 Valid Other origin onlycovered by 196.61.32.0/20 669 99% 68
196.61.47.0/24 Valid Other IRR onlyRADB 672 100% 68
196.61.46.0/24 Valid Other IRR onlyRADB 669 99% 68
197.159.128.0/24 Valid Other IRR onlyRIPE-NONAUTH 669 99% 68
41.222.232.0/22 Valid RIR databaseAFRINIC 671 100% 68
41.222.232.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
41.222.233.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
41.222.234.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
41.222.235.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
196.61.32.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
196.61.33.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
196.61.34.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
196.61.35.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.61.36.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.61.37.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.61.38.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 68
196.61.39.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.61.40.0/24 Valid RIR databaseAFRINIC 669 99% 68
196.61.41.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.129.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.130.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.131.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.132.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.133.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.134.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.135.0/24 Valid RIR databaseAFRINIC 669 99% 68
197.159.136.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.137.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.138.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.139.0/24 Valid RIR databaseAFRINIC, RADB, RIPE-NONAUTH 669 99% 68
197.159.140.0/24 Valid RIR databaseAFRINIC, RADB, RIPE-NONAUTH 669 99% 68
197.159.141.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
197.159.142.0/24 Valid RIR databaseAFRINIC, RADB, RIPE-NONAUTH 669 99% 68

AS-SET

AS37012 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 18 are in fix.csv.

  • ROA: none2
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none196.61.32.0/20No ROA covers it. Add a ROA for AS37012, maxLength 20.672 of 673
ROA: none197.159.128.0/20No ROA covers it. Add a ROA for AS37012, maxLength 20.672 of 673
Route object: none196.61.42.0/24Route objects for it name AS328983. A route object for 196.61.32.0/20 with origin AS37012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37012 in the RIR database for the space.669 of 673
Route object: none196.61.43.0/24Route objects for it name AS328983. A route object for 196.61.32.0/20 with origin AS37012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37012 in the RIR database for the space.669 of 673
Route object: none196.61.44.0/24Route objects for it name AS328983. A route object for 196.61.32.0/20 with origin AS37012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37012 in the RIR database for the space.669 of 673
Route object: none196.61.45.0/24Route objects for it name AS328983. A route object for 196.61.32.0/20 with origin AS37012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37012 in the RIR database for the space.669 of 673
Route object: RIR196.61.47.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR196.61.46.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR197.159.128.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

41.76.25.0/24RADBNo ROA
41.77.68.0/22RADBNo ROA
102.36.183.0/24RADBNo ROA
102.130.98.0/24RADBNo ROA
102.135.188.0/24RADBNo ROA
102.141.228.0/22RADBNo ROA
196.11.206.0/23RADBNo ROA
197.159.136.0/22RADBNo ROA
197.159.143.0/24AFRINICNo 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.