Historia awarii Check Point

1. 26 sierpnia 2026 07:56 UTCinvestigating

   we are currently investigating errors arriving from Threat Emulation on Europe site. this will have an affect on all requests arriving to Europe site. requests receives error from the site.

2. 26 sierpnia 2026 08:03 UTCmonitoring

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

3. 26 sierpnia 2026 08:05 UTCmonitoring

   we are starting to see requests arriving and handled normally. we are monitoring

4. 26 sierpnia 2026 08:31 UTCresolved

   This incident has been resolved.

1. 25 sierpnia 2026 17:34 UTCinvestigating

   We're investigating an issue causing slower response times. We'll share updates as we learn more.

2. 25 sierpnia 2026 18:36 UTCidentified

   We are continuing to investigate the issue, we do see some relief and response times are starting to get back to normal.

3. 25 sierpnia 2026 18:46 UTCmonitoring

   We identified an internal communication error between services and have applied a fix. We're now monitoring as things return to normal.

4. 25 sierpnia 2026 18:52 UTCresolved

   This incident has been resolved.

1. 25 sierpnia 2026 08:19 UTCinvestigating

   We are getting increased reports from customers unable to connect to gateways located in Israel-1 Data Center We are investigating the issue further and will provide an update shortly.

2. 25 sierpnia 2026 08:42 UTCmonitoring

   The primary ISP in the IL-1 DC (Bezeq) lost connectivity We failed over to the secondary ISP and connectivity to IL-1 resumed We are investigating the connectivity loss with Bezeq

3. 25 sierpnia 2026 09:05 UTCidentified

   Some gateways remain hung after the unexpected ISP failure We are looking into those specifically

4. 25 sierpnia 2026 09:31 UTCidentified

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

5. 25 sierpnia 2026 10:06 UTCmonitoring

   A fix have been implemented we are monitoring the results

6. 25 sierpnia 2026 10:46 UTCresolved

   This incident has been resolved. The IL-1 Data Center is now fully operational, and all affected gateways have been restored to normal function.

1. 3 sierpnia 2026 16:48 UTCresolved

   W tym czasie niesłusznie pojawiły się urządzenia odłączone. Pojawiły się błędy podczas próby tworzenia lub zapisywania ustawień - plan / brama. Brak wpływu na istniejące połączenia bram. Czas incydentu 7: 00-10: 00 UTC.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 29 lipca 2026 13:43 UTCinvestigating

   Obecnie badamy tę kwestię.

2. 29 lipca 2026 13:49 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 29 lipca 2026 13:57 UTCinvestigating

   Operacja jest kwestią sporną

4. 29 lipca 2026 14:40 UTCmonitoring

   Kwestia została znaleziona i przeprowadzona - monitorowanie

5. 29 lipca 2026 15:05 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 12 lipca 2026 05:47 UTCinvestigating

   We are currently investigating this issue.

2. 12 lipca 2026 06:14 UTCidentified

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

3. 12 lipca 2026 06:33 UTCresolved

   This incident has been resolved.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 6 lipca 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 lipca 2026 09:35 UTCinvestigating

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

3. 6 lipca 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 lipca 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

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 5 lipca 2026 12:27 UTCinvestigating

   We are currently investigating this issue.

2. 5 lipca 2026 13:10 UTCresolved

   This incident has been resolved.

1. 5 lipca 2026 10:24 UTCinvestigating

   We are currently investigating the issue.

2. 5 lipca 2026 11:27 UTCresolved

   This incident is resolved.

1. 1 lipca 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 czerwca 2026 06:35 UTCinvestigating

   We are currently investigating this issue.

2. 27 czerwca 2026 07:20 UTCmonitoring

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

3. 27 czerwca 2026 07:50 UTCresolved

   This incident has been resolved.

1. 22 czerwca 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 czerwca 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 czerwca 2026 02:54 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 czerwca 2026 03:35 UTCmonitoring

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

4. 10 czerwca 2026 03:37 UTCresolved

   This incident has been resolved.

1. 8 czerwca 2026 15:27 UTCinvestigating

   We are currently investigating this issue.

2. 8 czerwca 2026 16:11 UTCmonitoring

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

3. 8 czerwca 2026 16:26 UTCresolved

   This incident has been resolved.

1. 8 czerwca 2026 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 8 czerwca 2026 14:15 UTCmonitoring

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

3. 8 czerwca 2026 14:28 UTCresolved

   This incident has been resolved.

1. 8 czerwca 2026 12:10 UTCinvestigating

   We are currently investigating this issue.

2. 8 czerwca 2026 12:36 UTCmonitoring

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

3. 8 czerwca 2026 12:46 UTCresolved

   This incident has been resolved.

1. 7 czerwca 2026 16:50 UTCidentified

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

2. 7 czerwca 2026 16:52 UTCidentified

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

3. 7 czerwca 2026 17:48 UTCmonitoring

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

4. 7 czerwca 2026 18:59 UTCresolved

   This incident has been resolved.

1. 7 czerwca 2026 12:40 UTCidentified

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

2. 7 czerwca 2026 14:08 UTCresolved

   This incident has been resolved.

1. 2 czerwca 2026 09:28 UTCidentified

   Some customers may experience delays in logs arrival time

2. 2 czerwca 2026 19:33 UTCmonitoring

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

3. 3 czerwca 2026 10:44 UTCresolved

   This incident has been resolved.

1. 1 czerwca 2026 13:36 UTCinvestigating

   We are currently investigating this issue.

2. 1 czerwca 2026 15:06 UTCresolved

   This incident has been resolved.