bgpreport

Network · data from 2026-11-12

AS209425 KOI-AS KOI CLOUD SERVICES (Pty) Ltd

Registry name: KOI-AS KOI CLOUD SERVICES (Pty) Ltd, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209425, 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.
213.176.1.0/24 Valid None 2 0%low visibility 1
213.176.24.0/24 Valid None 2 0%low visibility 2
213.176.25.0/24 Valid None 2 0%low visibility 2
213.176.26.0/24 Valid None 2 0%low visibility 2
213.176.27.0/24 Valid None 2 0%low visibility 2
62.60.134.0/24 Valid RIR databaseRIPE 1 0%low visibility 2

AS-SET

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

  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none213.176.1.0/24No route object for it. Add a route object with origin AS209425 in the RIR database for the space.2 of 673
Route object: none213.176.24.0/24No route object for it. Add a route object with origin AS209425 in the RIR database for the space.2 of 673
Route object: none213.176.25.0/24No route object for it. Add a route object with origin AS209425 in the RIR database for the space.2 of 673
Route object: none213.176.26.0/24No route object for it. Add a route object with origin AS209425 in the RIR database for the space.2 of 673
Route object: none213.176.27.0/24No route object for it. Add a route object with origin AS209425 in the RIR database for the space.2 of 673

Route objects not announced

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

2001:3b80:e000::/36RIPEValid

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.