Skip to main content
Imperva

[INC-1028]Third-Party Network Issue Impacting CWAF and DDoS Protection Services

Partial outage Lasted 2h 46m · started · Imperva's page

Level
confirmed
Worst impact
Partial outage
Components
Cloud WAF Protection, Amsterdam, Netherlands (RTM), Barcelona, Spain (BCN), Copenhagen, Denmark (CPH), Queretaro, Mexico (QRO), Denver, CO (DEN), Detroit, MI (DET), Houston, TX (HOU), Frankfurt, Germany (HHN), L3/4 Network DDoS Protection, London 1, UK (LCY), Madrid, Spain (MAD), Paris, France (PAR), Vienna, Austria (GRZ), Warsaw, Poland (WAR)
Regions
eu
Down Index
34of 100

What to do

  • Check whether you use Imperva Cloud WAF Protection, Amsterdam, Netherlands (RTM), Barcelona, Spain (BCN), Copenhagen, Denmark (CPH) and 11 more in eu. 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 2h 46m it lasted.

    Anything that failed between 2026-05-10 13:35 UTC and 2026-05-10 16:21 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 4

  1. investigating

    A third-party internet service provider is currently experiencing an issue resulting in degradation of CWAF and Network DDoS services. Customers may experience elevated latency or, in some cases, temporary loss of availability for CWAF-protected sites. This impact includes CloudWAF customers using Origin POP and Network DDoS customers utilizing Mesh. Customer websites remain fully protected during this time. The next Status Update on this Incident will be provided no later than 14:05 UTC.

    provider

  2. monitoring

    Technical teams have performed remedial actions and services are returning to normal operations. 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

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

  4. resolved

    Monitoring has confirmed that services are stable, and the issue has been resolved. 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-2c91e132c4

Is Imperva still down?

No, this incident was resolved 2026-05-10 16:21 UTC. For Imperva's live state, see https://down.guide/imperva.

How long did it last?

2h 46m, from 2026-05-10 13:35 UTC to 2026-05-10 16:21 UTC, by the times Imperva posted.

What was affected?

Imperva named Cloud WAF Protection, Amsterdam, Netherlands (RTM), Barcelona, Spain (BCN), Copenhagen, Denmark (CPH) and 11 more in eu.

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.