История сбоев Check Point

1. 12 июля 2026 г. в 05:47 UTCinvestigating

   We are currently investigating this issue.

2. 12 июля 2026 г. в 06:14 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 июля 2026 г. в 06:33 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 6 июля 2026 г. в 09:04 UTCinvestigating

   We are currently investigating reports of timeouts when loading Zero Trust Applications. This issue is being treated with the highest priority, and our engineering team is actively working to identify the cause. A further update will be provided as soon as more information is available.

2. 6 июля 2026 г. в 09:35 UTCinvestigating

   All current reports of ZTA issues are generated from Israel-1 region Investigation continues

3. 6 июля 2026 г. в 10:06 UTCmonitoring

   ISP in Israel-1 was swapped 20 mins ago Errors are not seen since in our logs, and customers reported issue is resolved We are monitoring closely

4. 6 июля 2026 г. в 11:15 UTCresolved

   Root cause seem to derive from global Cellcom ISP routing issues, also reported in downdetector.co.il ZTA were recovered when ISP on Israel-1 was switched from Cellcom. Some local users that uses Cellcom\Golan Tel may still face signing in or connecting issues. Until the issue is resolved *by the ISP*, users are encouraged to use a different ISP

Автоматический перевод официального обновления инцидента.

1. 5 июля 2026 г. в 12:27 UTCinvestigating

   We are currently investigating this issue.

2. 5 июля 2026 г. в 13:10 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 5 июля 2026 г. в 10:24 UTCinvestigating

   We are currently investigating the issue.

2. 5 июля 2026 г. в 11:27 UTCresolved

   This incident is resolved.

1. 1 июля 2026 г. в 11:00 UTCresolved

   Incident Duration: June 29, 08:00 UTC – June 30, 09:30 UTC (~26 hours) Affected Services: Datatube EU Production - West Europe region Affected Products: CloudGuard WAF, Playblocks, XDR ──────────────────────────── Overview On June 29–30, 2026, EU production Datatube services experienced a partial degradation affecting data ingestion in the West Europe region, a small portion of events experienced delayed processing during this window. ──────────────────────────── Customer Impact During the incident window, approximately ~0.2% of total EU ingestion events were affected across products. Customers using CloudGuard WAF, Playblocks, or XDR in the West Europe region may have experienced: - Delayed visibility of security events in dashboards and reports - Delayed data in queries covering the June 29–30 window ──────────────────────────── Incident Timeline (UTC) Jun 29 – 08:00 First customer reports received; investigation initiated immediately, cross-team investigation mobilized across infrastructure, networking, and product teams. Jun 29 – 10:00 First mitigation applied - provided temporary partial relief. Jun 29 – 13:30 Second mitigation applied, narrowing the root cause scope further, also provided temporary partial relief. Jun 29 – 18:00 Issue confirmed as affecting multiple products; joint investigation continued. Jun 29 – 21:15 Capacity expanded to stabilize the environment and protect against further degradation. Jun 30 – 05:00 Final diagnostic steps executed to isolate root cause precisely. Jun 30 – 09:30 Root cause confirmed and resolved; all services fully restored. The investigation required coordinated effort across multiple teams because early symptoms were consistent with several possible root causes. Each mitigation step both provided partial relief and helped narrow the diagnosis - this is standard practice to avoid introducing new risk while a production system is under stress. ──────────────────────────── Root Cause A misconfiguration in the EU gateway's communication protocols, which was dormant under normal operating conditions, was triggered by load introduced during routine maintenance. Once identified, the fix was straightforward and immediately effective. ──────────────────────────── Next Steps & Action Items 1. Audit and align protocol configurations across all regional gateways - to prevent recurrence in other regions. 2. Add capacity alerting on all regional gateways - to detect such anomalies before they cause customer impact. 3. Improve client-side monitoring to surface connection-level failures and latencies earlier. 4. Introduce stress testing for sensitive network components as part of the change process - validating configurations in an isolated, production-like environment before and after any change to catch hidden issues before they reach production.

1. 27 июня 2026 г. в 06:35 UTCinvestigating

   We are currently investigating this issue.

2. 27 июня 2026 г. в 07:20 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 июня 2026 г. в 07:50 UTCresolved

   This incident has been resolved.

1. 22 июня 2026 г. в 10:10 UTCresolved

   The Web SmartConsole on the Portal was unavailable for few hours, customers could work regularly with Installed SmartConsole or Streamed SmartConsole

1. 10 июня 2026 г. в 02:52 UTCinvestigating

   Due to Infrastructure issues inside Infinity Portal UK region, Infinity Portal customers in UK data residency are not able to login to the portal. We are working to mitigate that.

2. 10 июня 2026 г. в 02:54 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 июня 2026 г. в 03:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 10 июня 2026 г. в 03:37 UTCresolved

   This incident has been resolved.

1. 8 июня 2026 г. в 15:27 UTCinvestigating

   We are currently investigating this issue.

2. 8 июня 2026 г. в 16:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 8 июня 2026 г. в 16:26 UTCresolved

   This incident has been resolved.

1. 8 июня 2026 г. в 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 8 июня 2026 г. в 14:15 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 8 июня 2026 г. в 14:28 UTCresolved

   This incident has been resolved.

1. 8 июня 2026 г. в 12:10 UTCinvestigating

   We are currently investigating this issue.

2. 8 июня 2026 г. в 12:36 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 8 июня 2026 г. в 12:46 UTCresolved

   This incident has been resolved.

1. 7 июня 2026 г. в 16:50 UTCidentified

   Users may experience increased latency for security logs and events in the Infinity Portal.

2. 7 июня 2026 г. в 16:52 UTCidentified

   We are continuing to work on a fix for this issue.

3. 7 июня 2026 г. в 17:48 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 7 июня 2026 г. в 18:59 UTCresolved

   This incident has been resolved.

1. 7 июня 2026 г. в 12:40 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 7 июня 2026 г. в 14:08 UTCresolved

   This incident has been resolved.

1. 2 июня 2026 г. в 09:28 UTCidentified

   Some customers may experience delays in logs arrival time

2. 2 июня 2026 г. в 19:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 3 июня 2026 г. в 10:44 UTCresolved

   This incident has been resolved.

1. 1 июня 2026 г. в 13:36 UTCinvestigating

   We are currently investigating this issue.

2. 1 июня 2026 г. в 15:06 UTCresolved

   This incident has been resolved.

1. 2 июня 2026 г. в 09:25 UTCresolved

   Some customers may experience delay in logs arrival time

1. 1 июня 2026 г. в 10:58 UTCresolved

   Users were unable to access Spark gateways through the service. The issue was caused by recent infrastructure changes that unintentionally impacted RMD access, resulting in valid access requests being rejected. The issue was resolved at 04:25 AM UTC.

1. 31 мая 2026 г. в 11:48 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 31 мая 2026 г. в 11:48 UTCidentified

   We are continuing to work on a fix for this issue.

3. 31 мая 2026 г. в 11:56 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 31 мая 2026 г. в 12:05 UTCresolved

   This incident has been resolved.

1. 13 мая 2026 г. в 15:40 UTCinvestigating

   We are currently investigating this issue.

2. 13 мая 2026 г. в 17:29 UTCinvestigating

   Issue resolved

3. 13 мая 2026 г. в 17:32 UTCresolved

   This incident has been resolved.

1. 27 апреля 2026 г. в 14:12 UTCinvestigating

   We are currently experiencing partial service disruptions. The issue is under investigation.

2. 27 апреля 2026 г. в 15:52 UTCresolved

   This incident has been resolved.