[INC-1021] Imperva Security Event Delay Issue

Update timeline

1. investigating May 03, 2026, 10:48 AM UTC

   We have discovered a potential service degradation, affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. 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.

2. identified May 03, 2026, 11:18 AM UTC

   We have identified the source of the service degradation affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 11:48 AM 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.

3. investigating May 03, 2026, 11:49 AM UTC

   Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 12:18 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.

4. identified May 03, 2026, 11:57 AM UTC

   During the course of the investigation our teams found that the issue also affects the Attack Analytics and Security log delivery via SIEM solution in the APAC region. The next status update on this incident will be provided no later than 12:27 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.

5. identified May 03, 2026, 12:31 PM UTC

   During the course of the investigation our teams found that the issue also affects ABP and Attack Analytics log delivery via SIEM solution in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 13:00 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.

6. identified May 03, 2026, 01:02 PM UTC

   Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 13:30 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.

7. identified May 03, 2026, 01:30 PM UTC

   The teams have identified a component potentially causing the issue. They are currently working to mitigate it. The next Status Update on this Incident will be provided no later than 14:00 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.

8. identified May 03, 2026, 02:03 PM UTC

   Team are actively working to mitigate the issue. The next Status Update on this Incident will be provided no later than 14:33 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

9. identified May 03, 2026, 02:33 PM UTC

   Technical teams are continuing to work on a fix the issue. The next status update on this incident will be provided no later than 15:03 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.

10. identified May 03, 2026, 03:06 PM UTC

    The team has resolved the Security Events page issue on the Management Platform; however, Attack Analytics, threat alert emails, and SIEM integrations may still be impacted. The next Status Update on this Incident will be provided no later than 15:36 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.

11. monitoring May 03, 2026, 03:28 PM UTC

    The incident has been resolved, and all services have returned to normal operating levels. We will continue to monitor the situation closely. 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.

12. resolved May 03, 2026, 04:28 PM UTC

    The incident has been resolved and normal service levels have been restored. 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.