Imperva Outage History

The Imperva Management Portal experienced service degradation that affected the propagation of configuration changes for 29 minutes. Technical teams performed remedial actions to restore normal service levels and continued monitoring while the system cleared its backlog. The incident was fully resolved with normal service levels restored.

Imperva experienced a 10.5-hour service degradation that caused significant delays in the propagation of configuration changes through the Imperva Management Portal. The incident affected users' ability to have their portal configuration changes processed in a timely manner, creating a backlog that required gradual processing throughout the event. Technical teams identified the root cause, performed remedial actions, and restored normal service levels, allowing the remaining backlog to clear.

Imperva experienced a data center issue at their Santiago, Chile (STC) facility that affected services for 49 minutes. Technical teams investigated and implemented a fix to remediate the problem. All services were restored to normal operation and the incident was resolved.

Imperva experienced a service disruption affecting their API that lasted 1.8 hours. The technical teams identified the root cause and implemented a fix to restore normal service levels. The incident was resolved after a monitoring period to ensure stability.

Imperva's Cloud WAF dashboard experienced a service degradation where the Security Events section was not displaying data, though customer domains remained fully protected throughout the incident. The issue lasted 14.5 hours while technical teams investigated, deployed a fix, and restored data visibility. The incident was resolved after completing final validation and backfilling missing data from the affected period.

Imperva's Advanced Bot Protection service experienced a 17.5-hour outage caused by an issue with key rotation affecting authentication tokens, which resulted in customer websites returning browser errors to end users. Technical teams identified the root cause and deployed a fix through a phased global rollout to minimize impact on live traffic. Normal service levels were restored after extended monitoring confirmed system stability.

Imperva experienced a CWAF (Cloud Web Application Firewall) issue affecting multiple data centers including New York, Dallas, and Ashburn. The incident lasted 56 minutes before service was restored to normal operations across all affected regions.

Customer traffic processed through Imperva's Johannesburg, South Africa data center experienced higher than expected latency and packet loss due to an upstream provider issue outside of Imperva's network. Engineers resolved the incident by bypassing two impacted circuits and removing them from production, which stabilized traffic and restored normal service levels. The incident lasted 1.2 hours before services returned to stable operation.

Imperva experienced a 3.7-hour degradation affecting the GRE Performance Dashboard across multiple data centers, preventing the dashboard from correctly displaying statistics data. Customer domains remained fully protected throughout the incident, with only the monitoring dashboard functionality impacted. Technical teams identified the root cause, performed remedial actions to restore normal dashboard functionality, and confirmed no data was lost during the event.

Imperva experienced a data center issue at their New York 2, NY (EWR) facility that required traffic to be rerouted through an alternate data center, causing increased latency for customers during the 3.6-hour incident. The engineering team implemented a fix and restored normal traffic flow to the original data center. Service was fully restored to normal operations after a monitoring period to ensure stability.