Is Imperva down right now?

No. Our checks are finding no problems with Imperva right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Imperva continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, DNS / site unreachable, 5xx error pages, can't connect, slow or laggy, API errors, high latency and no response / timing out. Those are the options the report button offers for Imperva, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Imperva specifically, Imperva's edge nodes, regional DDoS scrubbing centers, and WAF processing can fail independently, leaving some geographic regions or specific API endpoints unprotected while others remain functional. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For Imperva, test a protected endpoint from a different geographic location and check if Imperva's edge IP appears in the response headers or traceroute. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on Imperva's side. Specifically: do not disable Imperva protection or failover to unprotected origin IPs, as this exposes your infrastructure to attacks that will persist even after Imperva recovers. Reporting it here helps other people see they are not alone.

Continuously, around the clock. Imperva publishes a machine-readable status feed, so our first check reads it directly and reports what Imperva itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.imperva.com, and it is linked further up this page. That is Imperva's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Imperva or imperva.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Imperva's own support, not us.