Is Imperva Down?
Reachable from all 8 checked regions
Average response time: 2304ms
Last checked · checks run every 6 hours
Official status page: https://status.imperva.com
[INC-1106] Elevated Latency for a Subset of Origin Fetch Traffic in Ashburn, VA (WDC)
We have confirmed a solution which mitigates the sub-optimal routing and can be implemented by request on a per-customer basis for impacted websites while we continue to await the permanent fix by the third-party CDN provider.
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
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 3 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
3-day clean streakReachability 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.
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 all 18 regions to find out where it breaks.
Related services
Imperva outage FAQ
My site is down. Is it Imperva or my origin server?
Why are real users being blocked as bots?
Is the whole network affected or only my region?
Can I take Imperva out of the path during an outage?
Does an Imperva outage put my application at risk?
How we measure this
- We request Imperva's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
- A region counts as down only when it gets no usable HTTP response. A
403or429means 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 the same 18 regions, and tell you the moment something breaks.
Start Free Monitoring