- Level
- confirmed
- Worst impact
- Degraded
- Components
- SIEM Logs
- Down Index
- 18of 100
What to do
Check whether you use Imperva SIEM Logs. 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 1h 38m it lasted.
Anything that failed between 2026-09-17 23:52 UTC and 2026-09-18 01:30 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 5
- investigating
We are investigating an issue where some customers may receive SIEM logs from IP addresses that are no longer expected to be in use. Our teams are actively investigating the issue and working to identify the cause. We will provide further updates as more information becomes available.
provider
- investigating
We have identified the source of the issue affecting a subset of customers, resulting in SIEM logs being received from IP addresses that are no longer expected to be in use. Our teams are actively implementing mitigation measures to reduce customer impact and restore expected behavior. We will provide further updates as they become available. The next update on the issue will be shared no later than 00:30 UTC.
provider
- identified
Our teams continue to work on implementing mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. Efforts remain focused on reducing customer impact and restoring expected behavior. We will provide additional updates as progress is made. The next update on the issue will be shared no later than 01:00 UTC.
provider
- monitoring
Our teams have successfully implemented mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. The observed impact has been mitigated, and services are operating as expected at this time. We are continuing to closely monitor the environment to ensure ongoing stability and confirm the effectiveness of the mitigation. The next update on the issue will be shared no later than 01:30 UTC.
provider
- resolved
Mitigation measures have been successfully implemented, and after a period of monitoring, our teams have confirmed that services are operating as expected with no further impact observed. This incident is now resolved. We apologize for any inconvenience and thank you for your patience while we worked to address this issue.
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-221e3a2e1c
Is Imperva still down?
No, this incident was resolved 2026-09-18 01:30 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
1h 38m, from 2026-09-17 23:52 UTC to 2026-09-18 01:30 UTC, by the times Imperva posted.
What was affected?
Imperva named SIEM Logs.
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.