Service in the data center has been restored to 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.
Posted May 15, 2026 - 00:32 UTC
Monitoring
A fix has been implemented and we are continuing to monitor in order to ensure that service has returned to 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.
Posted May 14, 2026 - 23:55 UTC
Update
Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 23:55 UTC. Further updates to follow.
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.
Posted May 14, 2026 - 22:55 UTC
Update
Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 22:55 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.
In the event of a service disruption, the update will include potential impacts to any affected region.
Posted May 14, 2026 - 21:55 UTC
Update
Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 21:55 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.
In the event of a service disruption, the update will include potential impacts to any affected region.
Posted May 14, 2026 - 21:25 UTC
Update
Technical teams are currently investigating the issue and will provide updates as more information becomes available. The next Status Update on this Incident will be provided no later than 21:25 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.
In the event of a service disruption, the update will include potential impacts to any affected region.
Posted May 14, 2026 - 20:55 UTC
Identified
We have identified the source of the issue in the data center. Technical teams are working on a fix. The next Status Update on this Incident will be provided no later than 20:51 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.
In the event of a service disruption, the update will include potential impacts to any affected region.
Posted May 14, 2026 - 20:21 UTC
Investigating
Technical teams are investigating a potential issue in the New Delhi (NDL), Mumbai (NAG) Data Center. The next Status Update on this Incident will be provided no later than 20:19 UTC. Further updates to follow.
Posted May 14, 2026 - 19:49 UTC
This incident affected: APAC PoPs (Mumbai 2, India (NAG), New Delhi, India (NDL)).