bgpreport

Network · data from 2026-11-12

AS329647 SPRINT TANZANIA LIMITED

Registry name: SPRINT TANZANIA LIMITED - SPRINT TANZANIA LIMITED, TZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329647, 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.204.40.0/24 Valid Nonecovered by 102.204.40.0/22 671 100% 67
102.204.40.0/22 Valid RIR databaseAFRINIC 671 100% 67
102.204.41.0/24 Valid RIR databaseAFRINIC 671 100% 67
102.204.43.0/24 Valid RIR databaseAFRINIC 671 100% 67
102.204.42.0/24 Valid RIR databaseAFRINIC 669 99% 68
2c0f:3dc0::/32 Valid RIR databaseAFRINIC 634 100% 67

AS-SET

AS329647'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none102.204.40.0/24No route object for it. A route object for 102.204.40.0/22 with origin AS329647 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329647 in the RIR database for the space.671 of 673

Route objects not announced

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