Skip to main content
Imperva logo

Is Imperva Down?

No — Imperva is up

Reachable from all 8 checked regions

Average response time: 2748ms

Last checked · checks run every 6 hours

Official status page: https://status.imperva.com

Components the vendor reports as affected: New Delhi 2, India (DEL): October 2026 Under Maintenance Sydney 2, Australia (BWU): November 2026 Under Maintenance Milan 2, Italy (MIL): November 2026 Under Maintenance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Imperva fail from enough regions to rule out probe noise.

Imperva uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1896ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 54 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

54-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 37 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 40 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 24 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 24 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
2464ms
DNS 814ms TCP 1ms TLS 3ms TTFB 2307ms
fra
4162ms
DNS 1001ms TCP 138ms TLS 139ms TTFB 3411ms
gru
2999ms
DNS 143ms TCP 2ms TLS 4ms TTFB 2321ms
iad
1675ms
DNS 54ms TCP 1ms TLS 3ms TTFB 1631ms
jnb
3354ms
DNS 32ms TCP 0ms TLS 2ms TTFB 2361ms
lax
2529ms
DNS 160ms TCP 26ms TLS 28ms TTFB 2216ms
lhr
1883ms
DNS 33ms TCP 2ms TLS 6ms TTFB 1599ms
nrt
2923ms
DNS 143ms TCP 1ms TLS 2ms TTFB 2174ms

What Imperva does

Imperva provides web application firewalling, DDoS mitigation, bot management and application delivery from a network of points of presence that customer traffic is routed through. Because sites sit behind it by DNS, an Imperva problem is seen by visitors as the customer's own site failing, even when the origin server is entirely healthy.

What an outage looks like

Visitors receive error pages served by the edge rather than by your application, or requests hang before reaching your origin. Legitimate traffic is challenged or blocked as though it were a bot. Latency rises sharply for users routed through one region while others are unaffected. Origin logs go quiet even though the site is being visited, which is the clearest sign the edge is not forwarding.

What to do about it

status.imperva.com lists 114 components, grouped into North American, EMEA, LATAM and APAC points of presence plus Protection Services and Management and Analytics Services. Find the named PoP your traffic uses, such as Ashburn or Atlanta, not the headline. Cloud WAF Protection and the Cloud Security Management Platform report separately, so the console can be down while protection keeps running. Support Ticketing System and Support Phone Systems are tracked too.

Is it down for everyone, or just you?

If this page says Imperva is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Imperva outage FAQ

My site is down. Is it Imperva or my origin server?
Request your origin directly, bypassing Imperva, using its IP address or an origin hostname. If the application answers normally there while visitors see errors, the fault is at the edge. Quiet origin logs during a period when the site is clearly being visited point the same way, because it means requests are not being forwarded.
Why are real users being blocked as bots?
Bot management and WAF rules run at the edge, so a misclassification during a degraded period looks identical to a policy change you did not make. Imperva tracks Cloud WAF Protection as its own component. If it is degraded, avoid loosening rules permanently to work around it, since those relaxed rules will still be in place long after the incident clears.
Is the whole network affected or only my region?
Usually only part. Imperva reports each point of presence individually across four regional groups, so an incident in one PoP affects the visitors routed to it and nobody else. This is why a site can be reported down by customers in one country and fine everywhere else, and why the named PoP row is more informative than the overall status.
Can I take Imperva out of the path during an outage?
Technically yes by changing DNS to point at your origin, but doing so removes your WAF and DDoS protection and exposes the origin directly. DNS changes also take time to propagate, so relief is not immediate. Treat it as a deliberate decision with a security cost rather than an obvious fix, and plan the rollback before making it.
Does an Imperva outage put my application at risk?
An availability incident at the edge is not itself a compromise. The risk is the workaround: routing around the WAF exposes an origin that has been shielded, possibly for years, and origins in that position often carry unpatched surface. If you do bypass it, restore the protected path as soon as the component recovers.

How we measure this

  • We request Imperva's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Imperva publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Imperva goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required