bgpreport

Network · data from 2026-11-12

AS327941 SimbaNET Malawi

Registry name: SIMBANET MALAWI LIMITED - SIMBANET MALAWI LIMITED, MW · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327941, 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.
196.11.80.0/21 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 670 100% 68
196.11.80.0/24 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 670 100% 68
196.11.81.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.11.82.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.11.83.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.11.84.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.11.85.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.11.86.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
196.11.87.0/24 No ROA RIR databaseAFRINIC, RIPE-NONAUTH 670 100% 68
2c0f:f510::/32 No ROA RIR databaseAFRINIC, RADB, RIPE-NONAUTH 636 100% 69

AS-SET

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

  • ROA: none10
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none196.11.80.0/21No ROA covers it. Add a ROA for AS327941, maxLength 21.670 of 673
ROA: none196.11.80.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.81.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.82.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.83.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.84.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.85.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.86.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none196.11.87.0/24No ROA covers it. Add a ROA for AS327941, maxLength 24.670 of 673
ROA: none2c0f:f510::/32No ROA covers it. Add a ROA for AS327941, maxLength 32.636 of 636

Route objects not announced

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

169.255.53.0/24RIPE-NONAUTHNo ROA
196.11.80.0/22RADBNo ROA
196.11.80.0/23RADBNo ROA
196.223.27.0/24AFRINICNo ROA
2c0f:eb00:1200::/40AFRINICInvalid: origin

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.