Imperva 中断历史

1. 2026年8月19日 UTC 22:17investigating

   我们在墨西哥克雷塔罗数据中心发现了一个问题。 交通正通过该区域的一个备用数据中心进行改道。 客户在改道的时间段内可能会遇到一些暂时性. 下起事件最新消息将在协调世界时22:45之前分享

2. 2026年8月19日 UTC 22:40identified

   我们正与该区域的上游提供者发生问题。 为了尽量减小客户的影响,受影响的PoP已经被绕过,流量正在通过另一个数据中心被改变. 客户在改道时可能会遇到一些更长时间的情况。 我们的小组正在积极监测局势,并与上游提供者合作。 一旦获得更多信息,我们将提供下一次最新情况.

3. 2026年8月20日 UTC 00:38identified

   我们继续与我们的上游提供者密切合作,他们承认这一问题,并正在积极努力恢复正常服务。 为了保持服务的连续性,受影响的活动方案将继续被绕过,而提供者则在努力恢复。 在此期间,客户可能面临更大的延迟。 一旦获得更多信息,我们将提供进一步的最新资料.

4. 2026年8月20日 UTC 04:39identified

   Queretaro, Mexico(QRO) PoP仍然被绕开,而我们的上游供应商则继续致力于服务恢复. 一旦获得更多信息,我们将提供下一次最新情况.

5. 2026年8月20日 UTC 06:37identified

   我们的一个上游供应商现已恢复服务,通过该供应商的连通性恢复在线。 目前正在与其余的上游供应商合作,以恢复全面连接。 随着恢复活动的继续进行,QRO PoP仍然被绕开。 一旦获得更多信息,我们将提供进一步的最新资料.

6. 2026年8月20日 UTC 06:55identified

   我们的一个上游供应商现已恢复服务,通过该供应商的连通性恢复在线。 目前正在与其余的上游供应商合作,以恢复全面连接。 随着恢复活动的继续进行,QRO PoP仍然被绕开。 一旦获得更多信息,我们将提供进一步的最新资料

7. 2026年8月20日 UTC 10:37monitoring

   受波及的QRO PoP恢复了交通,并拆除了绕道. 上游提供商继续监测先前报告的网络问题,服务此时保持稳定并运作. 我们正在密切监测业绩和连通性,以确保持续稳定,并将在必要时提供进一步的最新资料.

8. 2026年8月20日 UTC 11:16resolved

   通过 " 快速恢复方案 " 影响连通性的问题已经得到解决。 在确认稳定网络条件后,已恢复了QRO PoP的交通,并拆除了绕行道. 我们在恢复后继续监测服务,不再观察任何影响。 这一事件现在已经得到解决。 我们感谢你在我们努力恢复正常行动时的耐心.

自动翻译自官方事件更新。

1. 2026年8月19日 UTC 03:04monitoring

   我们发现了影响法兰克福(HHN)数据中心问题的服务退化,这可能导致客户失去连通性、断断续续的包裹损失和/或超过预期的服务延迟。 PoP恢复服务,减轻了对客户的影响.

2. 2026年8月19日 UTC 03:55resolved

   技术小组通过持续监测实施了必要的修复、完成了验证活动并确认了服务稳定性。 所有服务正常运行。 邮电局已全面运作并准备就绪。 我们赞赏你在整个事件中的耐心和理解.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 16:53investigating

   我们已查明一个条件,即从WDC PoP的代理服务器中获取流量的客户源子正在经历非最佳的路由。 在这种情况下,从原产地获取途径APAC地区而不是美国东部的特定第三方CDN网络,这增加了原产地获取的延迟性,最终降低了网站访问的性能. 在我们与第三方CDN合作纠正其地理定位路线信息的同时,我们正在探索我们设备内部潜在的绕行办法,以取代目前存在的不理想路线。 一旦获得更多信息,我们将提供进一步的最新资料.

2. 2026年8月13日 UTC 17:55investigating

   我们正在积极探索潜在的缓解办法,以解决路线不理想的问题并减少对受影响来源的交通的影响。 与此同时,我们正同第三方提供者合作,解决潜在的地理定位问题。 一旦获得更多信息,我们将提供进一步的最新资料.

3. 2026年8月13日 UTC 20:16investigating

   我们同第三方CDN供应商确认,他们已开始进行配置更新工作,以纠正路线不理想的情况,在部署全球之前,ETA最多2周。 与此同时,我们继续探索减轻影响的步骤,我们也许能够在每个客户的基础上对受影响的网站实施这些措施.

4. 2026年8月13日 UTC 21:12identified

   我们确认了一项解决办法,该办法减轻了路由不理想的情况,并且可以在继续等待第三方CDN供应商永久解决的同时,根据每个客户的要求执行受影响的网站.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 08:22investigating

   我们正在调查一个影响交通的问题 到达我们的青年(加拿大蒙特利尔) PoP。 客户可能遇到连通性问题、增加延迟或服务中断,因为交通经过此地。 我们的小组正在积极调查这一问题并努力查明根源。 一旦获得更多信息,我们将提供进一步的最新资料。 下一次更新将在协调世界时08:51之前

2. 2026年8月13日 UTC 08:34monitoring

   我们缓解了影响YUL(加拿大蒙特利尔)方案的问题,将受影响的方案从服务中取消,并将交通改道到其他地点。 交通目前由其他邮局提供服务,服务已经稳定。 我们的小组继续调查影响青年团结组织的基础设施的问题的根本原因,并正努力使该方案恢复正常运作。 我们将继续密切监测环境,并随时提供进一步的最新资料。 下一次更新将不晚于协调世界时09:05.

3. 2026年8月13日 UTC 08:48monitoring

   交通目前由其他邮局提供服务,服务已经稳定。 我们的小组继续调查影响青年团结组织的基础设施的问题的根本原因,并正努力使该方案恢复正常运作。 我们将继续密切监测环境,并随时提供进一步的最新资料。 下一次更新将不晚于协调世界时09:18.

4. 2026年8月13日 UTC 09:29monitoring

   我们查明了影响YUL(加拿大蒙特利尔)《行动纲领》的问题的来源,并正在着手进行补救。 在完成补救可能需要较长时间的同时,通过替代存在点(PoPs)的换行途径使服务趋于稳定。 交通继续通过其他地点提供服务,目前我们没有观察客户的影响。 我们将继续努力使青年团结方案恢复正常运作,并将在获得更多信息后提供进一步的最新情况

5. 2026年8月14日 UTC 08:12monitoring

   我们查明了影响YUL(加拿大蒙特利尔)《行动纲领》的问题的来源,并继续努力进行补救。 服务保持稳定,因为交通是通过备用站点提供的。 我们最新预计的ETA恢复YUL PoP的正常运行时间是星期一. 我们将继续密切监测这项服务,并在获得更多信息后提供进一步的最新资料.

6. 2026年8月17日 UTC 05:44monitoring

   补救工作已接近完成,大部分所需工作现已完成。 在YUL PoP能够安全地重新启动之前,仅剩下少数最后活动. 与此同时,服务保持稳定,因为交通继续经由备用站点。 目前的目标是在星期一之前完成剩余活动并恢复YUL PoP的正常运行. 我们将继续密切监测这项服务,并随着工作的进展提供进一步的最新资料.

7. 2026年8月17日 UTC 10:49monitoring

   补救活动已经完成,YUL(加拿大蒙特利尔)方案已成功恢复并恢复服务。 交通再次通过YUL PoP正常服务. 我们正在继续密切监测环境,以确保稳定,并核实所有服务仍然充分运作。 目前,预计不会对客户产生影响。 一旦事件得到彻底解决,我们将提供最后的最新情况.

8. 2026年8月17日 UTC 13:17resolved

   影响YUL(蒙特利尔,加拿大)PoP的问题已经解决,PoP成功恢复正常运行. 交通再次通过YUL PoP服务,验证和监测证实,服务运行如期. 我们将继续监测环境,以确保持续稳定。 谢谢你在我们努力恢复全面服务时的耐心.

自动翻译自官方事件更新。

1. 2026年8月12日 UTC 19:59investigating

   We have discovered a service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. Customer sites are still fully protected at this time. Technical teams are investigating. Further updates to follow.

2. 2026年8月12日 UTC 20:31identified

   Technical teams have identified the underlying issue and are actively working on a fix to restore normal configuration publishing. The next update will be provided no later than 21:00 UTC.

3. 2026年8月12日 UTC 21:03monitoring

   The technical team has applied a fix to address the issue, and the Publisher has returned to normal operation. Configuration changes are now being processed as expected, and the service has returned to a stable state. The team continues to monitor the system to ensure ongoing stability.

4. 2026年8月12日 UTC 22:37identified

   During our ongoing monitoring, we observed another instance of delayed configuration publishing. The technical team is actively investigating and working on remediation. Customer sites remain protected, and we continue to closely monitor the service.

5. 2026年8月12日 UTC 23:30identified

   Our technical teams are actively engaged and working to remediate the issue. We are continuing to monitor the affected services closely and will provide further updates as more information becomes available. Customer sites remain protected.

6. 2026年8月13日 UTC 00:14identified

   Our technical teams continue to actively work on the issue affecting configuration publishing. Remediation efforts are underway, and we are closely monitoring the service to ensure a stable recovery. Customer sites remain protected. We will provide further updates as more information becomes available.

7. 2026年8月13日 UTC 01:31identified

   Our technical teams remain actively engaged in addressing the configuration publishing issue. Remediation activities are ongoing, and we continue to closely monitor the service to ensure a stable and sustained recovery. Customer sites remain protected. We will continue to provide updates as further information becomes available.

8. 2026年8月13日 UTC 02:41identified

   Our technical teams continue to actively work on the configuration publishing issue. Remediation is progressing in a controlled manner, with the team working to restore the processing of affected configurations. We are closely monitoring the service and validating the recovery as remediation activities continue. Customer sites remain protected. We will provide further updates as more information becomes available.

9. 2026年8月13日 UTC 03:45identified

   Our technical teams continue to actively investigate the configuration publishing issue. Remediation and validation activities are ongoing, and the team is working to restore normal publishing operations while closely monitoring the service. Customer sites remain protected. We will continue to provide updates as more information becomes available.

10. 2026年8月13日 UTC 05:40monitoring

    Technical teams have completed the necessary remediation, and configuration propagation through the Imperva Management Portal has returned to normal operating levels. The teams will continue to closely monitor the system to ensure ongoing stability. Further updates will be provided as they become available.

11. 2026年8月13日 UTC 10:14resolved

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

1. 2026年8月7日 UTC 17:08investigating

   We identified a brief issue impacting our Points of Presence (PoPs), which may have caused infrastructure tunnel disconnections and intermittent website timeouts for some customers. The issue has now recovered, and services are operating normally. Our teams are actively monitoring the platform to ensure continued stability.

2. 2026年8月7日 UTC 17:58investigating

   Services remain stable across all previously affected Points of Presence (PoPs). Our teams continue to closely monitor the environment and analyze the event to confirm the underlying cause and ensure the continued stability of our services.

3. 2026年8月7日 UTC 18:57monitoring

   A potential contributing factor has been identified. Services remain stable across all affected Points of Presence (PoPs), and no further issues have been observed since recovery. Our teams continue to closely monitor the environment to ensure ongoing service stability.

4. 2026年8月7日 UTC 19:50resolved

   The incident has been resolved, and services have remained stable across all affected Points of Presence (PoPs).

1. 2026年8月5日 UTC 11:56investigating

   We are currently investigating reports of a potential issue affecting the generation and/or delivery of real-time WAF alerts. Some customers may experience delays in receiving WAF alerts or observe that expected real-time notifications are not being triggered. We are actively assessing the scope and impact of the issue and will provide further updates as more information becomes available. WAF protection remains fully operational. This issue affects real-time alerts only and does not impact traffic inspection or policy enforcement. Our next update will be provided as soon as we have additional information to share.

2. 2026年8月5日 UTC 12:23identified

   We have identified the underlying cause of the issue affecting real-time WAF alerts. Our investigation indicates that the impact is limited to a subset of customers. WAF protection remains fully operational. This issue affects real-time alerting only and does not impact traffic inspection or policy enforcement. Our teams are working on mitigation and validation efforts. We will provide further updates as we make progress toward resolution. Our next update will be before 12:55 PM UTC

3. 2026年8月5日 UTC 12:35monitoring

   A fix has been implemented to address the issue affecting real-time WAF alerts, and we are observing recovery across impacted services. WAF protection remained fully operational throughout the incident. The issue was limited to real-time alerting and did not impact traffic inspection or policy enforcement. We are currently monitoring the environment to ensure alert delivery has returned to normal operation and that no further issues are observed. We will continue to provide updates as warranted.

4. 2026年8月5日 UTC 12:56resolved

   The issue affecting real-time WAF alerts has been resolved. Following the implementation of a fix and a period of monitoring, we have confirmed that real-time WAF alert delivery has returned to normal operation. WAF protection remained fully operational throughout the incident, and traffic inspection and policy enforcement were not impacted. We apologise for any inconvenience caused and appreciate your patience while we worked to resolve this issue.

1. 2026年7月29日 UTC 01:29investigating

   我们知道一个影响到全球支助电话系统的问题。 用户可能无法通过电话获得支持. 我们的小组正在积极调查这个问题,并努力尽快恢复服务。 我们为不便而道歉。 此事件的下一份状态更新将不迟于协调世界时02:00提供 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

2. 2026年7月29日 UTC 02:10investigating

   我们目前意识到影响我们支助电话系统的全球性问题。 因此,用户可能无法通过电话联系支持. 我们的小组正在积极调查这个问题,并努力尽快恢复服务。 我们对此可能造成的不便表示歉意。 关于这起事件的下一次更新将不迟于协调世界时02:40提供 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响

3. 2026年7月29日 UTC 03:07investigating

   我们目前正在调查有关影响我们使用支助电话系统的全球问题的报告。 此时,支持电话号码正常运行,用户应当能够通过电话联系支持. 鼓励客户利用客户门户网站提交相应程度的支助请求,以获得最快的援助,同时我们的团队继续监测服务稳定性。 有关此事件的下一次状态更新将不晚于协调世界时04:00提供 我们为任何不便表示歉意并感谢你的耐心。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响

4. 2026年7月29日 UTC 04:32identified

   这一问题已经确定,我们的小组正在积极采取纠正行动,同时监测恢复进展情况。 支持电话号码目前正常运行,用户应当能够通过电话联系支持. 鼓励客户利用客户门户网站提交相应程度的支助请求,以获得最快的援助,同时我们的团队继续监测服务稳定性。 一旦获得更多信息,将提供进一步的最新资料。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

5. 2026年7月29日 UTC 05:34monitoring

   我们的小组正在积极监测这项服务,以确保稳定和持续提供这些服务。 支持电话号码正常运行,用户应当能够通过电话联系支持. 客户可以继续使用客户门户网站,以适当的严厉程度提交支助请求,以获得最快的援助。 有关此事件的下一次状态更新将不晚于协调世界时06:00提供 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

6. 2026年7月29日 UTC 06:26monitoring

   我们的小组继续监测这项服务,以确保稳定和持续提供这些服务。 支持电话号码正常运行,用户可以通过电话联系支持. 客户可能继续利用客户门户网站提交相应程度的支助请求,以获得最快的援助。 本次事故的下一次状态更新将在协调世界时7:00之前提供. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

7. 2026年7月29日 UTC 07:10monitoring

   我们的小组继续监测这项服务,以确保稳定和持续提供这些服务。 支持电话号码正常运行,用户可以通过电话联系支持. 客户可能继续利用客户门户网站提交相应程度的支助请求,以获得最快的援助。 将在协调世界时11:00之前提供这一事件的下一次状态更新. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态.

8. 2026年7月29日 UTC 08:39resolved

   技术小组通过持续监测,实施了所需的修复措施,完成了验证活动并确认了服务稳定性。 我们赞赏你在整个事件中的耐心和理解。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

自动翻译自官方事件更新。

1. 2026年7月27日 UTC 06:09investigating

   我们正在调查影响支助车票系统的潜在问题。 客户可能会遇到进入支助门户的问题。 我们的技术小组正在积极调查这一问题。 有关该问题的下一份最新情况将不迟于协调世界时6:39分享.

2. 2026年7月27日 UTC 06:49investigating

   我们的团队正在积极努力恢复使用支持出票系统。 在这项工作进行期间,遇到进入支助门户的问题的客户可通过拨打+1 410 469 1651电话,向我们的支助小组提供紧急援助。 谢谢你在我们努力解决这个问题时的耐心.

3. 2026年7月27日 UTC 07:45monitoring

   阻止一些客户登入客户支助门户的问题已经解决。 技术小组已完成了补救行动,门户已恢复正常运作。 我们正在继续监测这项服务,以确保稳定,并将在监测完成后提供最后最新情况.

4. 2026年7月27日 UTC 08:32resolved

   阻止一些客户登入客户支助门户的问题已完全解决。 技术小组实施了纠正行动并证实正常的登录功能已经恢复。 客户支助门户正常运行,没有观察到对客户的进一步影响。 我们为不便而道歉,并感谢你在我们努力解决这一问题时的耐心。 事件现已结束.

自动翻译自官方事件更新。

1. 2026年7月17日 UTC 05:06identified

   我们在里约热内卢的布拉齐数据中心发现了一个问题。 交通正通过该区域的一个备用数据中心进行改道。 客户在改道的时间段内可能会遇到一些暂时性. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

2. 2026年7月17日 UTC 06:06identified

   该小组正在继续努力解决这一问题。 为保持服务可用性,正在通过该区域的一个备用数据中心对交通线路进行调整。 在这段时间里,顾客可能会经历更大的延迟,而调整路线仍然有效。 有关该问题的下一次最新情况将在协调世界时6:35之前分享。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

3. 2026年7月17日 UTC 06:41identified

   我们的团队正在积极努力解决这一问题。 为保持服务可用性,通过该区域的一个备用数据中心对交通线路进行了调整。 客户在临时路线不变时可能会有更大的延迟。 有关该问题的下一次最新情况将在协调世界时7:10之前分享。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

4. 2026年7月17日 UTC 07:14identified

   我们的小组正在积极调查和努力解决这一问题。 为保持服务可用性,通过本区域的备用数据中心临时调整了交通路线。 在这段时间里,顾客可能会有更大的耐性。 我们将不晚于协调世界时7:45提供下一次最新情况。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

5. 2026年7月17日 UTC 07:46identified

   我们的小组在路线基础设施中确定了一个硬件问题,并正同供应商积极合作,以排除和解决这一问题。 为保持服务可用性,继续通过该区域的一个备用数据中心临时调整交通线路。 客户可能会继续经历更大的延迟,而这种临时路线仍然在原地。 有关该问题的下一次更新将在协调世界时8:15之前分享。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

6. 2026年7月17日 UTC 08:24identified

   我们正同硬件供应商积极合作来解决这个问题。 为保持服务可用性,正在通过该区域的一个备用数据中心对交通线路进行调整。 在这段时间里,顾客可能会经历更大的延迟,而调整路线仍然有效。 下一次更新预计于UTC下午4:00左右进行. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

7. 2026年7月17日 UTC 15:25identified

   我们与硬件供应商合作解决了根本问题。 根据目前的评估和成功的健康检查,该团队已安排于协调世界时2026年7月18日03:00重新启动受影响的PoP. 为了保持服务可用性,继续通过该区域的一个备用数据中心调整交通路线。 在这段时间里,顾客可能会经历更大的延迟,而调整路线仍然有效。 这次事件的下一份最新消息将不迟于协调世界时2026年7月18日03:15提供.

8. 2026年7月18日 UTC 05:35monitoring

   技术团队成功启动"PoP",交通恢复巴西里约热内卢"PoP". 目前正在进行核查测试和持续监测,以验证稳定性并证实活动方案已充分运作并可以使用。 将在协调世界时6:03之前提供有关这一事件的下一次最新状况。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

9. 2026年7月18日 UTC 06:30resolved

   技术小组通过持续监测,实施了所需的修复措施,完成了验证活动并确认了服务稳定性。 所有服务正常运行,PoP已完全恢复正常运行. 我们赞赏你在整个事件中的耐心和理解。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

自动翻译自官方事件更新。

1. 2026年7月10日 UTC 15:38investigating

   我们在南非约翰内斯堡数据中心发现了一个潜在的问题。 交通正通过该区域的一个备用数据中心进行改道。 客户在改道的时间段内可能会遇到一些暂时性. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

2. 2026年7月10日 UTC 16:04identified

   工作队已经查明了根本问题,并落实了一项解决办法。 为了确保业务连续性和验证服务稳定性,定于协调世界时23:00重新启动南非约翰内斯堡活动方案。 与此同时,交通正通过该区域的一个备用数据中心进行改道。 客户在改道时可能会遇到更长时间和间歇性超时的情况。 小组继续密切监测环境。 下一期关于该问题的更新将在协调世界时23:00之前分享.

3. 2026年7月10日 UTC 23:06identified

   我们的小组目前正在努力恢复受影响的存在点。 一旦成功恢复《行动纲领》,我们将提供另一个最新情况。 与此同时,正在通过区域内的备用数据中心对交通进行改道,以保持服务的可用性。 在此期间,顾客可能会经历更长时间和间歇性超时. 该小组继续密切监测环境,并正在积极致力于尽快恢复正常服务。 关于该问题的下一次更新将不迟于协调世界时23:36分享.

4. 2026年7月10日 UTC 23:10monitoring

   技术团队成功启用了PoP,交通恢复了南非约翰内斯堡PoP(QRA). 目前正在进行核查测试和持续监测,以验证稳定性并证实活动方案已充分运作并可以使用。 将在协调世界时23:40之前提供有关这一事件的下一次最新状况.

5. 2026年7月10日 UTC 23:38resolved

   技术小组通过持续监测实施了必要的修复、完成了验证活动并确认了服务稳定性。 所有服务正常运行。 邮电局已全面运作并准备就绪。 我们赞赏你在整个事件中的耐心和理解.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 21:40investigating

   技术小组正在调查Querétaro、MX(QRO)数据中心的一个潜在问题。 下一份关于这起事件的最新情况将在协调世界时10:11之前提供。 进一步更新。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

2. 2026年7月1日 UTC 22:52identified

   技术小组确定了影响Querétaro、MX(QRO)数据中心的一个问题。 作为一项预防措施,该方案将继续绕开,以确保服务稳定性,并计划在非高峰时段重新启动。 客流量继续通常通过替代的邮政局提供服务。 工程组继续参与调查。 本次事件的下一次状态更新将不迟于协调世界时05:00提供. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

3. 2026年7月2日 UTC 04:59identified

   技术小组确定了影响墨西哥Querétaro数据中心的一个问题。 为了保持服务稳定性,作为一项预防措施,活动方案将保持绕行模式,并计划在非高峰时段恢复。 客户流量继续不间断地通过另一个活动方案提供服务。 工程组正在积极调查这一问题并努力解决问题。 下一次状态更新将不迟于协调世界时07:00提供. 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

4. 2026年7月2日 UTC 07:15monitoring

   技术团队已成功启用了"PoP",并恢复了克雷塔罗,MX (QRO)数据中心的流量. 目前正在进行核查测试和持续监测,以验证稳定性并证实活动方案已充分运作并可以使用。 下一份关于这起事件的最新情况将在协调世界时8:13之前提供。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

5. 2026年7月2日 UTC 08:18resolved

   技术小组进行了必要的修复,完成了验证活动,并通过持续监测确认了服务稳定性。 所有服务正常运行。 邮电局全面开通运营,做好服务准备. 我们赞赏你在整个事件中的耐心和理解。 最新状况是主动监测和透明通报我们云服务状况的一个组成部分。 Imperva调查并赋予所有可能或不会影响服务提供情况的被检测出的事件一种状态. 如果服务中断,更新内容将包括对任何受影响区域的潜在影响.

自动翻译自官方事件更新。

1. 2026年6月11日 UTC 08:07investigating

   We are currently investigating increased latency affecting Imperva Cloud WAF protected sites. At this time, a portion of Imperva Cloud WAF customers may experience slower response times when accessing protected applications through Imperva. Our teams are actively investigating the cause and working to mitigate the impact. We will provide another update as more information becomes available. The next update will be at 08:36 UTC at the latest.

2. 2026年6月11日 UTC 08:15monitoring

   The issue causing increased latency for Imperva Cloud WAF protected sites has been mitigated. Service performance has returned to normal, and our teams are continuing to monitor closely to ensure continued stability. We will provide a final update once monitoring is complete. Please note service impact continued for approximately 15 minutes.

3. 2026年6月11日 UTC 08:39resolved

   This issue has been resolved. Our teams have confirmed that service performance for Imperva Cloud WAF protected sites has returned to normal and remained stable following mitigation. We will continue to monitor service health as part of our standard operational processes. Thank you for your patience while we worked to resolve this issue.

1. 2026年6月10日 UTC 18:53investigating

   We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next update on the issue will be provided no later than 19:23 UTC.

2. 2026年6月10日 UTC 19:24investigating

   The team continues to actively investigate the issue and work toward resolution. At this time, the impact is limited to customer access to the Management Portal. Customer websites and protection services remain fully operational and continue to be protected as expected. Next update on the issue will be provided no later than 19:54 UTC.

3. 2026年6月10日 UTC 19:54investigating

   Technical teams continue to actively investigate the issue. A potential contributing factor has been identified, and teams are currently working to validate and address it. Next update on the issue will be provided no later than 20:24 UTC.

4. 2026年6月10日 UTC 20:19identified

   We have identified the underlying cause of the issue and have applied a fix. The issue affected access to the Management Portal and a subset of API requests. We are seeing signs of recovery following the implementation of the fix, and our teams are actively validating service restoration across the impacted components. Next update on the issue will be provided no later than 20:50 UTC.

5. 2026年6月10日 UTC 20:42monitoring

   A fix has been successfully implemented, and services have been restored. Our teams have validated the recovery and are continuing to closely monitor the environment to ensure ongoing stability. Next update on the issue will be provided no later than 21:42 UTC.

6. 2026年6月10日 UTC 21:43monitoring

   Services remain stable following the implementation of the fix, and no further issues have been observed. Our teams will continue to closely monitor the environment for an extended period to ensure stability. Next update on the issue will be provided no later than 23:43 UTC.

7. 2026年6月10日 UTC 23:47monitoring

   Services remain stable, and no further issues have been observed. Our teams will continue to closely monitor the environment to ensure ongoing stability and verify that all services continue to operate as expected. Next update on the issue will be provided no later than 01:45 UTC on 11 June 2026.

8. 2026年6月11日 UTC 00:43resolved

   Monitoring has confirmed that services remain stable following the implementation of the fix and the completion of validation activities. No further issues have been observed.

1. 2026年6月3日 UTC 13:29identified

   We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Next update will be shared no later than 14:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. 2026年6月3日 UTC 13:59investigating

   Technical teams are continuing to working on a fix for the data center issue. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Next update will be shared no later than 14:30 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

3. 2026年6月3日 UTC 14:25monitoring

   A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. Next update will be shared no later than 14:56 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

4. 2026年6月3日 UTC 14:55resolved

   Service in the data center has been restored to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

1. 2026年6月3日 UTC 08:36investigating

   We are currently investigating an issue causing slowness on the Management Platform and Customers accessing onboarded sites from the APAC region may experience intermittent latency or delays when reaching their protected websites. Our teams are actively investigating the cause and working to restore normal service performance. We will provide additional updates as more information becomes available. Next update will be shared no later then 09:00 UTC.

2. 2026年6月3日 UTC 08:59identified

   We have identified the source of the service degradation causing slowness on the Management Platform and customers accessing onboarded sites from the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Next update will be shared no later then 09:30 UTC. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

3. 2026年6月3日 UTC 09:11monitoring

   Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Next update will be shared no later than 09:42 UTC. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

4. 2026年6月3日 UTC 09:40resolved

   The incident has been resolved and normal service levels have been restored for the Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

1. 2026年5月29日 UTC 13:24investigating

   We are investigating an issue in the New York 2, NY (EWR) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. The next update on the incident will be shared no later than 13:55 UTC.

2. 2026年5月29日 UTC 13:56investigating

   We continue to investigate the issue affecting the data center. Traffic remains rerouted through an alternate data center in the region while troubleshooting efforts are ongoing. The next update on the incident will be shared no later than 14:25 UTC.

3. 2026年5月29日 UTC 14:29investigating

   Investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting and analysis efforts. Teams are also investigating a recent increase in anomalous traffic to determine whether it is contributing to the observed behavior. Traffic continues to be rerouted through an alternate data center in the region to minimize customer impact while the root cause is being identified. The next update on the incident will be shared no later than 15:28 UTC.

4. 2026年5月29日 UTC 15:27investigating

   The investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting. Customer traffic continues to be served through an alternate PoP in the region to minimize impact while investigation and mitigation efforts continue. The next update on the incident will be shared no later than 16:27 UTC.

5. 2026年5月29日 UTC 16:25investigating

   The investigation remains ongoing, with multiple technical teams continuing to analyze the available data and evaluate potential contributing factors. Customer traffic continues to be served through alternate PoPs in the region to maintain service continuity while troubleshooting efforts and root cause analysis proceed. The next update on the incident will be shared no later than 17:25 UTC.

6. 2026年5月29日 UTC 17:28investigating

   Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active. Customer traffic continues to be served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed. Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information becomes available. The next update on the incident will be shared no later than 18:25 UTC.

7. 2026年5月29日 UTC 18:26investigating

   The investigation is still ongoing, with multiple technical teams actively reviewing available data and evaluating possible contributing factors. At this stage, there are no major developments to report, and troubleshooting activities continue. Customer traffic remains routed through alternate regional PoPs to maintain service continuity while mitigation efforts and root cause analysis are in progress. Next update will be shared no later then 19:26 UTC.

8. 2026年5月29日 UTC 19:37investigating

   We are still investigating an issue affecting one of our points of presence (EWR), which may cause intermittent connectivity or latency. Traffic has been rerouted through alternate locations to maintain service continuity while our teams continue working toward resolution. Next update will be shared no later then 20:07 UTC.

9. 2026年5月29日 UTC 20:20investigating

   Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center. The next update will be provided no later than 21:20 UTC.

10. 2026年5月29日 UTC 21:34investigating

    Our Network Engineering teams remain actively engaged in investigating and mitigating the connectivity issues impacting the New York 2, NY (EWR) data center. The next update will be provided no later than 22:34 UTC.

11. 2026年5月29日 UTC 22:46identified

    The technical teams have localized the problem and addressed it. The EWR PoP will remain bypassed until a scheduled maintenance window of 0400 to 0800 UTC on 1 June 2026. The next update will be provided following the reactivation of the EWR PoP.

12. 2026年5月29日 UTC 23:41identified

    Technical teams have identified and remediated the underlying issue. As a precautionary measure, the EWR PoP will remain bypassed while monitoring continues. An estimated timeline for reactivation will be provided shortly.

13. 2026年6月3日 UTC 11:01identified

    The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.

14. 2026年6月4日 UTC 04:31identified

    A fix has been implemented, and traffic has been restored to the data center. We are continuing to monitor to ensure that service has returned to normal. The next update will be provided no later than 05:01 UTC.

15. 2026年6月4日 UTC 05:00monitoring

    Technical team has successfully activated the PoP, and traffic has been restored to the EWR data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. The next Status Update on this Incident will be provided no later than 06:01 UTC.

16. 2026年6月4日 UTC 06:01monitoring

    The technical team identified and resolved an unexpected issue affecting range advertisements. Continuous monitoring is underway to validate service stability and will confirm full operational readiness of the PoP. The PoP is now active, and traffic has been restored to the EWR data center. The next Status Update on this Incident will be provided no later than 06:31 UTC.

17. 2026年6月4日 UTC 06:30resolved

    The technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. The PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident.

1. 2026年5月28日 UTC 19:08identified

   We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center. The next update will be provided no later than 19:38 UTC.

2. 2026年5月28日 UTC 19:24identified

   We have identified connectivity issues in our Vancouver, Canada (VAN) data center. Traffic is being re-routed to an alternate data center. The next update will be provided no later than 19:54 UTC.

3. 2026年5月28日 UTC 19:54identified

   We have identified intermittent connectivity issues affecting the Vancouver, Canada (VAN) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next update will be provided no later than 20:24 UTC.

4. 2026年5月28日 UTC 20:44identified

   As a precautionary measure, the Vancouver, Canada (VAN) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.

5. 2026年5月28日 UTC 21:55identified

   The technical teams have identified an issue affecting the Vancouver, Canada (VAN) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

6. 2026年5月29日 UTC 10:18monitoring

   A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. The next update will be provided no later than 11:18 UTC.

7. 2026年5月29日 UTC 11:05resolved

   Service in the data center has been restored to normal.

1. 2026年5月28日 UTC 18:09identified

   We have identified connectivity issues in our New York 2, NY (EWR). traffic is being re-routed to an alternate data-center. Next update will be shared no later then 18:37.

2. 2026年5月28日 UTC 18:23identified

   We have identified connectivity issues affecting our New York 2, NY (EWR) data center. Traffic is currently being re-routed to an alternate data center to minimize customer impact. The next update will be provided no later than 18:53 UTC.

3. 2026年5月28日 UTC 18:57identified

   We have identified intermittent connectivity issues affecting the New York 2, NY (EWR) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next update will be provided no later than 19:27 UTC.

4. 2026年5月28日 UTC 19:30identified

   Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center. The next update will be provided no later than 20:00 UTC.

5. 2026年5月28日 UTC 20:17identified

   As a precautionary measure, the New York 2, NY (EWR) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.

6. 2026年5月28日 UTC 21:54identified

   The technical teams have identified an issue affecting the New York 2, NY (EWR) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

7. 2026年5月29日 UTC 07:25monitoring

   A fix has been implemented, and customer traffic continues to be served normally through the New York 2, NY (EWR) PoP. We will continue to monitor the situation to ensure that service remains normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

8. 2026年5月29日 UTC 08:41investigating

   During monitoring, the team identified some abnormalities in the network. The engineering team is currently re-investigating the issue, and traffic is being re-routed to an alternate data center. Next update will be shared no later then 09:11 UTC.

9. 2026年5月29日 UTC 09:12investigating

   The investigation is ongoing, and technical teams continue to actively troubleshoot and analyze the issue to determine the underlying cause. Next update will be shared no later then 09:42 UTC.

10. 2026年5月29日 UTC 09:48investigating

    Investigation is ongoing. Technical teams continue to analyze the issue and validate findings. Customer traffic continues to be served normally through an alternate PoP. Next update will be shared no later then 10:18 UTC.

11. 2026年5月29日 UTC 10:16identified

    The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP. The next update will be provided no later than 10:46 UTC.

12. 2026年5月29日 UTC 10:57monitoring

    A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. The next update will be provided no later than 12:00 UTC.

13. 2026年5月29日 UTC 12:01resolved

    Service in the data center has been restored to normal.

1. 2026年5月27日 UTC 19:22investigating

   We have discovered a potential service degradation, affecting some ABP dashboards. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. Further updates to follow. Next update will be shared no later then 19:52 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

2. 2026年5月27日 UTC 20:04investigating

   Investigation and remediation activities are currently in progress, with engineering teams actively working to identify the root cause and restore service stability. Next update will be shared no later then 20:33 UTC.

3. 2026年5月27日 UTC 20:47monitoring

   Technical teams have implemented mitigation measures and the ABP dashboards are now operating normally. Teams will continue to closely monitor the environment, and further updates will be shared as they become available.

4. 2026年5月27日 UTC 22:23monitoring

   The technical team remains in the monitoring phase to ensure service stability and confirm that the issue does not recur. The next update will be shared no later then 22:53 UTC.

5. 2026年5月27日 UTC 22:52resolved

   No abnormalities were observed during the monitoring period. The incident has been resolved, and normal service levels have been fully restored for the Imperva Advanced Bot Protection service.