- Level
- confirmed
- Worst impact
- Degraded
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 13h 34m it lasted.
Anything that failed between 2026-05-11 00:47 UTC and 2026-05-11 14:22 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 15
- investigating
Technical teams are investigating a potential issue in the Ashburn, VA (IAD) data center. 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
- investigating
We are continuing to investigate. The next Status Update on this Incident will be provided no later than 01:47 UTC.
provider
- investigating
Technical teams are continuing to investigate. The next Status Update on this Incident will be provided no later than 02:17 UTC.
provider
- investigating
Technical teams are still working on restoring connectivity within the PoP. The next Status Update on this Incident will be provided no later than 03:17 UTC.
provider
- identified
We have identified an issue in the data center and the PoP has been deactivated for now. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.
provider
- identified
The PoP remains deactivated while the team is working in restoring connectivity within the PoP. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
Technical teams have performed remedial actions and still monitoring the results.
provider
- monitoring
The PoP is still deactivated and traffic is being rerouted through an alternate data center in the region. We are continuing to monitor the PoP before bringing it up again.
provider
- monitoring
The PoP remains deactivated , with traffic continuing to be routed through alternate data centers in the region to ensure service continuity. We are closely monitoring the environment. Further updates to follow.
provider
- monitoring
The issue has been mitigated. We are currently in the process of activating the Ashburn, VA (IAD) PoP. Pre-checks are being completed as part of the restoration, and traffic will be gradually restored. The next update will be provided once the PoP is ready to be brought online.
provider
- monitoring
Pre-checks have been completed, and the PoP is expected to be brought back online within the next 15 minutes. The next update will be shared once the PoP is fully online.
provider
- monitoring
The Ashburn, VA (IAD) PoP is now online. Teams will continue to monitor closely to ensure service stability.
provider
- resolved
Monitoring has confirmed that the issue has been resolved, and all services are operating normally.
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-06cfee5bd2
Is Imperva still down?
No, this incident was resolved 2026-05-11 14:22 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
13h 34m, from 2026-05-11 00:47 UTC to 2026-05-11 14:22 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.