bgpreport

Network · data from 2026-11-12

AS203378 dzit General Authority of ZAKAT & TAX

Registry name: dzit General Authority of ZAKAT & TAX, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203378, 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.
185.117.128.0/24 No ROA RIR databaseRIPE 673 100% 67
185.117.128.0/23 No ROA RIR databaseRIPE 672 100% 67
185.117.129.0/24 No ROA RIR databaseRIPE 672 100% 67
2a06:8480:2::/47 No ROA RIR databaseRIPE 636 100% 67
2a06:8480::/48 No ROA RIR databaseRIPE 635 100% 68
2a06:8480:2::/48 No ROA RIR databaseRIPE 635 100% 67
2a06:8480::/47 No ROA RIR databaseRIPE 632 99% 67
2a06:8480:1::/48 No ROA RIR databaseRIPE 4 1%low visibility 4
2a06:8480:3::/48 No ROA RIR databaseRIPE 2 0%low visibility 2
37.216.202.0/24 Valid None 670 100% 67
82.197.54.0/24 Valid RIR databaseRIPE 673 100% 67
82.197.55.0/24 Valid RIR databaseRIPE 673 100% 70
185.117.130.0/23 Valid RIR databaseRIPE 673 100% 67
185.117.130.0/24 Valid RIR databaseRIPE 673 100% 67
185.117.131.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS203378 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 11 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.117.128.0/24No ROA covers it. Add a ROA for AS203378, maxLength 24.673 of 673
ROA: none185.117.128.0/23No ROA covers it. Add a ROA for AS203378, maxLength 23.672 of 673
ROA: none185.117.129.0/24No ROA covers it. Add a ROA for AS203378, maxLength 24.672 of 673
ROA: none2a06:8480:2::/47No ROA covers it. Add a ROA for AS203378, maxLength 47.636 of 636
ROA: none2a06:8480::/48No ROA covers it. Add a ROA for AS203378, maxLength 48.635 of 636
ROA: none2a06:8480:2::/48No ROA covers it. Add a ROA for AS203378, maxLength 48.635 of 636
ROA: none2a06:8480::/47No ROA covers it. Add a ROA for AS203378, maxLength 47.632 of 636
ROA: none2a06:8480:1::/48No ROA covers it. Add a ROA for AS203378, maxLength 48.4 of 636
ROA: none2a06:8480:3::/48No ROA covers it. Add a ROA for AS203378, maxLength 48.2 of 636
Route object: none37.216.202.0/24No route object for it. Add a route object with origin AS203378 in the RIR database for the space.670 of 673

Route objects not announced

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

185.117.128.0/22RIPENo 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.