Imperva Status

Identified: We have completed the work to replace the damaged equipment which we have identified, and our engineers are currently conducting final verification tests to confirm PoP readiness. Once all verification is completed, we will determine the time to reactivate the PoP. Further updates will be posted here as we have more information.

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

Identified: We are continuing to assess the extent of equipment damage in the LHR PoP, which will allow us to finalize a plan to restore the PoP to service. As this continues to be an extended incident, customers which utilize PoP-specific features such as Dynamic Content Acceleration ("Origin PoP") associated to LHR may wish to evaluate whether to designate an alternate PoP until LHR is restored.

Identified: It has been reported to Imperva that the service degradation which impacted the LHR POP is due to an environmental issue at the local 3rd party facility provider. During the service interruption, traffic should have shifted to other, redundant POP infrastructure after a brief period. Our facility provider and Imperva technical teams are continuing to evaluate the situation. At this time, there is no Estimated Time to Recovery for the LHR POP. Further updates to follow.

Identified: Due to an issue in the London (LHR) data center traffic remains 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 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.

Identified: We are still trying to fix the 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.

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.

Monitoring: A fix has been implemented and we are continuing to monitor in order to ensure that service has returned 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.

Identified: We have identified an issue in the London (LHR) 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 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.

Investigating: Technical teams are investigating a potential issue in the London (LHR) data center. 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.

Identified: Multiple subsea cable cuts in the Red Sea were identified in early September 2025 which have had a tangible impact to transcontinental Internet traffic. This could potentially cause an impact for Cloud WAF and Network DDoS mitigation services.

This incident is to communicate awareness of the situation as the subsea cable cuts are outside of Thales control. Thales Network Operations continues to monitor the situation and is consulting with our partners to provide updates on the situation as they become available. We currently do not have an expected time frame for resolution.

If you experience an impact to your service, please engage Thales Support for further investigation to determine if it is related to this incident.

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.

Identified: Multiple subsea cable cuts in the Red Sea were identified in early September 2025 which have had a tangible impact to transcontinental Internet traffic. This could potentially cause an impact for Cloud WAF and Network DDoS mitigation services.

This incident is to communicate awareness of the situation as the subsea cable cuts are outside of Thales control. Thales Network Operations continues to monitor the situation and is consulting with our partners to provide updates on the situation as they become available. We currently do not have an expected time frame for resolution.

If you experience an impact to your service, please engage Thales Support for further investigation to determine if it is related to this incident.

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.