Skip to main content
Imperva

[INC-1021] Imperva Security Event Delay Issue

Degraded Lasted 5h 40m · started · Imperva's page

Level
confirmed
Worst impact
Degraded
Components
Cloud Security Management Platform, SIEM Logs, Events Page, Attack Analytic
Regions
apac
Down Index
25of 100

What to do

  • Check whether you use Imperva Cloud Security Management Platform, SIEM Logs, Events Page, Attack Analytic in apac. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5h 40m it lasted.

    Anything that failed between 2026-05-03 10:48 UTC and 2026-05-03 16:28 UTC may need a replay.
  • Subscribe to Imperva's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=imperva works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Imperva 12

  1. investigating

    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.

    provider

  2. identified

    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.

    provider

  3. investigating

    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.

    provider

  4. identified

    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.

    provider

  5. identified

    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.

    provider

  6. identified

    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.

    provider

  7. identified

    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.

    provider

  8. identified

    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

    provider

  9. identified

    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.

    provider

  10. identified

    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.

    provider

  11. monitoring

    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.

    provider

  12. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-e4c3cbd811

Is Imperva still down?

No, this incident was resolved 2026-05-03 16:28 UTC. For Imperva's live state, see https://down.guide/imperva.

How long did it last?

5h 40m, from 2026-05-03 10:48 UTC to 2026-05-03 16:28 UTC, by the times Imperva posted.

What was affected?

Imperva named Cloud Security Management Platform, SIEM Logs, Events Page, Attack Analytic in apac.

What caused it?

Imperva hasn't published a root cause. If it does, it shows here.

Where does this come from?

Imperva's official status page, https://status.imperva.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.