Is Imperva Down?

The incident causing delays with certain configuration changes has been resolved. Configuration processing remains at expected levels, and the service has remained stable following mitigation. We will continue to monitor service health as part of our normal operations. --- [2026-11-05T16:23:02.637Z] (monitoring) The incident causing delays with certain configuration changes has been mitigated. Configuration processing has returned to expected levels, and our teams are closely monitoring the service to ensure continued stability. --- [2026-11-05T10:30:29.370Z] (identified) We have made significant progress with our mitigation efforts, and service has improved across most affected locations. Some customers may continue to experience delays with certain configuration changes being applied in the Jakarta (JKT), Kuala Lumpur (KUL), and Manila (MNL) Points of Presence (PoPs). Additional mitigation activities for the remaining affected APAC locations are planned during regional off-hours to minimize potential customer disruption. We continue to monitor the service closely and will provide further updates as progress is made. --- [2026-11-04T23:52:13.443Z] (identified) Our phased mitigation efforts have significantly reduced the scope of the issue. A small portion of service capacity, approximately 5%, may continue to experience the issue and will be addressed during the next phase of remediation. We continue to monitor the service closely and will provide a further update before 08:00 UTC. --- [2026-11-04T15:23:46.394Z] (identified) Some customers may continue to experience delays when applying certain configuration changes. The issue remains limited in scope and does not affect all customers or configuration changes. Our teams are actively executing a phased mitigation plan to restore normal processing for the affected services. The phased plan will be applied during low traffic times in our PoPs to minimise any further disruption. We continue to monitor the service closely and will provide further updates as progress is made. The next update will be before 00:00 UTC. --- [2026-11-04T15:07:46.241Z] (investigating) We are investigating an incident where some customers may experience delays when applying certain configuration changes. Not all configuration changes or customers are affected. Our teams are actively investigating and we will provide further updates as more information becomes available. The next update will not be after 15:30 UTC --- [2026-11-04T15:00:19.140Z] (investigating) We are investigating an incident where some customers may experience delays when applying certain configuration changes. Not all configuration changes or customers are affected. Our teams are actively investigating and we will provide further updates as more information becomes available. The next update will not be after 15:30 UTC

The issue affecting access to www.imperva.com has been resolved. The website is operating normally, and our monitoring confirms service stability has been restored. We appreciate your patience while our teams worked to resolve the issue. --- [2026-11-04T09:38:58.036Z] (monitoring) The issue affecting access to www.imperva.com has been mitigated, and the website is responding normally. Our teams have observed improvements in service stability and are continuing to monitor performance to ensure a consistent and reliable experience. --- [2026-11-04T09:27:46.870Z] (identified) Mitigation efforts are ongoing as our teams continue working to address the issue and restore normal access to www.imperva.com. We will provide further updates as more information becomes available. --- [2026-11-04T09:16:02.598Z] (investigating) Our teams have identified the source of the degradation and are actively implementing the mitigation. We will continue to provide further updates as progress is made. --- [2026-11-04T09:07:54.262Z] (investigating) We have identified an issue causing intermittent access to **www.imperva.com**. Our teams are actively investigating and working to implement a fix. We will continue to monitor the situation and provide further updates as more information becomes available.

Maintenance on the Bangkok, Thailand data center will be performed on Tuesday, November 10th, 2026 at 18:00 UTC. We expect to complete the maintenance by Wednesday, November 11th, 2026 at 00:00 UTC. For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

As part of our commitment to building a future-facing network, Imperva recently launched our Next Generation Architecture in the DEL – New Delhi, India PoP with improved capacity, connectivity, and services. This PoP is replacing our currently operational PoP in NDL – New Delhi, India. Imperva will be migrating all services and customer traffic from our NDL PoP to our DEL PoP and decommissioning our NDL PoP during a scheduled maintenance window which will begin at 2026-11-11 at 17:00 UTC , completing by 2026-11-12 at 03:00 UTC. For Cloud WAF customers, Imperva will reroute traffic to an unaffected PoP in the region for the duration of the maintenance, with no expected interruption to Cloud WAF services. At the end of the maintenance, traffic will be serviced by the new PoP. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via an alternate connection such as GRE tunnels or Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. At the end of the maintenance, DDoS Protection traffic will be serviced by the new PoP. If Performance Monitoring is enabled on the connections, you will notice a change in the IP address of the PM servers that are sending ICMP echo messages. This might require you to modify ACL/firewall configurations to allow ICMP traffic from the new IPs. To learn more, see https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/performance-monitoring.htm