bgpreport

Network · data from 2026-11-12

AS36985 Global Micro Solutions

Registry name: Global Micro Solutions - Global Micro Solutions, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36985, 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.
41.77.56.0/22 Valid Nonecovered by 41.77.56.0/21 154 23% 44
41.77.60.0/22 Valid Nonecovered by 41.77.56.0/21 154 23% 44
41.223.172.0/23 Valid Nonecovered by 41.223.172.0/22 154 23% 44
41.223.174.0/23 Valid Nonecovered by 41.223.172.0/22 154 23% 44
154.66.64.0/21 Valid Nonecovered by 154.66.64.0/20 154 23% 44
154.66.72.0/21 Valid Nonecovered by 154.66.64.0/20 154 23% 44
41.77.56.0/21 Valid RIR databaseAFRINIC 672 100% 66
41.223.172.0/22 Valid RIR databaseAFRINIC, NTTCOM 672 100% 66
154.66.64.0/20 Valid RIR databaseAFRINIC 672 100% 66
2c0f:f150::/32 Valid RIR databaseAFRINIC 634 100% 67

AS-SET

AS36985'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 7 are in fix.csv.

  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none41.77.56.0/22No route object for it. A route object for 41.77.56.0/21 with origin AS36985 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36985 in the RIR database for the space.154 of 673
Route object: none41.77.60.0/22No route object for it. A route object for 41.77.56.0/21 with origin AS36985 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36985 in the RIR database for the space.154 of 673
Route object: none41.223.172.0/23No route object for it. A route object for 41.223.172.0/22 with origin AS36985 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36985 in the RIR database for the space.154 of 673
Route object: none41.223.174.0/23No route object for it. A route object for 41.223.172.0/22 with origin AS36985 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36985 in the RIR database for the space.154 of 673
Route object: none154.66.64.0/21No route object for it. A route object for 154.66.64.0/20 with origin AS36985 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36985 in the RIR database for the space.154 of 673
Route object: none154.66.72.0/21No route object for it. A route object for 154.66.64.0/20 with origin AS36985 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36985 in the RIR database for the space.154 of 673

Route objects not announced

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

154.66.66.0/24AFRINICValid

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.