[INC-1134] Degradation of performance in Imperva Management Console

What to do

• Check whether you use Imperva Cloud Security Management Platform. 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 34m it lasted.

  Anything that failed between 2026-09-17 09:45 UTC and 2026-09-17 10:19 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. investigatingSep 17, 2026, 9:45 AM UTC

   We are investigating an issue affecting the performance of the Imperva Management Console (MY). Customers may encounter elevated latency, login failures, or degraded console performance. Our engineering teams are engaged and investigating the issue with high priority. We will continue to provide updates as our investigation progresses. The next update will not be later than 10:15 UTC.

   provider

2. monitoringSep 17, 2026, 9:56 AM UTC

   The issue affecting the Imperva Management Console (MY) has been resolved, and service has been restored. Customers should now be able to access and use the console normally. Our team will continue to closely monitor the service to ensure stability. The next update will be no later than 10:30 UTC

   provider

3. resolvedSep 17, 2026, 10:19 AM UTC

   The issue affecting the Imperva Management Console (MY) has been resolved. Service performance has returned to normal, and customers should no longer experience elevated latency, login issues, or general console degradation. We will continue to monitor the environment to ensure stability. Thank you for your patience while we worked to resolve this issue.

   provider

Corrections

None so far.

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