Is Imperva Down?

SaaSLive status, outages, and incident history

No. Imperva is up right now.

Every monitored Imperva system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 32m agoLive, rechecked every 60s

Start monitoring Imperva Official Imperva status page

How we know: the official Imperva status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Imperva Component Status

The main Imperva systems on this page. All 20 are operational right now.

2maintenance18operational

APAC PoPs » Singapore

Maintenance

Coming Soon » Chicago 3, IL (MDW): August 2026

Maintenance

APAC PoPs » Auckland, New Zealand

Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking APAC PoPs » Bangkok, Thailand, APAC PoPs » Hanoi, Vietnam, APAC PoPs » Hong Kong, APAC PoPs » Jakarta, Indonesia, APAC PoPs » Kuala Lumpur, Malaysia, APAC PoPs » Manila, Philippines, APAC PoPs » Melbourne, Australia, APAC PoPs » Mumbai, India, APAC PoPs » New Delhi, India, APAC PoPs » Osaka, Japan, APAC PoPs » Seoul, South Korea, APAC PoPs » Sydney, Australia, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Imperva Outages & Incidents

Incident history from the official Imperva status page, including resolution updates.

Uptime history4 days observed

Aug 8100.00% averageAug 11

[ICM-5357] ORD to MDW PoP Migration - Chicago, ILScheduled for Aug 25, 2026 · 24h 0mScheduled

As part of our commitment to building a future-facing network, Imperva recently launched our Next Generation Architecture in the MDW - Chicago 3, IL PoP with improved capacity, connectivity, and services. This PoP is replacing our currently operational PoP in ORD – Chicago 1, IL. Imperva will be migrating all services and customer traffic from our ORD PoP to our MDW PoP, and decommissioning our ORD PoP during a scheduled maintenance window which will begin at Tuesday, August 25th, 2026 at 08:00 UTC, completing by Wednesday, August 26th, 2026 at 08:00 UTC. For Cloud WAF customers, Imperva will reroute traffic to an unaffected PoP in the region for the duration of the maintenance, with no expected interruption to Cloud WAF services. At the end of the maintenance, traffic will be serviced by the new PoP. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via an alternate connection such as GRE tunnels or Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. At the end of the maintenance, DDoS Protection traffic will be serviced by the new PoP. If Performance Monitoring is enabled on the connections, you will notice a change in the IP address of the PM servers that are sending ICMP echo messages. This might require you to modify ACL/firewall configurations to allow ICMP traffic from the new IPs. To learn more, see https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/performance-monitoring.htm

[ICM-5347] Planned Maintenance on the Imperva data center in Detroit, MIScheduled for Aug 24, 2026 · 8h 0mScheduled

Maintenance on the Detroit, MI data center will be performed on Monday, August 24th, 2026 at 04:00 UTC. We expect to complete the maintenance by Monday, August 24th, 2026 at 12:00 UTC. For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

[ICM-5330] Planned Maintenance on the Imperva data center in Vienna, AustriaScheduled for Aug 18, 2026 · 8h 0mScheduled

Maintenance on the Vienna, Austria data center will be performed on Tuesday, August 18th, 2026 at 23:00 UTC. We expect to complete the maintenance by Wednesday, August 19th, 2026 at 07:00 UTC. For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Live Imperva Outage Reports

Problems reported by engineers using Imperva. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Imperva problems reported yet.

Something wrong with Imperva on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Imperva

Imperva publishes a public status page at status.incapsula.com covering 112 components, including Auckland, New Zealand (AKL), North American PoPs and Third Party Services. PulsAPI tracks Imperva outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Imperva uptime at 100.00%. Response times, incident history, and SLA tracking for Imperva are available on the PulsAPI dashboard.

Imperva Status FAQ

Is Imperva down right now?

PulsAPI checks Imperva every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Imperva status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Imperva is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Imperva recovers.

How do I check Imperva uptime history?

PulsAPI tracks Imperva uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Imperva.

How fast does PulsAPI detect Imperva outages?

PulsAPI polls the official Imperva status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Imperva components?

Yes. PulsAPI monitors 20 individual Imperva components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Imperva goes down?

Yes. Create a PulsAPI account and subscribe to Imperva. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Imperva status changes.

How do I report an issue with Imperva to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Imperva problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Imperva?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Imperva alongside up to 9 other services at pulsapi.com/signup.

Track Imperva with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Imperva status changes.

Start free trial