- Level
- confirmed
- Worst impact
- Degraded
- Components
- Cloud Security Management Platform
- Down Index
- 21of 100
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 5h 50m it lasted.
Anything that failed between 2026-06-10 18:53 UTC and 2026-06-11 00:43 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 8
- investigating
We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next update on the issue will be provided no later than 19:23 UTC.
provider
- investigating
The team continues to actively investigate the issue and work toward resolution. At this time, the impact is limited to customer access to the Management Portal. Customer websites and protection services remain fully operational and continue to be protected as expected. Next update on the issue will be provided no later than 19:54 UTC.
provider
- investigating
Technical teams continue to actively investigate the issue. A potential contributing factor has been identified, and teams are currently working to validate and address it. Next update on the issue will be provided no later than 20:24 UTC.
provider
- identified
We have identified the underlying cause of the issue and have applied a fix. The issue affected access to the Management Portal and a subset of API requests. We are seeing signs of recovery following the implementation of the fix, and our teams are actively validating service restoration across the impacted components. Next update on the issue will be provided no later than 20:50 UTC.
provider
- monitoring
A fix has been successfully implemented, and services have been restored. Our teams have validated the recovery and are continuing to closely monitor the environment to ensure ongoing stability. Next update on the issue will be provided no later than 21:42 UTC.
provider
- monitoring
Services remain stable following the implementation of the fix, and no further issues have been observed. Our teams will continue to closely monitor the environment for an extended period to ensure stability. Next update on the issue will be provided no later than 23:43 UTC.
provider
- monitoring
Services remain stable, and no further issues have been observed. Our teams will continue to closely monitor the environment to ensure ongoing stability and verify that all services continue to operate as expected. Next update on the issue will be provided no later than 01:45 UTC on 11 June 2026.
provider
- resolved
Monitoring has confirmed that services remain stable following the implementation of the fix and the completion of validation activities. No further issues have been observed.
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-a809d4c020
Is Imperva still down?
No, this incident was resolved 2026-06-11 00:43 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
5h 50m, from 2026-06-10 18:53 UTC to 2026-06-11 00:43 UTC, by the times Imperva posted.
What was affected?
Imperva named Cloud Security Management Platform.
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.