Skip to main content
Imperva

[INC-1018] Imperva Management Portal Configuration Changes Issue

Partial outage Lasted 10h 31m · started · Imperva's page

Level
confirmed
Worst impact
Partial outage
Components
Cloud Security Management Configuration Changes
Down Index
33of 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 10h 31m it lasted.

    Anything that failed between 2026-04-24 14:43 UTC and 2026-04-25 01: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 potential issue affecting My Publishing. 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. investigating

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

    The investigation into the service degradation affecting the Imperva Management Portal is ongoing, and the next update is scheduled for 16:30 UTC. 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

  4. investigating

    The team is actively investigating the service degradation impacting the Imperva Management Portal, with the next update expected at 17:05 UTC. 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

  5. investigating

    We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 18:05 UTC. 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

  6. investigating

    We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 19:06 UTC. 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

  7. investigating

    We are actively investigating a service degradation affecting the Imperva Management Portal. We will provide the next update as soon as more information becomes available. 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

  8. investigating

    The team is actively investigating the issue and processed approximately 30% of configuration change. The next update will be provided as soon as more information becomes available. 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

  9. identified

    We have identified the source of the service degradation that is causing delays in the propagation of recent configuration changes in the Imperva Management Portal. An additional 20% of configuration changes have been processed, reducing the overall delay. The next update will be provided at 00:47 UTC. 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

  10. 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

  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-8ea2cf1e9c

Is Imperva still down?

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

How long did it last?

10h 31m, from 2026-04-24 14:43 UTC to 2026-04-25 01:14 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.