Imperva Status

Identified: 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.

Identified: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Resolved: Service in the data center has been restored to normal.

Monitoring: 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.

Identified: 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.

Investigating: 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.

Investigating: 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.

Investigating: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Resolved: Service in the data center has been restored to normal.

Monitoring: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center.

The next update will be provided no later than 19:38 UTC.

Resolved: 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.

Monitoring: 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.

Monitoring: 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.

Investigating: 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.

Investigating: 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.

Resolved: 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.

Monitoring: 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.

Monitoring: 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.

Investigating: 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.

Investigating: 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.