Check Point outage history

We are currently investigating this issue.

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

This incident has been resolved.

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.

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

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

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

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating the issue.

This incident is resolved.

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.

We are currently investigating this issue.

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

This incident has been resolved.

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

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.

We are continuing to investigate this issue.

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

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating this issue.

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

This incident has been resolved.

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

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

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

This incident has been resolved.

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

This incident has been resolved.

Some customers may experience delays in logs arrival time

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

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Some customers may experience delay in logs arrival time

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.

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

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

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

This incident has been resolved.

We are currently investigating this issue.

Issue resolved

This incident has been resolved.

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

This incident has been resolved.