bgpreport

Network · data from 2026-11-12

AS203905 GEWAPE CLOUD

Registry name: GEWAPE-AS GEWAPE CLOUD (K) LIMITED, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203905, 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.
102.129.218.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 66
102.129.217.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 66
102.215.225.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 68
2a13:9500:169::/48 Valid RIR databaseRIPE 635 100% 69
102.165.24.0/24 Valid RIR databaseAFRINIC, RADB 5 1%low visibility 5

AS-SET

AS203905's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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