INC-1163 SIEM log investigation

What to do

• Check whether your product depends on Imperva. 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 16m it lasted.

  Anything that failed between 2026-10-15 21:49 UTC and 2026-10-15 23:05 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 3

1. investigatingOct 15, 2026, 9:49 PM UTC

   We are currently investigating an issue with SIEM log data that may affect the accuracy of information reported for some customers. Our team is working to assess the impact and identify the appropriate corrective actions. The next update will be provided by 22:30 UTC.

   provider

2. identifiedOct 15, 2026, 10:36 PM UTC

   We have identified the source of the SIEM log data issue affecting the accuracy of information reported for some customers. Our teams are actively working to implement mitigation measures and restore normal service. The next update will be provided by 23:00 UTC.

   provider

3. resolvedOct 15, 2026, 11:05 PM UTC

   Mitigation measures have been implemented to address the SIEM log data issue. Our teams have confirmed the environment accuracy.

   provider

Corrections

None so far.

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