Network · data from 2026-11-12
AS3288 MOFET-AS Zipcom Communications LTD
Registry name: MOFET-AS Zipcom Communications LTD, IL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3288, 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.
| 192.115.88.0/24 | No ROA | Nonecovered by 192.115.88.0/21 | 673 100% |
| 192.115.90.0/24 | No ROA | Nonecovered by 192.115.88.0/21 | 673 100% |
| 192.115.91.0/24 | No ROA | Nonecovered by 192.115.88.0/21 | 673 100% |
| 192.115.93.0/24 | No ROA | Nonecovered by 192.115.88.0/21 | 673 100% |
| 192.115.94.0/24 | No ROA | Nonecovered by 192.115.88.0/21 | 673 100% |
| 192.115.97.0/24 | No ROA | Nonecovered by 192.115.96.0/21 | 673 100% |
| 192.115.98.0/24 | No ROA | Nonecovered by 192.115.96.0/21 | 673 100% |
| 192.115.100.0/24 | No ROA | Nonecovered by 192.115.96.0/21 | 673 100% |
| 192.115.101.0/24 | No ROA | Nonecovered by 192.115.96.0/21 | 673 100% |
| 192.115.102.0/24 | No ROA | Nonecovered by 192.115.96.0/21 | 673 100% |
| 192.115.88.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 192.115.96.0/21 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS3288 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 22 are in fix.csv.
- ROA: none12
- Route object: none10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.115.88.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.88.0/24 | No route object for it. A route object for 192.115.88.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.90.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.90.0/24 | No route object for it. A route object for 192.115.88.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.91.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.91.0/24 | No route object for it. A route object for 192.115.88.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.93.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.93.0/24 | No route object for it. A route object for 192.115.88.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.94.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.94.0/24 | No route object for it. A route object for 192.115.88.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.97.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.97.0/24 | No route object for it. A route object for 192.115.96.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.98.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.98.0/24 | No route object for it. A route object for 192.115.96.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.100.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.100.0/24 | No route object for it. A route object for 192.115.96.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.101.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.101.0/24 | No route object for it. A route object for 192.115.96.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.102.0/24 | No ROA covers it. Add a ROA for AS3288, maxLength 24. |
| Route object: none | 192.115.102.0/24 | No route object for it. A route object for 192.115.96.0/21 with origin AS3288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3288 in the RIR database for the space. |
| ROA: none | 192.115.88.0/21 | No ROA covers it. Add a ROA for AS3288, maxLength 21. |
| ROA: none | 192.115.96.0/21 | No ROA covers it. Add a ROA for AS3288, maxLength 21. |
Route objects not announced
Every route object with origin AS3288 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.