Imperva Outage History

We have identified a service degradation affecting the Imperva API. As a result, some customers attempting to download SIEM logs via the API may receive HTTP 502 errors. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. All customer websites remain fully protected at this time. Technical teams are investigating. 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.

We continue to investigate the connectivity issue affecting the Madrid (MAD) PoP. Traffic remains rerouted through alternate PoPs as a mitigation measure while investigations continue. Current monitoring indicates network services remain stable and traffic is being successfully handled through alternate locations. The MAD PoP will be returned to service once investigation and validation activities have been completed. We will continue to provide updates as more information becomes available.

We are aware of an ABP issue affecting some users on Google Chrome 153 and above. Other browsers and versions are not currently affected. Customer sites are still fully protected by Advanced Bot Protection at this time. Our team is actively working on a fix. Technical teams are investigating. Further updates to follow.

Our teams continue to work on implementing mitigation measures to address the issue. Technical teams are still engaged and actively investigating. Customer sites are still fully protected by Advanced Bot Protection at this time.

One of our upstream providers is currently experiencing a major outage. We are contacting the provider to gather more information about the issue. As a mitigation, we have rerouted traffic away from the affected carrier at the impacted PoPs, which has mitigated customer impact. We will continue to closely monitor the environment to ensure ongoing service stability. Further updates will be provided as more information becomes available.

We are investigating an issue where some customers may receive SIEM logs from IP addresses that are no longer expected to be in use. Our teams are actively investigating the issue and working to identify the cause. We will provide further updates as more information becomes available.

We have identified the source of the issue affecting a subset of customers, resulting in SIEM logs being received from IP addresses that are no longer expected to be in use. Our teams are actively implementing mitigation measures to reduce customer impact and restore expected behavior. We will provide further updates as they become available.

We are currently investigating an issue that may cause intermittent DNS resolution failures for some customers. Our teams are actively investigating the issue and working to identify the cause and restore consistent DNS resolution. We will provide further updates as more information becomes available.

We continue to investigate intermittent DNS resolution issues that may affect a small number of requests. The issue is highly intermittent and remains limited in scope. Our teams are actively investigating the issue and working to identify the cause and ensure consistent DNS resolution. The next update on this issue will be shared no later than 20:10 UTC.

We are investigating an issue affecting the performance of the Imperva Management Console (MY). Customers may encounter elevated latency, login failures, or degraded console performance. Our engineering teams are engaged and investigating the issue with high priority. We will continue to provide updates as our investigation progresses. The next update will not be later than 10:15 UTC.

We have identified an issue in the Madrid, Spain 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. _ _ Further updates will be shared as more information becomes available.

Imperva has been alerted to the fact that there have been two major fiber cuts in North America. These fiber cuts are within the network of a major upstream carrier. A subset of customer traffic coming to or going from the Imperva network may transit this infrastructure and as a result of this issue, customers may experience connectivity issues, increased latency, or service degradation. We will provide further updates as more information becomes available. The next update will be before 20:50 UTC

We have identified an issue in the Rio de Janeiro, Brazi 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. Further updates will be shared as more information becomes available.

The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. Further updates will be shared as more information becomes available.

Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency. Further updates will be shared as more information becomes available.

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 07:30 UTC.

We have identified an issue in the Istanbul, Turkey (SAW ) 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 on the incident will be shared no later than 19:41 UTC

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.

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.

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.