由于事件而减少服务
Outage重大事件
受影响的组件
Check Point Mobile Security - US RegionCheck Point Mobile Security - EU RegionCheck Point Mobile Security - IN Region
- identified
这一问题已经确定,一个解决办法正在实施之中.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
58 Check Point incidents · 2025年12月 — official updates, affected components, duration and resolution details.
这一问题已经确定,一个解决办法正在实施之中.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查这个问题
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
事件持续时间:9月27日02:30 - 06:00 UTC\(~3.5小时\) 受影响服务:DataTube - 加拿大、澳大利亚地区 ──────────────────────────── 概览 2026年9月27日,加拿大和澳大利亚地区的客户由于网络配置问题会影响与后端服务的连通性而出现服务中断. ──────────────────────────── 客户影响 加拿大和澳大利亚区域的客户无法摄取数据,导致服务恢复后积压并延迟摄入 ──────────────────────────── 根原因 中断的原因是网络配置发生变化,影响到区域基础设施各组成部分之间的连通性。 问题一经确定并纠正,便全面恢复服务. ──────────────────────────── 下一步 我们正在增加监测,以更早地发现这类问题,并审查我们的变革管理进程,以降低类似事件的风险。 我们对此可能造成的不便表示歉意.
自动翻译自官方事件更新。
我们目前正在调查欧洲站点的威胁模拟产生的错误。 这将影响所有到达欧洲站点的请求。 请求收到站点错误.
一项措施已经执行,我们正在监测结果.
我们开始看到 请求到达和处理正常。 我们正在监测
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个导致反应时间更慢的问题. 我们会分享最新消息,因为我们学到更多.
我们正在继续调查这一问题,我们确实看到一些缓解和反应时间开始恢复正常.
我们查明了各服务部门之间的内部沟通错误,并采用了固定办法。 我们现在正在监测 事情恢复正常.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们收到越来越多的来自客户的报告 无法连接到位于以色列一号数据中心的网关 我们正在进一步调查这一问题,并将很快提供最新情况.
IL-1DC(Bezeq)中的主要ISP失去连接 我们未能到达二级ISP 恢复与IL-1的连接 我们正在调查与贝泽克的连接损失
一些网关在ISP出乎意料的故障后仍然被吊起 我们正在调查这些
我们正在继续努力解决这个问题。
我们正监测结果
这一事件已经得到解决。 IL-1数据中心现在已全面运作,所有受影响的网关已恢复正常功能.
自动翻译自官方事件更新。
设备在这段时间里出现错误的断开 。 试图创建或保存设置时出现错误 - 计划/网关 。 对现有网关连接没有影响. 事件发生时间: UTC早上7: 00-10:00.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
行动有点问题 我们一直在调查
发现并处理了问题----监测
这一事件已经得到解决.
自动翻译自官方事件更新。
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.