bgpreport

Network · data from 2026-11-12

AS329580 The Cloud Network Limited

Registry name: The Cloud Network Limited - The Cloud Network Limited, GH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329580, 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.205.89.0/24 Valid Nonecovered by 102.205.88.0/23 41 6%low visibility 15
102.205.91.0/24 Valid Nonecovered by 102.205.90.0/23 41 6%low visibility 15
102.202.228.0/22 Valid RIR databaseAFRINIC 673 100% 66
102.205.88.0/22 Valid RIR databaseAFRINIC 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS329580: AS-CLOUDGHANA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS329580 isn't in the set, or no route object for AS329580 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS329580 in itNot covered
AS-CLOUDGHANA AFRINIC 1112 Yes 0

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

  • Route object: none2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none102.205.89.0/24No route object for it. A route object for 102.205.88.0/23 with origin AS329580 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329580 in the RIR database for the space.41 of 673
Route object: none102.205.91.0/24No route object for it. A route object for 102.205.90.0/23 with origin AS329580 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329580 in the RIR database for the space.41 of 673

Route objects not announced

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

102.202.228.0/23AFRINICValid
102.202.228.0/24AFRINICValid
102.202.229.0/24AFRINICValid
102.202.230.0/23AFRINICValid
102.202.230.0/24AFRINICValid
102.202.231.0/24AFRINICValid
102.205.88.0/23AFRINICValid
102.205.88.0/24AFRINICValid
102.205.90.0/23AFRINICValid
102.205.90.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.