- Level
- confirmed
- Worst impact
- Degraded
- Components
- Buenos Aires, Argentina (EZE)
What to do
Check whether you use Imperva Buenos Aires, Argentina (EZE). 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 0m it lasted.
Anything that failed between 2026-05-13 01:57 UTC and 2026-05-13 01:57 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 1
- resolved
We have discovered a service degradation that affected the EZE PoP which may have resulted in customers experiencing impact for Imperva Cloud WAF and DDoS for Networks traffic routed through the EZE PoP. Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts. Services has been restored for EZE PoP.
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-9a08244daa
Is Imperva still down?
No, this incident was resolved 2026-05-13 01:57 UTC. For Imperva's live state, see https://down.guide/imperva.
How long did it last?
0m, from 2026-05-13 01:57 UTC to 2026-05-13 01:57 UTC, by the times Imperva posted.
What was affected?
Imperva named Buenos Aires, Argentina (EZE).
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.