- Level
- confirmed
- Worst impact
- Degraded
- Components
- CDN and WAF Management
- Down Index
- 21of 100
What to do
Check whether you use Imperva CDN and WAF Management. 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 12m it lasted.
Anything that failed between 2026-09-17 18:57 UTC and 2026-09-18 00:09 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 currently investigating an issue that may cause intermittent DNS resolution failures for some customers. Our teams are actively investigating the issue and working to identify the cause and restore consistent DNS resolution. We will provide further updates as more information becomes available.
provider
- investigating
We continue to investigate intermittent DNS resolution issues that may affect a small number of requests. The issue is highly intermittent and remains limited in scope. Our teams are actively investigating the issue and working to identify the cause and ensure consistent DNS resolution. The next update on this issue will be shared no later than 20:10 UTC.
provider
- identified
The issue has been identified, and our teams have confirmed the cause of the intermittent DNS resolution failures. The team is currently applying the mitigation in a controlled manner across the affected services. The issue remains intermittent and limited in scope. The next update on the issue will be shared no later that 20:20 UTC.
provider
- identified
Mitigation efforts are continuing. We are seeing recovery as the targeted fix is progressively applied to the affected services. The next update on the issue will be shared no later than 20:55 UTC.
provider
- identified
Mitigation and validation efforts are continuing. The team is closely monitoring the service while applying the targeted fix across the remaining affected systems and validating recovery. The next update on the issue will be shared no later than 21:25 UTC.
provider
- identified
Mitigation and validation efforts remain ongoing. The team continues to apply the targeted fix to the remaining affected systems while closely monitoring the service and validating recovery. The next update on the issue will be shared no later than 22:05 UTC.
provider
- monitoring
The team has completed the mitigation, and the affected services have been validated to be operating as expected. We will continue to closely monitor the service to ensure the fix remains effective and services remains stable.
provider
- resolved
The services are now stable, and the issue has been fully mitigated. Post-mitigation validation has been completed, confirming that the services are operating as expected. The incident is now considered resolved.
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-305dbf2b60
Is Imperva still down?
No, this incident was resolved 2026-09-18 00:09 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
5h 12m, from 2026-09-17 18:57 UTC to 2026-09-18 00:09 UTC, by the times Imperva posted.
What was affected?
Imperva named CDN and WAF Management.
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.