- Level
- confirmed
- Worst impact
- Degraded
- Components
- Mumbai, India (NAG), New Delhi, India (NDL)
- Regions
- apac, in
What to do
Check whether you use Imperva Mumbai, India (NAG), New Delhi, India (NDL) in apac, in. 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 43m it lasted.
Anything that failed between 2026-05-14 19:49 UTC and 2026-05-15 00:32 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
Technical teams are investigating a potential issue in the New Delhi (NDL), Mumbai (NAG) Data Center. The next Status Update on this Incident will be provided no later than 20:19 UTC. Further updates to follow.
provider
- identified
We have identified the source of the issue in the data center. Technical teams are working on a fix. The next Status Update on this Incident will be provided no later than 20:51 UTC. 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
Technical teams are currently investigating the issue and will provide updates as more information becomes available. The next Status Update on this Incident will be provided no later than 21:25 UTC. 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
Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 21:55 UTC. 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
Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 22:55 UTC. 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
Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 23:55 UTC. 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
- monitoring
A fix has been implemented and we are continuing to monitor in order to ensure that service has returned to normal. 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
- resolved
Service in the data center has been restored to normal. 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
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-b92a15375e
Is Imperva still down?
No, this incident was resolved 2026-05-15 00:32 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
4h 43m, from 2026-05-14 19:49 UTC to 2026-05-15 00:32 UTC, by the times Imperva posted.
What was affected?
Imperva named Mumbai, India (NAG), New Delhi, India (NDL) in apac, in.
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.