bgpreport

Network · data from 2026-11-12

AS213302 Zetox Tawfiq Mhamid

Registry name: Zetox Tawfiq Mhamid, IL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213302, 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.
2a06:9801:800::/40 No ROA RIR databaseRIPE 3 0%low visibility 3
2a06:9801:d00::/40 No ROA RIR databaseRIPE 3 0%low visibility 3
2a06:de01:800::/38 No ROA RIR databaseRIPE 3 0%low visibility 3
2a10:ccc7:3c00::/38 No ROA RIR databaseRIPE 3 0%low visibility 3
2a06:9801:2000::/36 Valid RIR databaseRIPE 3 0%low visibility 3
2a10:fa80:9000::/36 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS213302 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 6 are in fix.csv.

  • ROA: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a06:9801:800::/40No ROA covers it. Add a ROA for AS213302, maxLength 40.3 of 636
ROA: none2a06:9801:d00::/40No ROA covers it. Add a ROA for AS213302, maxLength 40.3 of 636
ROA: none2a06:de01:800::/38No ROA covers it. Add a ROA for AS213302, maxLength 38.3 of 636
ROA: none2a10:ccc7:3c00::/38No ROA covers it. Add a ROA for AS213302, maxLength 38.3 of 636

Route objects not announced

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

2a0f:85c1:baa::/48RIPENo ROA
2a0f:85c1:be0::/44RIPENo 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.