[INC-1148] Imperva Management API Degradation

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 20m it lasted.

  Anything that failed between 2026-10-01 11:27 UTC and 2026-10-01 11:48 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 1, 2026, 11:27 AM UTC

   We have identified a service degradation affecting the Imperva API. As a result, some customers attempting to download SIEM logs via the API may receive HTTP 502 errors. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. All customer websites remain 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. monitoringOct 1, 2026, 11:40 AM UTC

   A fix has been implemented and we are monitoring the results.

   provider

3. resolvedOct 1, 2026, 11:48 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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