Skip to main content
Imperva

[INC-1019] Imperva Management Portal Configuration Changes Issue

Degraded Lasted 26m · started · Imperva's page

Level
confirmed
Worst impact
Degraded
Components
Cloud Security Management Configuration Changes
Down Index
16of 100

What to do

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

    Anything that failed between 2026-04-27 11:04 UTC and 2026-04-27 11:31 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. investigating

    We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 11:34UTC. 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. monitoring

    Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. 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

  3. 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-799f41a4b3

Is Imperva still down?

No, this incident was resolved 2026-04-27 11:31 UTC. For Imperva's live state, see https://down.guide/imperva.

How long did it last?

26m, from 2026-04-27 11:04 UTC to 2026-04-27 11:31 UTC, by the times Imperva posted.

What was affected?

Imperva named Cloud Security Management Configuration Changes.

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.