Is Imperva down?

Product match: components.

Read the provider’s incident report

1. 2026-11-05T17:57:59.446Z · resolved

   The incident causing delays with certain configuration changes has been resolved. Configuration processing remains at expected levels, and the service has remained stable following mitigation. We will continue to monitor service health as part of our normal operations.

2. 2026-11-05T16:23:02.637Z · monitoring

   The incident causing delays with certain configuration changes has been mitigated. Configuration processing has returned to expected levels, and our teams are closely monitoring the service to ensure continued stability.

3. 2026-11-05T10:30:29.370Z · identified

   We have made significant progress with our mitigation efforts, and service has improved across most affected locations. Some customers may continue to experience delays with certain configuration changes being applied in the Jakarta (JKT), Kuala Lumpur (KUL), and Manila (MNL) Points of Presence (PoPs). Additional mitigation activities for the remaining affected APAC locations are planned during regional off-hours to minimize potential customer disruption. We continue to monitor the service close

4. 2026-11-04T23:52:13.443Z · identified

   Our phased mitigation efforts have significantly reduced the scope of the issue. A small portion of service capacity, approximately 5%, may continue to experience the issue and will be addressed during the next phase of remediation. We continue to monitor the service closely and will provide a further update before 08:00 UTC.

5. 2026-11-04T15:23:46.394Z · identified

   Some customers may continue to experience delays when applying certain configuration changes. The issue remains limited in scope and does not affect all customers or configuration changes. Our teams are actively executing a phased mitigation plan to restore normal processing for the affected services. The phased plan will be applied during low traffic times in our PoPs to minimise any further disruption. We continue to monitor the service closely and will provide further updates as progress is m

6. 2026-11-04T15:07:46.241Z · investigating

   We are investigating an incident where some customers may experience delays when applying certain configuration changes. Not all configuration changes or customers are affected. Our teams are actively investigating and we will provide further updates as more information becomes available. The next update will not be after 15:30 UTC

7. 2026-11-04T15:00:19.140Z · investigating

   We are investigating an incident where some customers may experience delays when applying certain configuration changes. Not all configuration changes or customers are affected. Our teams are actively investigating and we will provide further updates as more information becomes available. The next update will not be after 15:30 UTC

Product match: components.

Read the provider’s incident report

1. 2026-11-04T10:17:43.725Z · resolved

   The issue affecting access to www.imperva.com has been resolved. The website is operating normally, and our monitoring confirms service stability has been restored. We appreciate your patience while our teams worked to resolve the issue.

2. 2026-11-04T09:38:58.036Z · monitoring

   The issue affecting access to www.imperva.com has been mitigated, and the website is responding normally. Our teams have observed improvements in service stability and are continuing to monitor performance to ensure a consistent and reliable experience.

3. 2026-11-04T09:27:46.870Z · identified

   Mitigation efforts are ongoing as our teams continue working to address the issue and restore normal access to www.imperva.com. We will provide further updates as more information becomes available.

4. 2026-11-04T09:16:02.598Z · investigating

   Our teams have identified the source of the degradation and are actively implementing the mitigation. We will continue to provide further updates as progress is made.

5. 2026-11-04T09:07:54.262Z · investigating

   We have identified an issue causing intermittent access to **www.imperva.com**. Our teams are actively investigating and working to implement a fix. We will continue to monitor the situation and provide further updates as more information becomes available.

Product match: components.

Read the provider’s incident report

1. 2026-11-02T06:07:39.391Z · resolved

   The services has remained stable throughout the monitoring period, with no further issues detected. The Network Protection Dashboard is functioning as expected.

2. 2026-11-02T04:53:21.681Z · monitoring

   A fix has been successfully implemented, and the Network Protection Dashboard is now operating normally. We will continue to monitor the service to ensure stability.

3. 2026-11-02T04:32:08.578Z · investigating

   We continue to investigate the issue affecting the Network Protection Dashboard. Our team is actively working on remediation to restore normal functionality. The next update will be provided no later than 05:00 UTC.

4. 2026-11-02T04:09:05.093Z · investigating

   We are investigating an issue affecting the Network Protection Dashboard, where some dashboard information may be unavailable or fail to load. Our team is working to identify the cause and restore normal functionality. Further updates will be provided as more information becomes available.

Product match: components.

Read the provider’s incident report

1. 2026-10-29T09:14:44.882Z · resolved

   Monitoring has confirmed that network performance is stable and services are operating normally.

2. 2026-10-29T08:54:26.601Z · monitoring

   Following confirmation of resolution from our upstream providers and verification of network stability, the Queretaro, Mexico (QRO) PoP has been reactivated. Our team will continue to monitor performance to ensure ongoing stability.

3. 2026-10-29T06:07:21.600Z · identified

   Our teams continue to monitor network stability and coordinate with upstream providers to confirm full service restoration before reactivating the Queretaro, Mexico (QRO) PoP.

4. 2026-10-29T04:15:01.676Z · identified

   Our upstream providers have confirmed that corrective measures have been implemented and are reporting improvements in network performance. We are also observing improvements, and our teams will continue to closely monitor the situation to ensure sustained stability before reactivating the Queretaro, Mexico (QRO) PoP and restoring normal traffic routing.

5. 2026-10-29T02:59:49.802Z · identified

   Third-party upstream providers in the region are experiencing issues, and our teams remain in close contact with them for updates. Traffic will continue to be rerouted through alternate PoPs in the region while the providers work to resolve the issue.

6. 2026-10-29T01:23:11.596Z · identified

   Traffic remains rerouted through alternate PoPs in the region. Customers may experience increased latency while the reroute is in place.

7. 2026-10-29T00:09:33.907Z · identified

   We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service

Product match: components.

Read the provider’s incident report

1. 2026-10-20T16:21:18.737Z · resolved

   This incident has been resolved.

2. 2026-10-20T16:12:37.192Z · monitoring

   A fix has been implemented and we are monitoring the results.

3. 2026-10-20T14:28:12.882Z · identified

   Mitigation efforts are ongoing. Our teams have completed additional configuration changes and continue working to restore normal service. Further updates will be provided as information becomes available.

4. 2026-10-20T12:54:12.642Z · identified

   Imperva teams continue working to mitigate the issue and restore normal service. We are currently implementing and validating mitigation actions. Further updates will be provided as information becomes available.

5. 2026-10-20T10:26:26.996Z · identified

   Efforts to mitigate the issue are still ongoing. Our teams continue working to restore normal service. Further updates will be provided as information becomes available.

6. 2026-10-20T09:43:48.004Z · identified

   Efforts into mitigating the issue are still ongoing. Further updates will be provided as information becomes available. The next update will be before 11:15 UTC

7. 2026-10-20T09:04:08.239Z · identified

   Our internal teams have identified the service degradation that is affecting the newly onboarded sites. We are currently working to remediate the incident and further updates will be provided as information becomes available. The next update will be before 09:45 UTC

8. 2026-10-20T08:43:00.659Z · investigating

   We are investigating a service degradation affecting resolution for some newly onboarded sites. Our teams are working to determine the cause and will provide updates as more information becomes available. The next update will be provided by 09:15 UTC.

Product match: unmapped.

Read the provider’s incident report

1. 2026-10-19T22:47:56.713Z · resolved

   Following successful mitigation and a period of monitoring, we have confirmed that the service is operating normally and the issue is resolved. We apologize for any inconvenience this may have caused.

2. 2026-10-19T21:35:10.513Z · monitoring

   Mitigation efforts have concluded and new site resolution has returned to normal. The next update will be provided by 22:45 UTC.

3. 2026-10-19T21:29:31.000Z · identified

   The impact has been mitigated, and normal service has been restored. Our teams are continuing to monitor the environment to confirm stability. Further updates will be provided as information becomes available.

4. 2026-10-19T20:30:23.794Z · identified

   Following identification of the service degradation, our teams successfully tested mitigation measures and are actively working to deploy them and restore normal service.

5. 2026-10-19T19:27:48.000Z · identified

   Our internal teams have identified the service degradation that is affecting the newly onboarded sites. We are currently working to remediate the incident and further updates will be provided as information becomes available.

6. 2026-10-19T19:10:36.221Z · investigating

   Investigation into the cause of the service degradation is currently ongoing. Further updates will be provided as information becomes available.

7. 2026-10-19T18:34:39.726Z · investigating

   Our internal teams are continuing to investigate the service degradation that is affecting the newly onboarded sites. Investigation into the cause of the service degradation is ongoing. Further updates will be provided by 19:00 UTC

8. 2026-10-19T17:38:02.000Z · investigating

   We are investigating a service degradation affecting resolution for some newly onboarded sites. Our teams are working to determine the cause and will provide updates as more information becomes available. The next update will be provided by 18:30 UTC.

Product match: unmapped.

Read the provider’s incident report

1. 2026-10-15T23:05:01.779Z · resolved

   Mitigation measures have been implemented to address the SIEM log data issue. Our teams have confirmed the environment accuracy.

2. 2026-10-15T22:36:34.222Z · identified

   We have identified the source of the SIEM log data issue affecting the accuracy of information reported for some customers. Our teams are actively working to implement mitigation measures and restore normal service. The next update will be provided by 23:00 UTC.

3. 2026-10-15T21:49:14.752Z · investigating

   We are currently investigating an issue with SIEM log data that may affect the accuracy of information reported for some customers. Our team is working to assess the impact and identify the appropriate corrective actions. The next update will be provided by 22:30 UTC.

Product match: components.

Read the provider’s incident report

1. 2026-10-13T17:44:53.776Z · resolved

   Monitoring has confirmed that the service is stable and certificate issuance is functioning as expected. No additional issues have been observed, and this incident has been resolved. Thank you for your patience.

2. 2026-10-13T15:38:10.000Z · monitoring

   The issue was identified as a degradation affecting a third-party service. The issue should now be resolved, and certificate issuance is operating as expected. We are closely monitoring the service to ensure continued stability. The next update will be no later than 18:00 UTC

3. 2026-10-13T13:58:36.470Z · identified

   We have identified the issue affecting the onboarding of new WAF sites and the issuance of new certificates. Our teams are actively working to restore normal service. The next update will be before 15:00 UTC.

4. 2026-10-13T13:29:10.566Z · identified

   We are investigating an issue affecting Imperva-generated certificate issuance. Customers may experience issues when onboarding new sites using an Imperva-generated certificate and renewing existing certificates. Customer assets and sites remain protected during this time. The next update will be before 14:00 UTC.

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-11T04:08:37.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Imperva feature.

The latest status observation was 2026-11-11T03:58:44.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save Imperva in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.