Imperva logo

Is Imperva Down?

SaaSLive status, outages, and incident history

Degraded. Imperva is up but having problems.

Imperva is reporting degraded performance as of September 25, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked 4m agoLive · 60s while moving

Don't find out like this next time

You searched to find out Imperva was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official Imperva status page
How we know: the official Imperva status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Imperva Component Status

2 of 117 Imperva components are impaired. Worst problems listed first.

2degraded7maintenance108operational
North American PoPs » Ashburn 1, VA
Degraded
North American PoPs » Ashburn 2, VA
Degraded
Coming Soon » Chicago 3, IL (MDW): August 2026
Maintenance

114 more components tracked

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

Also tracking Coming Soon » Dallas 2, TX (DAL): September 2026, Coming Soon » Jakarta 2, Indonesia (HLP): September 2026, Coming Soon » New York 3, NY (JFK): October 2026, Coming Soon » New York 3, NY (JFK): September 2026, North American PoPs » Chicago 1, IL, North American PoPs » Chicago 3, IL (MDW): August 2026, Additional services » Documentation Portal, Additional services » Support Phone Systems, Additional services » Support Ticketing System, APAC PoPs » Auckland, New Zealand, APAC PoPs » Bangkok, Thailand, APAC PoPs » Hanoi, Vietnam, and 102 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Imperva Outages & Incidents

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

[ICM-5550] Planned Maintenance on the Imperva data center in Osaka, JapanScheduled for Oct 8, 2026 · 4h 0mScheduled

Maintenance on the Osaka, Japan data center will be performed on Thursday, October 8th, 2026 at 17:00 UTC. We expect to complete the maintenance by Thursday, October 8th, 2026 at 21: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-5549] Planned Maintenance on the Imperva data center in Kuala Lumpur, MalaysiaScheduled for Oct 6, 2026 · 4h 0mScheduled

Maintenance on the Kuala Lumpur, Malaysia data center will be performed on Tuesday, October 6th, 2026 at 19:00 UTC. We expect to complete the maintenance by Tuesday, October 6th, 2026 at 23: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-5526] NYC to JFK PoP Migration - New York 1, NYScheduled for Oct 6, 2026 · 24h 0mScheduled

As part of our commitment to building a future-facing network, Imperva recently launched our Next Generation Architecture in the JFK - New York 3, NY PoP with improved capacity, connectivity, and services. This PoP is replacing our currently operational PoP in NYC – New York 1, NY. Imperva will be migrating all services and customer traffic from our NYC PoP to our JFK PoP, and decommissioning our NYC PoP during a scheduled maintenance window which will begin at Tuesday, October 6th, 2026 at 07:00 UTC, completing by Wednesday, October 7th, 2026 at 07: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

Imperva Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Imperva incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 26 days with incidentsSep 25

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.

Are you seeing Imperva problems too?

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?

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. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Imperva changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Imperva outages?

PulsAPI reads the official Imperva status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Imperva components?

Yes. PulsAPI monitors 117 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 free account and subscribe to Imperva: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

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. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Imperva plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Imperva with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services