bgpreport

Network · data from 2026-11-12

AS327840 RAIN GROUP HOLDINGS (PTY) LTD - RAIN GROUP HOLDINGS (PTY) LTD

Registry name: RAIN GROUP HOLDINGS (PTY) LTD - RAIN GROUP HOLDINGS (PTY) LTD, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327840, 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.
2c0e:8001:3000::/49 Invalid: origin None 1 0%low visibility 1
2c0e:8001:4000::/49 Invalid: origin None 1 0%low visibility 1
2c0e:8002:2000::/64 Invalid: origin None 1 0%low visibility 1
2c0e:8002:2000:1::/64 Invalid: origin None 1 0%low visibility 1
154.73.252.0/22 No ROA RIR databaseAFRINIC 671 100% 68

AS-SET

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

  • ROA: origin4
  • ROA: none1
  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin2c0e:8001:3000::/49ROAs covering it name AS37105, not AS327840. If AS327840 should announce it, add a ROA for AS327840.1 of 636
Route object: none2c0e:8001:3000::/49No route object for it. Add a route object with origin AS327840 in the RIR database for the space.1 of 636
ROA: origin2c0e:8001:4000::/49ROAs covering it name AS37105, not AS327840. If AS327840 should announce it, add a ROA for AS327840.1 of 636
Route object: none2c0e:8001:4000::/49No route object for it. Add a route object with origin AS327840 in the RIR database for the space.1 of 636
ROA: origin2c0e:8002:2000::/64ROAs covering it name AS37105, not AS327840. If AS327840 should announce it, add a ROA for AS327840.1 of 636
Route object: none2c0e:8002:2000::/64No route object for it. Add a route object with origin AS327840 in the RIR database for the space.1 of 636
ROA: origin2c0e:8002:2000:1::/64ROAs covering it name AS37105, not AS327840. If AS327840 should announce it, add a ROA for AS327840.1 of 636
Route object: none2c0e:8002:2000:1::/64No route object for it. Add a route object with origin AS327840 in the RIR database for the space.1 of 636
ROA: none154.73.252.0/22No ROA covers it. Add a ROA for AS327840, maxLength 22.671 of 673

Route objects not announced

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

154.73.252.0/24AFRINICNo ROA
154.73.253.0/24AFRINICNo ROA
154.73.254.0/24AFRINICNo ROA
154.73.255.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.