Imperva Outage History

Imperva experienced traffic degradation in their Dusseldorf, Germany (DUS) data center for 7.1 hours. Customer traffic was rerouted through an alternate data center in the region, causing some increased latency during the incident. The issue was fixed and service was restored to normal operation.

Imperva experienced a 10.9-hour outage affecting their certificate issuance process due to an issue with their upstream certificate authority provider, preventing customers from ordering or issuing new certificates. Existing certificates and active services remained unaffected throughout the incident. The issue was resolved after engineering teams worked with the certificate authority provider to restore full certificate ordering and issuance functionality.

Imperva experienced a data center issue in Seoul, South Korea that lasted 2.8 hours and also affected the Tokyo region. Traffic was automatically rerouted through alternate data centers in the region, causing increased latency for customers during the incident. The issue was resolved with a fix implementation, and service was restored to normal operations in the Seoul data center.

Imperva experienced a technical issue in their Tokyo, Japan (TKO) data center that lasted 20.2 hours. As a precautionary measure, the TKO Point of Presence (PoP) was bypassed and customer traffic was rerouted through alternate PoPs to maintain service stability. The issue was resolved with a fix implemented and traffic restored to the Tokyo data center, with service returning to normal operations.

Imperva experienced an issue at their Chicago 2, IL data center that required traffic to be rerouted through alternate regional data centers, causing increased latency for customers. The data center was kept in bypass mode for approximately 7.5 hours to maintain service stability, with repairs conducted during off-peak hours. Service was fully restored to normal operations after implementing a fix and monitoring the resolution.

Imperva experienced a major incident where cache purge requests were not working properly, causing customer websites to display outdated or cached content for 5.7 hours. The engineering team identified the root cause and implemented a fix to restore normal cache purge functionality. The issue was fully resolved after ongoing remediation efforts.

Imperva's Attack Analytics service experienced a major incident lasting 7.4 hours where the page was returning errors and was inaccessible to users. Technical teams identified the root cause and implemented a fix that restored normal service functionality. The incident was fully resolved after a monitoring period to ensure service stability.

Imperva experienced a major incident affecting their API Security service where customers were unable to access the "My APIs" Inventory and upload/manage OAS/Swagger files. The technical teams identified the root cause and performed remedial actions to restore functionality. The incident was fully resolved after 2.7 hours with normal service levels restored.

Imperva experienced a connectivity issue at their Istanbul Turkey (SAW) data center caused by a third-party transit ISP problem that lasted 12.3 hours. Traffic was automatically rerouted through an alternate regional data center to maintain service availability, though customers experienced increased latency during this period. The issue was resolved after the ISP fixed the connectivity problem and normal routing was restored.

Imperva experienced a technical issue at their Tokyo, Japan (TKO) data center that required bypassing the Point of Presence as a precautionary measure for 5.8 hours. Customer traffic was automatically rerouted through alternate data centers with no service disruption to users. The issue was later determined to be an internal monitoring system problem, and normal service through the Tokyo data center was restored.