Skip to main content
Imperva

[INC-1104]Imperva Management Portal Configuration Changes Issue

Degraded Lasted 14h 15m · started · Imperva's page

Level
confirmed
Worst impact
Degraded
Components
Cloud Security Management Configuration Changes, CDN and WAF Management
Down Index
23of 100

What to do

  • Check whether you use Imperva Cloud Security Management Configuration Changes, CDN and WAF Management. 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 14h 15m it lasted.

    Anything that failed between 2026-08-12 19:59 UTC and 2026-08-13 10:14 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 11

  1. investigating

    We have discovered a service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. Customer sites are still fully protected at this time. Technical teams are investigating. Further updates to follow.

    provider

  2. identified

    Technical teams have identified the underlying issue and are actively working on a fix to restore normal configuration publishing. The next update will be provided no later than 21:00 UTC.

    provider

  3. monitoring

    The technical team has applied a fix to address the issue, and the Publisher has returned to normal operation. Configuration changes are now being processed as expected, and the service has returned to a stable state. The team continues to monitor the system to ensure ongoing stability.

    provider

  4. identified

    During our ongoing monitoring, we observed another instance of delayed configuration publishing. The technical team is actively investigating and working on remediation. Customer sites remain protected, and we continue to closely monitor the service.

    provider

  5. identified

    Our technical teams are actively engaged and working to remediate the issue. We are continuing to monitor the affected services closely and will provide further updates as more information becomes available. Customer sites remain protected.

    provider

  6. identified

    Our technical teams continue to actively work on the issue affecting configuration publishing. Remediation efforts are underway, and we are closely monitoring the service to ensure a stable recovery. Customer sites remain protected. We will provide further updates as more information becomes available.

    provider

  7. identified

    Our technical teams remain actively engaged in addressing the configuration publishing issue. Remediation activities are ongoing, and we continue to closely monitor the service to ensure a stable and sustained recovery. Customer sites remain protected. We will continue to provide updates as further information becomes available.

    provider

  8. identified

    Our technical teams continue to actively work on the configuration publishing issue. Remediation is progressing in a controlled manner, with the team working to restore the processing of affected configurations. We are closely monitoring the service and validating the recovery as remediation activities continue. Customer sites remain protected. We will provide further updates as more information becomes available.

    provider

  9. identified

    Our technical teams continue to actively investigate the configuration publishing issue. Remediation and validation activities are ongoing, and the team is working to restore normal publishing operations while closely monitoring the service. Customer sites remain protected. We will continue to provide updates as more information becomes available.

    provider

  10. monitoring

    Technical teams have completed the necessary remediation, and configuration propagation through the Imperva Management Portal has returned to normal operating levels. The teams will continue to closely monitor the system to ensure ongoing stability. Further updates will be provided as they become available.

    provider

  11. resolved

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. 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-5c55937da1

Is Imperva still down?

No, this incident was resolved 2026-08-13 10:14 UTC. For Imperva's live state, see https://down.guide/imperva.

How long did it last?

14h 15m, from 2026-08-12 19:59 UTC to 2026-08-13 10:14 UTC, by the times Imperva posted.

What was affected?

Imperva named Cloud Security Management Configuration Changes, CDN and WAF Management.

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.