- 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 9h 46m it lasted.
Anything that failed between 2026-05-16 20:50 UTC and 2026-05-17 06:36 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 18
- investigating
We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 21:20 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
- investigating
Engineering team actively investigating the ongoing service degradation impacting the Imperva Management Portal. The next update will be provided at 21:53 UTC.
provider
- investigating
The ongoing service degradation affecting the Imperva Management Portal remains under active investigation by the Engineering team. The next update will be communicated at 22:30 UTC.
provider
- investigating
Mitigation activities are still in progress, and teams continue working to restore service stability. The next update will be shared once a significant development is available.
provider
- investigating
The Imperva Management Portal will be unavailable for the next 30 minutes; however, all applications will remain protected by Cloud WAF. The next update will be communicated at 00:11 UTC.
provider
- investigating
Technical team continue to work on remediation activities to restore service stability. The next update will be communicated at 00:42 UTC.
provider
- investigating
Investigation is ongoing, and our technical teams are actively working to restore full service stability. The next update will be communicated at 01:15 UTC.
provider
- investigating
Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance. The next update will be communicated at 01:50 UTC.
provider
- investigating
The investigation is ongoing, and the team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance. The next update will be communicated at 02:20 UTC.
provider
- investigating
The investigation is ongoing, and the team continues to actively work towards remediation. The next update will be shared no later than 02:53 UTC.
provider
- investigating
Investigation is in progress, and our teams are actively engaged in working toward resolving the issue. The next update will be shared no later than 03:23 UTC.
provider
- identified
Technical teams have identified the issue and implemented fixes. We are seeing steady improvements in system performance. Some delays may still persist, and it may take a few hours for publishing activity to fully catch up. The next update will be shared no later than 03:53 UTC.
provider
- identified
We continue to see improvements in system performance following the fixes implemented by our technical teams. Service stability is improving, although some delays may still persist as publishing activity continues to catch up over the next few hours. The next update will be shared no later than 04:23 UTC.
provider
- identified
We continue to work on improving system performance. While some progress has been made, certain delays may still persist. Our teams remain actively engaged in resolving the issue and restoring full service stability. The next update will be shared no later than 05:15 UTC.
provider
- identified
We are taking additional actions to improve system performance. These steps are expected to help accelerate recovery and reduce remaining delays. We will continue to share updates as progress continues. The next update will be shared no later than 05:40 UTC.
provider
- identified
We are seeing continued progress, with the backlog steadily decreasing and system performance improving. The next update will be shared no later than 06:05 UTC.
provider
- monitoring
The backlog has been fully processed, and the system is now operating as expected. We will continue to monitor to ensure ongoing stability.
provider
- resolved
The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal.
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-0cb3be204b
Is Imperva still down?
No, this incident was resolved 2026-05-17 06:36 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
9h 46m, from 2026-05-16 20:50 UTC to 2026-05-17 06:36 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.