bgpreport

Network · data from 2026-11-12

AS329530 Savanna Fibre (Tanzania) Ltd

Registry name: Savanna Fibre (Tanzania) Ltd - Savanna Fibre (Tanzania) Ltd, TZ · PeeringDB

10IPv4 routes 100.0% RPKI valid · 30.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 7 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS329530, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS329530, 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.202.72.0/24 Valid Nonecovered by 102.202.72.0/22 673 100% 66
102.202.73.0/24 Valid Nonecovered by 102.202.72.0/22 673 100% 67
102.202.74.0/24 Valid Nonecovered by 102.202.72.0/22 673 100% 67
102.202.75.0/24 Valid Nonecovered by 102.202.72.0/22 673 100% 66
102.205.248.0/24 Valid Nonecovered by 102.205.248.0/22 673 100% 67
102.205.250.0/24 Valid Nonecovered by 102.205.248.0/22 673 100% 66
102.205.251.0/24 Valid Nonecovered by 102.205.248.0/22 673 100% 67
102.205.249.0/24 Valid Other IRR onlyRADB 673 100% 66
102.202.72.0/22 Valid RIR databaseAFRINIC 673 100% 66
102.205.248.0/22 Valid RIR databaseAFRINIC 673 100% 66
2c0f:5cc0::/32 Valid RIR databaseAFRINIC 636 100% 67

AS-SET

AS329530'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 8 are in fix.csv.

  • Route object: none7
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none102.202.72.0/24No route object for it. A route object for 102.202.72.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: none102.202.73.0/24No route object for it. A route object for 102.202.72.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: none102.202.74.0/24No route object for it. A route object for 102.202.72.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: none102.202.75.0/24No route object for it. A route object for 102.202.72.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: none102.205.248.0/24No route object for it. A route object for 102.205.248.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: none102.205.250.0/24No route object for it. A route object for 102.205.248.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: none102.205.251.0/24No route object for it. A route object for 102.205.248.0/22 with origin AS329530 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329530 in the RIR database for the space.673 of 673
Route object: RIR102.205.249.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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