bgpreport

Network · data from 2026-11-12

AS328950 Green Telecom Limited

Registry name: Green Telecom Limited - Green Telecom Limited, TZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328950, 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.218.72.0/24 No ROA Nonecovered by 102.218.72.0/22 671 100% 68
102.218.73.0/24 No ROA Nonecovered by 102.218.72.0/22 671 100% 68
102.218.74.0/24 No ROA Nonecovered by 102.218.72.0/22 671 100% 68
102.218.75.0/24 No ROA Nonecovered by 102.218.72.0/22 671 100% 68
102.218.72.0/22 No ROA RIR databaseAFRINIC 671 100% 68
2c0f:700::/32 No ROA RIR databaseAFRINIC 635 100% 67

AS-SET

AS328950'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 10 are in fix.csv.

  • ROA: none6
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none102.218.72.0/24No ROA covers it. Add a ROA for AS328950, maxLength 24.671 of 673
Route object: none102.218.72.0/24No route object for it. A route object for 102.218.72.0/22 with origin AS328950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328950 in the RIR database for the space.671 of 673
ROA: none102.218.73.0/24No ROA covers it. Add a ROA for AS328950, maxLength 24.671 of 673
Route object: none102.218.73.0/24No route object for it. A route object for 102.218.72.0/22 with origin AS328950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328950 in the RIR database for the space.671 of 673
ROA: none102.218.74.0/24No ROA covers it. Add a ROA for AS328950, maxLength 24.671 of 673
Route object: none102.218.74.0/24No route object for it. A route object for 102.218.72.0/22 with origin AS328950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328950 in the RIR database for the space.671 of 673
ROA: none102.218.75.0/24No ROA covers it. Add a ROA for AS328950, maxLength 24.671 of 673
Route object: none102.218.75.0/24No route object for it. A route object for 102.218.72.0/22 with origin AS328950 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328950 in the RIR database for the space.671 of 673
ROA: none102.218.72.0/22No ROA covers it. Add a ROA for AS328950, maxLength 22.671 of 673
ROA: none2c0f:700::/32No ROA covers it. Add a ROA for AS328950, maxLength 32.635 of 636

Route objects not announced

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