- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Web Application Performance
- Down Index
- 30of 100
What to do
Check whether you use Imperva Web Application Performance. 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 3h 28m it lasted.
Anything that failed between 2026-05-06 11:36 UTC and 2026-05-06 15:04 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 are investigating a potential issue impacting Cloud WAF Protected Websites. Some websites may fail to load or return errors. Customer domains remain fully protected at this time. Our technical teams are actively working to identify the root cause, and further updates will be shared 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
- identified
We have identified the issue, and a fix is currently being implemented. The next Status Update on this Incident will be provided no later than 12:22 UTC.
provider
- identified
We are continuing to actively work on implementing a fix. The next Status Update on this Incident will be provided no later than 12:55 UTC.
provider
- investigating
Our investigation has determined that the previously suspected cause may be one contributing factor within a broader underlying root-cause pattern than initially identified. We are continuing to investigate and actively working to identify the underlying cause. The next Status Update on this Incident will be provided no later than 13:11 UTC.
provider
- investigating
We are continuing to actively investigate this issue. The next Status Update on this Incident will be provided no later than 13:39 UTC.
provider
- investigating
We are actively investigating this issue and continuing our efforts to identify the cause of the issue. The next Status Update on this Incident will be provided no later than 14:13 UTC.
provider
- monitoring
A fix has been implemented, and services have returned to normal. We are continuing to monitor the situation closely to ensure stability. The next Status Update on this Incident will be provided no later than 15:04 UTC.
provider
- resolved
The issue has been resolved, and monitoring has confirmed service stability.
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-cf62152812
Is Imperva still down?
No, this incident was resolved 2026-05-06 15:04 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
3h 28m, from 2026-05-06 11:36 UTC to 2026-05-06 15:04 UTC, by the times Imperva posted.
What was affected?
Imperva named Web Application Performance.
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.