Network · data from 2026-11-12
AS31997 ZONEALARM-COM - Check Point Software Technologies, Inc.
Registry name: ZONEALARM-COM - Check Point Software Technologies, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31997, 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.
| 209.97.115.0/24 | No ROA | Nonecovered by 209.97.112.0/20 | 672 100% |
| 172.102.144.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 172.102.145.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 172.102.146.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 172.102.147.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.208.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.209.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.210.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.211.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.212.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.214.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.215.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.216.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.220.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.221.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.87.222.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.113.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.116.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.117.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.118.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.119.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.120.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.121.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.122.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.123.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.124.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.125.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.126.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 209.97.127.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 2620:0:2a01::/48 | No ROA | RIR databaseARIN | 634 100% |
AS-SET
AS31997 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 39 are in fix.csv.
- ROA: none30
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.97.115.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| Route object: none | 209.97.115.0/24 | No route object for it. A route object for 209.97.112.0/20 with origin AS31997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31997 in the RIR database for the space. |
| ROA: none | 172.102.144.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 172.102.145.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 172.102.146.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 172.102.147.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.208.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.209.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.210.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.211.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.212.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.214.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.215.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.216.0/22 | No ROA covers it. Add a ROA for AS31997, maxLength 22. |
| ROA: none | 209.87.220.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.221.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.87.222.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.113.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.116.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.117.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.118.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.119.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.120.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.121.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.122.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.123.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.124.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.125.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.126.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 209.97.127.0/24 | No ROA covers it. Add a ROA for AS31997, maxLength 24. |
| ROA: none | 2620:0:2a01::/48 | No ROA covers it. Add a ROA for AS31997, maxLength 48. |
Route objects not announced
Route objects with origin AS31997 whose prefix no peer sees AS31997 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 172.102.148.0/24 | ARIN | No ROA |
| 172.102.149.0/24 | ARIN | No ROA |
| 172.102.150.0/24 | ARIN | No ROA |
| 172.102.151.0/24 | ARIN | No ROA |
| 209.87.208.0/20 | RADB | No ROA |
| 209.87.222.0/23 | RADB | No ROA |
| 209.97.112.0/20 | ARIN | No ROA |
| 2620:0:2a05::/48 | ARIN | No 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.