Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Imperva Outage History

Every past Imperva outage tracked by IsDown, with detection times, duration, and resolution details.

There were 708 Imperva outages since November 2019. The 97 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 28, 2026

May 2026: [INC-1054] Connectivity issue in VAN POP.

Detected May 28, 2026 3:08 PM EDT · Resolved May 29, 2026 7:07 AM EDT · Duration about 16 hours

Imperva experienced connectivity issues at their Vancouver, Canada data center that lasted 16 hours. As a precautionary measure, the affected data center was bypassed and customer traffic was automatically rerouted to an alternate regional data center to maintain normal service. The technical teams implemented a fix and restored the Vancouver data center to normal operation after monitoring confirmed service stability.

Minor May 28, 2026

May 2026: [INC-1053] Connectivity issue in EWR

Detected May 28, 2026 2:09 PM EDT · Resolved May 29, 2026 8:03 AM EDT · Duration about 18 hours

Imperva experienced connectivity issues at their New York 2 (EWR) data center that lasted 17.9 hours. Customer traffic was automatically rerouted to alternate data centers throughout the incident, maintaining normal service availability. The technical teams identified and resolved the underlying connectivity problem, restoring normal operations to the affected data center.

Minor May 27, 2026

May 2026: [INC-1051] Imperva Management Portal ABP Dashboard Issue

Detected May 27, 2026 3:22 PM EDT · Resolved May 27, 2026 6:52 PM EDT · Duration about 3 hours

Imperva experienced a service degradation affecting some Advanced Bot Protection (ABP) dashboards for 3.5 hours, while customer sites remained fully protected throughout the incident. Technical teams implemented mitigation measures to restore normal dashboard functionality. The incident was resolved after a monitoring period confirmed no abnormalities and full service restoration.

Major May 22, 2026

May 2026: [INC-1049] Issue with creation of the site certificates.

Detected May 22, 2026 6:56 PM EDT · Resolved May 22, 2026 8:01 PM EDT · Duration about 1 hour

Imperva experienced a major incident affecting site certificate validation and creation. The issue impacted certificate-related services across the platform for approximately 1.1 hours. Technical teams identified the contributing factor and implemented a fix, restoring all services to normal operation.

Major May 19, 2026

May 2026: [INC-1045] Imperva Management Portal Configuration Changes Issue

Detected May 19, 2026 5:06 PM EDT · Resolved May 22, 2026 5:20 PM EDT · Duration 3 days

The Imperva Management Portal experienced a 72-hour service degradation where configuration changes were propagating with significant delays, affecting custom TLS certificate uploads, rule/policy modifications, and site configuration changes made through the management console. Technical teams identified the root cause and applied corrective actions, then worked through a substantial backlog of pending configuration changes over several days. The incident was fully resolved after all backlog processing was completed and normal configuration propagation was restored, with existing protections remaining operational throughout the incident.

Major May 16, 2026

May 2026: [INC-1042] Issues with Imperva Management Portal Configuration Changes

Detected May 16, 2026 4:50 PM EDT · Resolved May 17, 2026 2:40 AM EDT · Duration about 10 hours

The Imperva Management Portal experienced a 9.8-hour service degradation that prevented users from making configuration changes, though Cloud WAF protection remained active for applications. Technical teams identified the root cause and implemented fixes, but it took several hours to process the backlog of delayed publishing activities. The incident was fully resolved with normal service levels restored for configuration change propagation in the Management Portal.

Major May 15, 2026

May 2026: [INC-1040] Imperva Management Portal Login Issue

Detected May 15, 2026 3:22 PM EDT · Resolved May 15, 2026 7:32 PM EDT · Duration about 4 hours

Imperva experienced a major service degradation that prevented customers from logging into the Imperva Management Portal for 4.2 hours. Technical teams identified the root cause and performed remedial actions to restore access, with some intermittent issues with the publisher service during recovery. Normal service levels were fully restored, while Cloud WAF protection remained operational throughout the incident.

Minor May 15, 2026

May 2026: [INC-1038] Imperva Management Portal UI Performance Degradation

Detected May 15, 2026 4:17 AM EDT · Resolved May 15, 2026 7:43 AM EDT · Duration about 3 hours

The Imperva Management Portal experienced performance degradation in the India region, causing slow response times and login failures for users accessing the portal interface. Customer websites remained fully protected throughout the incident, with only the management interface affected. The issue was identified as ISP-related and resolved after technical teams implemented mitigation actions, restoring normal service levels after 3.4 hours.

Minor May 14, 2026

May 2026: [INC-1037] New Delhi, Mumbai Data Center Issue

Detected May 14, 2026 3:49 PM EDT · Resolved May 14, 2026 8:35 PM EDT · Duration about 5 hours

Imperva experienced a data center issue affecting their New Delhi and Mumbai facilities that lasted 4.8 hours. Technical teams identified the source of the problem and implemented a fix to restore normal service operations. The incident was resolved after a monitoring period to ensure service stability.

Minor May 14, 2026

May 2026: [INC-1036] Imperva Management Portal Slowness Issue

Detected May 14, 2026 1:26 PM EDT · Resolved May 14, 2026 2:29 PM EDT · Duration about 1 hour

The Imperva Management Portal experienced slowness issues that degraded customers' ability to use the service for approximately 1.1 hours. Technical teams performed remedial actions to restore normal service levels. The incident was fully resolved with the portal returning to normal operation.