Is Imperva down?

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.

Product match: unmapped.

Read the provider’s incident report

1. 2026-10-13T17:29:56.132Z · resolved

   We have completed monitoring and confirmed that the mitigation measures have successfully resolved the issue that resulted in false positive IRA blocks for some customers. Service is operating normally, and no further impact has been observed. We sincerely apologize for the inconvenience and appreciate your patience while our teams worked to identify and resolve the issue.

2. 2026-10-13T16:28:34.415Z · monitoring

   We have implemented mitigation measures to address the issue that may have resulted in false positive IRA blocks for some customers. Current indicators show the mitigations are performing as expected, and we are actively monitoring the environment to confirm stability. The next update will be provided before 17:30 UTC.

3. 2026-10-13T15:58:27.000Z · identified

   We are actively implementing mitigation measures to reduce the impact of false positive IRA blocks. The next update will be before 16:30 UTC.

4. 2026-10-13T15:30:43.748Z · identified

   We have identified the cause of the issue that may be resulting in false positive IRA blocks for some customers. Our teams are actively working on mitigation measures and will provide additional updates as progress is made. The next update will be provided before 16:00 UTC.

5. 2026-10-13T15:18:45.000Z · investigating

   We are currently investigating an issue that may be causing some customers to experience false positive IRA blocks. Our teams are actively working to identify the cause and mitigate the impact. The next update will be before 15:30 UTC.

Product match: components.

Read the provider’s incident report

1. 2026-10-10T10:11:47.902Z · resolved

   The Dallas, TX (DAL) has been reactivated, and monitoring has confirmed stability. Services are operating normally, and the incident is now resolved.

2. 2026-10-10T09:18:11.244Z · monitoring

   The Dallas, TX (DAL) PoP has been successfully activated and returned to service. Our technical teams will continue to closely monitor the PoP to ensure stability and performance.

3. 2026-10-09T23:46:00.669Z · identified

   A fix has been applied to address the connectivity issue affecting the DAL (Dallas) PoP. Traffic continues to be routed through an alternate PoP while our teams monitor service stability. The DAL PoP is scheduled to return to service during a low-traffic period, around 09:00 UTC on Saturday, 10 October. We will provide a further update once the PoP is back in service.

4. 2026-10-09T23:21:12.908Z · identified

   The issue affecting the DAL PoP has been identified, and our technical teams are actively working on a fix. Traffic remains rerouted through an alternate PoP in the region. The next update will be provided no later than 00:20 UTC on Saturday, 10 October.

5. 2026-10-09T22:46:00.607Z · investigating

   We are continuing to investigate this issue.

6. 2026-10-09T22:43:25.593Z · investigating

   Investigation into the cause of the service degradation affecting the DAL PoP is still ongoing. Traffic remains rerouted through an alternate PoP in the region. Further updates will be provided as information becomes available.

7. 2026-10-09T22:42:44.570Z · investigating

   Investigation into the cause of the service degradation affecting the DAL PoP is still ongoing. Traffic remains rerouted through an alternate PoP in the region. Further updates will be provided as information becomes available.

8. 2026-10-09T22:16:23.555Z · investigating

   We have discovered a service degradation that is affecting the DAL POP, which may have resulted in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Traffic is currently being rerouted through an alternate PoP in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Investigation into the cause of the service degradation is currently ongoing. Further updates will be provided a

Product match: components.

Read the provider’s incident report

1. 2026-10-06T01:48:36.467Z · resolved

   Traffic across all affected PoPs is stable, and services are operating normally with no further impact observed.

2. 2026-10-06T00:42:23.624Z · monitoring

   The Warsaw (WAR) PoP has been successfully activated and is now operational. Network traffic across all core Points of Presence—including Singapore (XSP), Atlanta (ATL), Detroit (DET), Tokyo (NRT), and Warsaw (WAR)—remains stable and fully operational following our remediation efforts. Our engineering teams will continue to closely monitor system performance.

3. 2026-10-05T13:06:03.396Z · monitoring

   Network traffic across all core points of presence—including Singapore (XSP), Atlanta (ATL), Detroit (DET), and Tokyo (NRT)—remains stable and fully operational following our earlier remediation efforts. Our engineering teams are keeping a close watch on system performance, and we will share a follow-up update as soon as the Warsaw (WAR) PoP is successfully brought back online.

4. 2026-10-05T12:11:33.988Z · monitoring

   Service for Singapore (XSP), Atlanta (ATL), Detroit (DET), and Tokyo (NRT) has been fully restored and is operating normally. Traffic for Warsaw (WAR) remains bypassed while our engineering teams complete final validation and plan to bring the PoP back online during scheduled off-peak maintenance hours. . We are actively monitoring the system, and the next update will be provided by 13:00 UTC

5. 2026-10-05T11:45:55.357Z · investigating

   We are observing IPv6 connectivity issues affecting Detroit, MI (DET). Our teams are actively investigating the issue and working to implement remediation. The next update will be provided by 13:15 UTC.

6. 2026-10-05T11:34:36.536Z · investigating

   Our investigation is ongoing, and our teams are actively working to identify the cause and implement the appropriate remediation. The next update will be provided by 12:05 UTC.

7. 2026-10-05T11:02:43.696Z · investigating

   We are observing a recurrence of IPv6 connectivity issues affecting Singapore (XSP) and Atlanta (ATL). Service in Tokyo (NRT) remains fully operational. Additionally, IPv4 issues were observed for Warsaw (WAR). Traffic for WAR has been bypassed to restore service stability while our engineering teams actively investigate the root cause for XSP and the underlying issue at WAR. The next update will be provided by 11:30am UTC

8. 2026-10-05T10:26:22.866Z · investigating

   We are observing a recurrence of the IPv6 connectivity issues affecting Singapore (XSP). Service in Tokyo (NRT) and Atlanta (ATL) remains fully operational. Our engineering team is actively investigating the cause of this regression and working to restore stability to XSP, as well as resolving the ongoing impact in Warsaw (WAR). The next update will be provided by 11:00 UTC

9. 2026-10-05T09:57:56.610Z · investigating

   We are continuing to address the IPv6 connectivity issue across our network. Service for Singapore (XSP), Tokyo (NRT), and Atlanta (ATL) is operating normally. Our teams are actively investigating the root cause and working to restore full connectivity for the remaining affected locations (WAR). The next update will be provided by 10:30 UTC.

10. 2026-10-05T09:32:41.421Z · investigating

    We are continuing to address the IPv6 connectivity issue across our network. Service for Atlanta, GA (ATL) and Tokyo, Japan (NRT) is operating normally. Our teams are actively investigating the root cause and working on a permanent resolution. The next update will be provided by 10:00 UTC.

11. 2026-10-05T09:07:17.812Z · investigating

    Our investigation remains ongoing, and our teams are actively working to identify the cause and implement the appropriate remediation. The next update will be provided no later than 09:40 UTC.

12. 2026-10-05T08:41:24.300Z · investigating

    We are investigating an issue affecting network connectivity for customers using IPv6 addresses at multiple locations. Customers using IPv4 connectivity are not impacted. Our teams are actively investigating the issue and working to identify the appropriate remediation. We will provide further updates as more information becomes available.

Product match: components.

Read the provider’s incident report

1. 2026-10-02T02:50:06.334Z · resolved

   The Frankfurt, Germany (HHN) PoP has been reactivated and is now returned to service. This incident has been resolved.

2. 2026-10-02T00:37:14.175Z · identified

   The connectivity issue has been identified and resolved by our technical teams, and the system will continue to be monitored for stability. The Frankfurt, Germany (HHN) PoP will be returned to service during the low traffic period for this PoP. This is scheduled for around 02:00 UTC Friday 2nd October. A further update will be posted once this process has been completed.

3. 2026-10-01T22:44:05.022Z · investigating

   We continue to investigate the issue affecting the PoP. Traffic remains routed through alternate locations in the region. The team is performing additional validation and testing before returning the PoP to service. We will continue to monitor the situation closely and provide further updates as more information becomes available.

4. 2026-10-01T21:26:15.484Z · investigating

   We continue to investigate the connectivity issue affecting the Frankfurt, Germany (HHN) PoP. Traffic remains rerouted through alternate PoPs while the investigation continues. Current monitoring indicates that services remain stable and traffic is being successfully handled through the alternate locations. The HHN PoP will be returned to service once the investigation and validation activities are complete.

5. 2026-10-01T20:39:24.717Z · investigating

   We continue to investigate the connectivity issue affecting the Frankfurt, Germany (HHN) PoP. Traffic remains rerouted through alternate PoPs as a mitigation measure while investigations continue. Current monitoring indicates network services remain stable and traffic is being successfully handled through alternate locations. The HHN PoP will be returned to service once investigation and validation activities have been completed. We will continue to provide updates as more information becomes

6. 2026-10-01T20:07:05.349Z · investigating

   We have identified a connectivity issue affecting the Frankfurt, Germany (HHN) PoP. As a mitigation measure, traffic is being rerouted through alternate locations to reduce customer impact while our teams investigate. Some customers may experience intermittent latency or connectivity degradation. We are actively working to resolve the issue and will provide updates as more information becomes available.

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-22T00:14:20.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10: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-10-22T00:01:02.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.