bgpreport

Network · data from 2026-11-12

AS56753 ZakatAS Zakat-House

Registry name: ZakatAS Zakat-House, KW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56753, 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.
195.254.170.0/24 Valid Other IRR onlyRADB 672 100% 67
195.254.170.0/23 Valid RIR databaseRIPE 672 100% 67
195.254.171.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: RIR195.254.170.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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