- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 100
What to do
Check whether your product depends on Imperva. 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 4h 58m it lasted.
Anything that failed between 2026-09-10 17:34 UTC and 2026-09-10 22: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 10
- investigating
We have discovered a service degradation, affecting customers accessing the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next Update on this incident will be shared no later than 18:00 UTC
provider
- investigating
Our technical teams are actively investigating the issue affecting the Management Portal. The teams are working to identify the cause and restore services. Next update on the incident will be shared no later than 18:30 UTC.
provider
- investigating
We are currently working on remedial actions to mitigate the impact to customers at this time. Further updates will be provided as information becomes available.
provider
- investigating
We continue to work on the issue affecting the Imperva Management Portal. Our teams are actively working on remedial measures to restore normal functionality. We apologize for the inconvenience and will provide further updates as soon as additional information becomes available. The next update on the issue will be provided no later than 20:30 UTC.
provider
- investigating
Our technical teams have identified the issue and implemented mitigation measures to restore service. Management Portal functionality is currently being validated, and we are continuing to monitor the environment closely to confirm stability. The next update will be provided as further information becomes available, no later than 20:30 UTC.
provider
- monitoring
We have completed remedial actions to resolve the service degradation and the Imperva Management Portal is returning to normal service levels. We are continuing to monitoring the system in order to ensure the continued stability of the service. The next update on the issue will be provided no later than 21:00 UTC.
provider
- monitoring
We are continuing to monitor the system to ensure continued stability. The next update will be provided no later than 21:30 UTC.
provider
- monitoring
We are continuing to monitor the system to ensure continued stability. The next update will be provided no later than 22:00 UTC.
provider
- monitoring
The environment remains stable, and we are continuing to monitor performance closely. The next update will be provided no later than 22:30 UTC.
provider
- resolved
Service levels have been restored and the Imperva Management Portal has returned to normal functionality. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.
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-ca89b501ad
Is Imperva still down?
No, this incident was resolved 2026-09-10 22:31 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
4h 58m, from 2026-09-10 17:34 UTC to 2026-09-10 22:31 UTC, by the times Imperva posted.
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.