Imperva Outage History

Started Oct 20, 2026, 08:43 AM UTC· resolved Oct 20, 2026, 04:21 PM UTC

1. investigating Oct 20, 2026, 08:43 AM UTC

   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.

2. identified Oct 20, 2026, 09:04 AM UTC

   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

3. identified Oct 20, 2026, 09:43 AM UTC

   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

4. identified Oct 20, 2026, 10:26 AM UTC

   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.

5. identified Oct 20, 2026, 12:54 PM UTC

   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.

6. identified Oct 20, 2026, 02:28 PM UTC

   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.

7. monitoring Oct 20, 2026, 04:12 PM UTC

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

8. resolved Oct 20, 2026, 04:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 19, 2026, 05:38 PM UTC· resolved Oct 19, 2026, 10:47 PM UTC

1. investigating Oct 19, 2026, 05:38 PM UTC

   We have discovered a service degradation that is affecting newly onboarded sites having problematic with CNAME resolution. Investigation into the cause of the service degradation is currently ongoing. Further updates will be provided as information becomes available.

2. investigating Oct 19, 2026, 06:34 PM UTC

   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

3. investigating Oct 19, 2026, 07:10 PM UTC

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

4. identified Oct 19, 2026, 07:27 PM UTC

   Our internal teams have identified the service degradation that is affecting the newly onboarded sites. They are currently working to remediate the incident and further updates will follow.

5. identified Oct 19, 2026, 08:30 PM UTC

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

6. identified Oct 19, 2026, 09:29 PM UTC

   The impact has been mitigated, and normal service has been restored. Our teams are continuing to monitor the environment to confirm stability. The next update will be provided by 22:30 UTC.

7. monitoring Oct 19, 2026, 09:35 PM UTC

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

8. resolved Oct 19, 2026, 10:47 PM UTC

   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.

Read the full incident report →

Started Oct 15, 2026, 09:49 PM UTC· resolved Oct 15, 2026, 11:05 PM UTC

1. investigating Oct 15, 2026, 09:49 PM UTC

   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.

2. identified Oct 15, 2026, 10:36 PM UTC

   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. resolved Oct 15, 2026, 11:05 PM UTC

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

Read the full incident report →

Started Oct 13, 2026, 03:18 PM UTC· resolved Oct 13, 2026, 05:29 PM UTC

1. investigating Oct 13, 2026, 03:18 PM UTC

   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 16:00 UTC.

2. identified Oct 13, 2026, 03:30 PM UTC

   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.

3. identified Oct 13, 2026, 03:31 PM UTC

   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.

4. monitoring Oct 13, 2026, 04:28 PM UTC

   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.

5. resolved Oct 13, 2026, 05:29 PM UTC

   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.

Read the full incident report →

Started Oct 13, 2026, 01:29 PM UTC· resolved Oct 13, 2026, 05:44 PM UTC

1. identified Oct 13, 2026, 01:29 PM UTC

   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.

2. identified Oct 13, 2026, 01:58 PM UTC

   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.

3. monitoring Oct 13, 2026, 03:38 PM UTC

   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 17:00 UTC

4. resolved Oct 13, 2026, 05:44 PM UTC

   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.

Read the full incident report →

Started Oct 09, 2026, 10:16 PM UTC· resolved Oct 10, 2026, 10:11 AM UTC

1. investigating Oct 09, 2026, 10:16 PM UTC

   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 as information becomes available.

2. investigating Oct 09, 2026, 10:42 PM UTC

   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.

3. investigating Oct 09, 2026, 10:43 PM UTC

   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.

4. investigating Oct 09, 2026, 10:46 PM UTC

   We are continuing to investigate this issue.

5. identified Oct 09, 2026, 11:21 PM UTC

   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.

6. identified Oct 09, 2026, 11:46 PM UTC

   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.

7. monitoring Oct 10, 2026, 09:18 AM UTC

   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.

8. resolved Oct 10, 2026, 10:11 AM UTC

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

Read the full incident report →

Started Oct 05, 2026, 08:41 AM UTC· resolved Oct 06, 2026, 01:48 AM UTC

1. investigating Oct 05, 2026, 08:41 AM UTC

   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.

2. investigating Oct 05, 2026, 09:07 AM UTC

   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.

3. investigating Oct 05, 2026, 09:32 AM UTC

   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.

4. investigating Oct 05, 2026, 09:57 AM UTC

   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.

5. investigating Oct 05, 2026, 10:26 AM UTC

   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

6. investigating Oct 05, 2026, 11:02 AM UTC

   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

7. investigating Oct 05, 2026, 11:34 AM UTC

   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.

8. investigating Oct 05, 2026, 11:45 AM UTC

   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.

9. monitoring Oct 05, 2026, 12:11 PM UTC

   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

10. monitoring Oct 05, 2026, 01:06 PM UTC

    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.

11. monitoring Oct 06, 2026, 12:42 AM UTC

    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.

12. resolved Oct 06, 2026, 01:48 AM UTC

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

Read the full incident report →

Started Oct 01, 2026, 08:07 PM UTC· resolved Oct 02, 2026, 02:50 AM UTC

1. investigating Oct 01, 2026, 08:07 PM UTC

   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.

2. investigating Oct 01, 2026, 08:39 PM UTC

   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 available.

3. investigating Oct 01, 2026, 09:26 PM UTC

   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.

4. investigating Oct 01, 2026, 10:44 PM UTC

   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.

5. identified Oct 02, 2026, 12:37 AM UTC

   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.

6. resolved Oct 02, 2026, 02:50 AM UTC

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

Read the full incident report →

Started Oct 01, 2026, 11:27 AM UTC· resolved Oct 01, 2026, 11:48 AM UTC

1. investigating Oct 01, 2026, 11:27 AM UTC

   We have identified a service degradation affecting the Imperva API. As a result, some customers attempting to download SIEM logs via the API may receive HTTP 502 errors. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. All customer websites remain fully protected at this time. Technical teams are investigating. Further updates to follow. 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 disruption, the update will include potential impacts to any affected region.

2. monitoring Oct 01, 2026, 11:40 AM UTC

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

3. resolved Oct 01, 2026, 11:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 11:42 AM UTC· resolved Sep 28, 2026, 11:42 AM UTC

1. resolved Sep 28, 2026, 11:42 AM UTC

   Imperva identified an issue in the London (LCY) PoP that impacted a subset of customers who experienced packet loss, connection timeouts, and intermittent connectivity issues. The issue was traced to one of Imperva's third-party internet service providers. To mitigate the impact, Imperva rerouted traffic and bypassed the affected provider. Following this mitigation, service was restored and performance returned to normal levels.

Read the full incident report →

Started Sep 28, 2026, 09:53 AM UTC· resolved Sep 29, 2026, 02:05 AM UTC

1. identified Sep 28, 2026, 09:53 AM UTC

   We have identified a connectivity issue affecting the Madrid (MAD) 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.

2. investigating Sep 28, 2026, 10:06 AM UTC

   We continue to investigate the connectivity issue affecting the Madrid (MAD) 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 MAD PoP will be returned to service once investigation and validation activities have been completed. We will continue to provide updates as more information becomes available.

3. identified Sep 28, 2026, 04:22 PM UTC

   The connectivity issue has been identified and resolved by our technical teams, and the system will continue to be monitored for stability. The MAD (Madrid) PoP will be returned to service during the low traffic period for this PoP. This is scheduled for around 0001UTC Tuesday 29th September. A further update will be posted once this process has been completed.

4. identified Sep 28, 2026, 11:49 PM UTC

   The team is preparing to begin the PoP activation shortly. We will closely monitor the PoP throughout the activation and provide further updates as the process progresses. The next update on this incident will be provided no later than 01:00 UTC on 29 September 2026.

5. monitoring Sep 29, 2026, 01:01 AM UTC

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

6. resolved Sep 29, 2026, 02:05 AM UTC

   Service in the data center has been restored to normal. This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 07:42 AM UTC· resolved Sep 28, 2026, 09:56 AM UTC

1. investigating Sep 28, 2026, 07:42 AM UTC

   We have identified an issue affecting the XSP (Singapore) PoP. Customers may experience increased latency, Error 20 responses, and connectivity impacts related to GRE tunnels. Our teams are actively investigating the issue and working to determine the scope, impact, and root cause. We will provide further updates as soon as additional information becomes available. The next update will not be later than 08:10am UTC

2. monitoring Sep 28, 2026, 07:47 AM UTC

   We have implemented corrective actions and service has returned to normal operation. The affected GRE tunnels have been successfully re-established, and traffic is flowing as expected across the previously impacted locations. Customers should no longer experience the increased latency or Error 20 responses previously observed. We are continuing to monitor the environment closely to ensure stability.

3. identified Sep 28, 2026, 08:26 AM UTC

   We have identified an issue affecting multiple network locations (PoPs). Customers may experience increased latency, encounter Error 20 responses, and may be impacted by GRE tunnel connectivity issues. Our engineering teams are actively investigating the issue to determine the full scope, impact, and underlying cause. We are working to restore normal service as quickly as possible and will provide updates as more information becomes available.

4. identified Sep 28, 2026, 08:39 AM UTC

   We have restored traffic flow across all previously affected PoPs, and GRE tunnel connectivity has been re-established. Traffic is currently routing as expected. While service has stabilized, our engineering teams remain actively engaged in investigating the underlying cause of the issue and monitoring the environment closely. Customers may have experienced increased latency, Error 20 responses, or GRE tunnel connectivity issues during the period of impact. We will continue to provide updates as our investigation progresses - the next update will be no later than 09:09 UTC

5. monitoring Sep 28, 2026, 09:11 AM UTC

   We continue to observe stable operations across the previously affected PoPs, with no further signs of impact at this time. Engineering teams remain engaged and are closely monitoring the environment while the investigation into the underlying cause continues. We will provide a final update once monitoring activities have been completed.

6. resolved Sep 28, 2026, 09:56 AM UTC

   The issue affecting multiple PoPs has been resolved. Services have recovered, and GRE tunnel connectivity has been restored across the impacted locations. Customers should no longer experience elevated latency or Error 20 responses related to this event. Our teams have validated service recovery and continue to monitor the environment to ensure ongoing stability.

Read the full incident report →

Started Sep 23, 2026, 04:42 AM UTC· resolved Sep 23, 2026, 06:00 AM UTC

1. investigating Sep 23, 2026, 04:42 AM UTC

   We are aware of an ABP issue affecting some users on Google Chrome 153 and above. Other browsers and versions are not currently affected. Customer sites are still fully protected by Advanced Bot Protection at this time. Our team is actively working on a fix. Technical teams are investigating. Further updates to follow.

2. investigating Sep 23, 2026, 05:20 AM UTC

   Our teams continue to work on implementing mitigation measures to address the issue. Technical teams are still engaged and actively investigating. Customer sites are still fully protected by Advanced Bot Protection at this time.

3. identified Sep 23, 2026, 05:40 AM UTC

   We have identified the source of the issue affecting the Advanced Bot Protection service. Technical teams are working on a mitigation. Further updates to follow.

4. monitoring Sep 23, 2026, 05:52 AM UTC

   Technical teams have performed remedial actions and the Advanced Bot Protection service has been restored. Technical teams will continue monitoring the system. Further updates to follow.

5. resolved Sep 23, 2026, 06:00 AM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva Advanced Bot Protection service.

Read the full incident report →

Started Sep 22, 2026, 11:29 AM UTC· resolved Sep 23, 2026, 07:57 AM UTC

1. investigating Sep 22, 2026, 11:29 AM UTC

   One of our upstream providers is currently experiencing a major outage. We are contacting the provider to gather more information about the issue. As a mitigation, we have rerouted traffic away from the affected carrier at the impacted PoPs, which has mitigated customer impact. We will continue to closely monitor the environment to ensure ongoing service stability. Further updates will be provided as more information becomes available.

2. monitoring Sep 22, 2026, 11:38 AM UTC

   We have rerouted traffic away from the affected carrier in the impacted PoPs, mitigating customer impact. We will continue to closely monitor the environment to ensure ongoing service stability.

3. monitoring Sep 22, 2026, 02:45 PM UTC

   To maintain service stability, the impacted upstream provider remains bypassed. Our teams continue to closely monitor the environment and are working with the upstream provider to gather further information. Additional updates will be provided as more details become available.

4. monitoring Sep 23, 2026, 07:57 AM UTC

   The affected network path remains bypassed as a precautionary measure to ensure continued service stability across the Imperva network. Following the mitigation actions implemented, service has been restored to normal and no further customer impact has been observed. Our teams continue to closely monitor the environment to ensure ongoing stability. At this time, the bypass remains in place while the external network issue is being addressed. Additional updates will be provided as more information becomes available.

5. resolved Sep 23, 2026, 07:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 17, 2026, 11:11 PM UTC· resolved Sep 18, 2026, 01:30 AM UTC

1. investigating Sep 17, 2026, 11:11 PM UTC

   We are investigating an issue where some customers may receive SIEM logs from IP addresses that are no longer expected to be in use. Our teams are actively investigating the issue and working to identify the cause. We will provide further updates as more information becomes available.

2. investigating Sep 17, 2026, 11:52 PM UTC

   We have identified the source of the issue affecting a subset of customers, resulting in SIEM logs being received from IP addresses that are no longer expected to be in use. Our teams are actively implementing mitigation measures to reduce customer impact and restore expected behavior. We will provide further updates as they become available.

3. identified Sep 18, 2026, 12:25 AM UTC

   Our teams continue to work on implementing mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. Efforts remain focused on reducing customer impact and restoring expected behavior. We will provide additional updates as progress is made.

4. monitoring Sep 18, 2026, 12:59 AM UTC

   Our teams have successfully implemented mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. The observed impact has been mitigated, and services are operating as expected at this time. We are continuing to closely monitor the environment to ensure ongoing stability and confirm the effectiveness of the mitigation. The next update on the issue will be shared no later than 01:30 UTC.

5. resolved Sep 18, 2026, 01:30 AM UTC

   Mitigation measures have been successfully implemented, and after a period of monitoring, our teams have confirmed that services are operating as expected with no further impact observed. This incident is now resolved. We apologize for any inconvenience and thank you for your patience while we worked to address this issue.

Read the full incident report →

Started Sep 17, 2026, 06:57 PM UTC· resolved Sep 18, 2026, 12:09 AM UTC

1. investigating Sep 17, 2026, 06:57 PM UTC

   We are currently investigating an issue that may cause intermittent DNS resolution failures for some customers. Our teams are actively investigating the issue and working to identify the cause and restore consistent DNS resolution. We will provide further updates as more information becomes available.

2. investigating Sep 17, 2026, 07:39 PM UTC

   We continue to investigate intermittent DNS resolution issues that may affect a small number of requests. The issue is highly intermittent and remains limited in scope. Our teams are actively investigating the issue and working to identify the cause and ensure consistent DNS resolution. The next update on this issue will be shared no later than 20:10 UTC.

3. identified Sep 17, 2026, 07:50 PM UTC

   The issue has been identified, and our teams have confirmed the cause of the intermittent DNS resolution failures. The team is currently applying the mitigation in a controlled manner across the affected services. The issue remains intermittent and limited in scope. The next update on the issue will be shared no later that 20:20 UTC.

4. identified Sep 17, 2026, 08:24 PM UTC

   Mitigation efforts are continuing. We are seeing recovery as the targeted fix is progressively applied to the affected services. The next update on the issue will be shared no later than 20:55 UTC.

5. identified Sep 17, 2026, 08:55 PM UTC

   Mitigation and validation efforts are continuing. The team is closely monitoring the service while applying the targeted fix across the remaining affected systems and validating recovery. The next update on the issue will be shared no later than 21:25 UTC.

6. identified Sep 17, 2026, 09:34 PM UTC

   Mitigation and validation efforts remain ongoing. The team continues to apply the targeted fix to the remaining affected systems while closely monitoring the service and validating recovery. The next update on the issue will be shared no later than 22:05 UTC.

7. monitoring Sep 17, 2026, 10:04 PM UTC

   The team has completed the mitigation, and the affected services have been validated to be operating as expected. We will continue to closely monitor the service to ensure the fix remains effective and services remains stable.

8. resolved Sep 18, 2026, 12:09 AM UTC

   The services are now stable, and the issue has been fully mitigated. Post-mitigation validation has been completed, confirming that the services are operating as expected. The incident is now considered resolved.

Read the full incident report →

Started Sep 17, 2026, 09:45 AM UTC· resolved Sep 17, 2026, 10:19 AM UTC

1. investigating Sep 17, 2026, 09:45 AM UTC

   We are investigating an issue affecting the performance of the Imperva Management Console (MY). Customers may encounter elevated latency, login failures, or degraded console performance. Our engineering teams are engaged and investigating the issue with high priority. We will continue to provide updates as our investigation progresses. The next update will not be later than 10:15 UTC.

2. monitoring Sep 17, 2026, 09:56 AM UTC

   The issue affecting the Imperva Management Console (MY) has been resolved, and service has been restored. Customers should now be able to access and use the console normally. Our team will continue to closely monitor the service to ensure stability. The next update will be no later than 10:30 UTC

3. resolved Sep 17, 2026, 10:19 AM UTC

   The issue affecting the Imperva Management Console (MY) has been resolved. Service performance has returned to normal, and customers should no longer experience elevated latency, login issues, or general console degradation. We will continue to monitor the environment to ensure stability. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Sep 10, 2026, 05:34 PM UTC· resolved Sep 10, 2026, 10:31 PM UTC

1. investigating Sep 10, 2026, 05:34 PM UTC

   We have discovered a service degradation, affecting customers accessing the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next Update on this incident will be shared no later than 18:00 UTC

2. investigating Sep 10, 2026, 05:59 PM UTC

   Our technical teams are actively investigating the issue affecting the Management Portal. The teams are working to identify the cause and restore services. Next update on the incident will be shared no later than 18:30 UTC.

3. investigating Sep 10, 2026, 06:30 PM UTC

   We are currently working on remedial actions to mitigate the impact to customers at this time. Further updates will be provided as information becomes available.

4. investigating Sep 10, 2026, 07:29 PM UTC

   We continue to work on the issue affecting the Imperva Management Portal. Our teams are actively working on remedial measures to restore normal functionality. We apologize for the inconvenience and will provide further updates as soon as additional information becomes available. The next update on the issue will be provided no later than 20:30 UTC.

5. investigating Sep 10, 2026, 08:01 PM UTC

   Our technical teams have identified the issue and implemented mitigation measures to restore service. Management Portal functionality is currently being validated, and we are continuing to monitor the environment closely to confirm stability. The next update will be provided as further information becomes available, no later than 20:30 UTC.

6. monitoring Sep 10, 2026, 08:32 PM UTC

   We have completed remedial actions to resolve the service degradation and the Imperva Management Portal is returning to normal service levels. We are continuing to monitoring the system in order to ensure the continued stability of the service. The next update on the issue will be provided no later than 21:00 UTC.

7. monitoring Sep 10, 2026, 09:09 PM UTC

   We are continuing to monitor the system to ensure continued stability. The next update will be provided no later than 21:30 UTC.

8. monitoring Sep 10, 2026, 09:31 PM UTC

   We are continuing to monitor the system to ensure continued stability. The next update will be provided no later than 22:00 UTC.

9. monitoring Sep 10, 2026, 09:59 PM UTC

   The environment remains stable, and we are continuing to monitor performance closely. The next update will be provided no later than 22:30 UTC.

10. resolved Sep 10, 2026, 10:31 PM UTC

    Service levels have been restored and the Imperva Management Portal has returned to normal functionality. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.

Read the full incident report →

Started Sep 10, 2026, 12:45 PM UTC· resolved Sep 11, 2026, 01:50 AM UTC

1. investigating Sep 10, 2026, 12:45 PM UTC

   We are currently investigating an issue affecting the ability to invite new users to the Imperva Management platform. Existing users may continue to access and use the platform as normal. Our team is actively working to identify the cause and restore full functionality. We will provide further updates as more information becomes available.​ ‌The next update will not be later than 13:15 UTC

2. investigating Sep 10, 2026, 01:13 PM UTC

   We are continuing to investigate an issue affecting the creation of new users in the Imperva Management Platform. The impact currently appears to be limited to a subset of customers. Our teams are actively working to identify the cause and restore normal functionality. We apologise for the inconvenience and will provide further updates as soon as additional information becomes available. Next update: no later than 13:35.

3. investigating Sep 10, 2026, 01:34 PM UTC

   We continue to investigate an issue affecting the creation of new users in the Imperva Management Platform. At this time, we are assessing whether the issue is intermittent rather than limited to a specific subset of customers. Our teams remain actively engaged in the investigation and are working to better understand the scope and underlying cause of the issue. We apologise for the inconvenience and will provide further updates as soon as additional information becomes available. Next update: no later than 13:55 UTC.

4. investigating Sep 10, 2026, 01:54 PM UTC

   We continue to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems and working to identify the root cause. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available. Next update: no later than 14:15 UTC.

5. investigating Sep 10, 2026, 02:16 PM UTC

   We are continuing to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems to identify the root cause and determine the appropriate resolution. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available. Next update: no later than 14:35 UTC.

6. investigating Sep 10, 2026, 02:38 PM UTC

   We are continuing to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems to identify the root cause and determine the appropriate resolution. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available. Next update: no later than 14:58 UTC.

7. investigating Sep 10, 2026, 03:01 PM UTC

   We continue to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems and working to identify the root cause. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available. Next update: no later than 15:20 UTC.

8. investigating Sep 10, 2026, 03:25 PM UTC

   We continue to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems and working to identify the root cause. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available. Next update: no later than 15:44 UTC.

9. investigating Sep 10, 2026, 03:49 PM UTC

   We are continuing to investigate the issue preventing new user invitations on the My Management platform. Existing users can continue using the platform as normal. We will provide another update as more information becomes available. Next update: no later than 16:09 UTC.

10. investigating Sep 10, 2026, 04:11 PM UTC

    We are continuing to investigate the issue preventing new user invitations on the My Management platform. Existing users can continue using the platform as normal. We will provide another update as more information becomes available. Next update: no later than 16:30 UTC.

11. investigating Sep 10, 2026, 04:58 PM UTC

    We are continuing to investigate an issue preventing new user invitations on the My Management platform. Additionally, due to a separate issue, some customers may experience difficulties accessing or loading the My Management platform. Our teams are actively investigating this issue as well and working to identify the root cause. Next update on the issue will be shared no later that 17:27 UTC.

12. investigating Sep 10, 2026, 05:29 PM UTC

    Our investigation into the issue preventing new user invitations on the My Management platform is ongoing. The relevant teams continue to work on identifying the root cause and implementing a resolution. Additionally, due to a separate issue, some customers may experience difficulties accessing or loading the My Management platform. Our teams are actively investigating this issue as well and working to identify the root cause. Next update on the issue will be shared no later than 18:00 UTC.

13. investigating Sep 10, 2026, 06:04 PM UTC

    Our investigation into the issue preventing new user invitations on the My Management platform is continuing. The relevant teams remain engaged in identifying the root cause and working towards a resolution. Separately, we continue to investigate the issue affecting some customers who may experience difficulties accessing or loading the My Management platform. The relevant teams are actively working to identify the cause and restore normal functionality. Next update on the issue will be shared no later than 18:35 UTC

14. investigating Sep 10, 2026, 06:30 PM UTC

    Our investigation into the issue preventing new user invitations on the My Management platform is continuing. The teams have identified a potential contributing factor related to the user management functionality and are continuing to investigate to confirm the root cause and determine the appropriate resolution. Separately, we continue to investigate the issue affecting some customers who may experience difficulties accessing or loading the My Management platform. The relevant teams remain actively engaged in identifying the cause and working towards restoring normal functionality. The next update on the issue will be provided no later than 19:05 UTC.

15. identified Sep 10, 2026, 07:05 PM UTC

    We have identified a potential cause for the issue preventing new user invitations on the My Management platform. The relevant teams are actively investigating and working towards implementing a resolution. Separately, the investigation into the issue affecting some customers who may experience difficulties accessing or loading the My Management platform continues. The relevant teams remain engaged in identifying the cause and restoring normal functionality. We will provide further updates as more information becomes available.

16. identified Sep 10, 2026, 08:24 PM UTC

    The relevant teams continue to actively investigate the issue affecting new user invitations and are working towards implementing a resolution. Separately, for the issue affecting some customers who experienced difficulties accessing or loading the My Management platform, our technical teams have identified the issue and implemented mitigation measures to restore service. Management Portal functionality is currently being validated, and we continue to monitor the environment closely to confirm stability. We will provide further updates as more information becomes available.

17. identified Sep 10, 2026, 08:42 PM UTC

    The issue affecting new user invitations remains under investigation, with the relevant teams continuing to work towards a resolution. Access for existing users to the My Management platform has been restored. The technical teams have completed the required remedial actions, and the platform is currently being monitored closely to confirm stability. We will provide further updates as more information becomes available.

18. monitoring Sep 10, 2026, 10:03 PM UTC

    The issue affecting user management and preventing new user invitations on the My Management platform has been resolved. The relevant teams have completed the required remediation, and user management functionality has been restored. The platform is currently being monitored closely to confirm continued stability.

19. resolved Sep 11, 2026, 01:50 AM UTC

    The issue affecting user management has been resolved. Based on successful testing and continued stability, we have confirmed that the service is operating as expected, and the incident is considered resolved.

Read the full incident report →

Started Sep 09, 2026, 05:31 PM UTC· resolved Sep 09, 2026, 10:29 PM UTC

1. investigating Sep 09, 2026, 05:31 PM UTC

   We have discovered a service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next Update on this incident will be shared no later than 18:00 UTC

2. investigating Sep 09, 2026, 06:03 PM UTC

   Our technical teams are actively investigating an issue affecting access to the Management Portal. The teams are working to identify the cause and restore services. Next update on the incident will be shared no later than 18:32 UTC.

3. investigating Sep 09, 2026, 06:16 PM UTC

   Our technical teams continue to actively investigate an issue affecting the ability to log in to the Management Portal. Customer sites remain fully protected at this time, with no impact to their protection services. Next update on the incident will be shared no later than 18:46 UTC.

4. investigating Sep 09, 2026, 06:53 PM UTC

   Our technical teams continue to investigate the issue affecting access to the Management Portal. Following adjustments to the affected services, we are seeing signs of improvement, including successful login attempts. The teams are continuing to investigate the underlying root cause and work toward a permanent resolution. Customer websites and traffic remain fully protected at this time. Further updates will be provided as the investigation progresses.

5. investigating Sep 09, 2026, 07:24 PM UTC

   Login to the Management Portal has been restored, and users are currently able to access the portal. Most core functionality is available; however, Certificate Management functionality remains unavailable while our technical teams continue to investigate and work toward full service restoration. Customer websites and traffic remain fully protected at this time. Next update on this incident will be shared no later than 19:55 UTC.

6. identified Sep 09, 2026, 07:33 PM UTC

   Our technical teams have identified the issue and are actively working toward full service restoration. At this time, login access to the Management Portal has been restored. However, SSL Certificate Management functionality remains unavailable, and the team is working to apply a fix and restore this functionality. Customer websites and traffic remain fully covered by SSL and protected at this time.

7. identified Sep 09, 2026, 08:33 PM UTC

   Our technical teams continue to work toward fully restoring SSL Certificate Management functionality. Management Portal login and other core functionality are operating as expected. The remaining impact is limited to SSL Certificate Management. Customer websites and traffic remain fully covered by SSL and protected at this time. Further updates will be provided as we continue to work toward full remediation.

8. monitoring Sep 09, 2026, 09:18 PM UTC

   The issues affecting Management Portal login and SSL Certificate Management have been remediated, and all functionality is currently operating as expected. Our technical teams are actively monitoring the environment to confirm service stability and ensure continued normal operation. The next update will be provided as further information becomes available.

9. resolved Sep 09, 2026, 10:29 PM UTC

   Monitoring has confirmed that the environment remains stable, with no further issues observed. The incident is now confirmed as resolved, and normal service has been restored.

Read the full incident report →

Started Sep 08, 2026, 05:03 AM UTC· resolved Sep 08, 2026, 05:37 AM UTC

1. investigating Sep 08, 2026, 05:03 AM UTC

   We have identified an issue in the Madrid, Spain 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. _ _ Further updates will be shared as more information becomes available.

2. identified Sep 08, 2026, 05:22 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Sep 08, 2026, 05:26 AM UTC

   Traffic has been restored to the Madrid, Spain (MAD) Data Center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.

4. resolved Sep 08, 2026, 05:37 AM UTC

   Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service.

Read the full incident report →

Started Sep 02, 2026, 08:21 PM UTC· resolved Sep 03, 2026, 12:33 AM UTC

1. investigating Sep 02, 2026, 08:21 PM UTC

   Imperva has been alerted to the fact that there have been two major fiber cuts in North America. These fiber cuts are within the network of a major upstream carrier. A subset of customer traffic coming to or going from the Imperva network may transit this infrastructure and as a result of this issue, customers may experience connectivity issues, increased latency, or service degradation. We will provide further updates as more information becomes available. The next update will be before 20:50 UTC

2. monitoring Sep 02, 2026, 08:46 PM UTC

   We have rerouted traffic away from the affected carrier in the impacted PoPs, mitigating customer impact. We will continue to closely monitor the environment to ensure ongoing service stability.

3. resolved Sep 03, 2026, 12:33 AM UTC

   Monitoring has shown stable performance following the mitigation measures implemented earlier. This incident is considered resolved at this time. We will continue to monitor the environment as part of our standard operational practices to ensure ongoing service stability.

Read the full incident report →

Started Sep 02, 2026, 04:56 AM UTC· resolved Sep 02, 2026, 07:16 AM UTC

1. investigating Sep 02, 2026, 04:56 AM UTC

   We have identified an issue in the Rio de Janeiro, Brazi 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. Further updates will be shared as more information becomes available.

2. investigating Sep 02, 2026, 05:34 AM UTC

   The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. Further updates will be shared as more information becomes available.

3. investigating Sep 02, 2026, 06:18 AM UTC

   Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency. Further updates will be shared as more information becomes available.

4. investigating Sep 02, 2026, 06:59 AM UTC

   The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP. The next update will be provided no later than 07:30 UTC.

5. identified Sep 02, 2026, 07:00 AM UTC

   The issue has been identified and a fix is being implemented.

6. monitoring Sep 02, 2026, 07:03 AM UTC

   Technical team has successfully activated the PoP, and traffic has been restored to the Janeiro, Brazil (RIO) Data Center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.

7. resolved Sep 02, 2026, 07:16 AM UTC

   Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service.

Read the full incident report →

Started Aug 30, 2026, 09:05 AM UTC· resolved Aug 30, 2026, 10:57 AM UTC

1. investigating Aug 30, 2026, 09:05 AM UTC

   We are currently investigating an issue affecting email notifications. Customers may experience delays or failures in receiving notification and confirmation emails. Our engineering teams are actively working to identify the cause and restore normal notification delivery as quickly as possible. We will provide additional updates as more information becomes available. The next update will be before 09:05 UTC.

2. investigating Aug 30, 2026, 09:27 AM UTC

   Copilot said: Our teams continue to actively investigate the issue affecting email notifications. We are working to identify the underlying cause and restore normal notification delivery as quickly as possible. Customers may continue to experience delays or failures in receiving notification and confirmation emails during this time. We will provide our next update no later than 09:30 UTC

3. identified Aug 30, 2026, 09:37 AM UTC

   We have identified a potential source of the issue affecting email notifications and are actively validating our findings. Our teams are working to implement and verify corrective actions while closely monitoring system behaviour. Customers may continue to experience delays or failures in receiving notification and confirmation emails during this period. We will continue to monitor the effectiveness of the mitigation efforts and provide further updates as additional information becomes available. The next update will be provided before 10:05 UTC.

4. identified Aug 30, 2026, 10:01 AM UTC

   Our investigation into the email notification degradation is ongoing. We have identified the affected notification flow and are actively working to restore normal delivery rates. While mitigation efforts continue, some customers may still experience delays or failures in receiving email notifications. We will continue to monitor the effectiveness of the mitigation efforts and provide further updates as additional information becomes available. The next update will be provided before 10:35 UTC.

5. monitoring Aug 30, 2026, 10:30 AM UTC

   We have implemented mitigation measures and are observing recovery in email notification delivery. Current monitoring indicates notification volumes have returned to expected levels, and email notifications are being processed successfully. We will continue to monitor the service closely to ensure recovery is sustained and to identify any residual impact.

6. resolved Aug 30, 2026, 10:57 AM UTC

   We have implemented corrective actions and confirmed that the affected functionality has been restored. Monitoring has shown normal service operation, and validation efforts indicate that requests are being processed successfully. Our teams will continue to review the incident to better understand the contributing factors and help prevent similar issues in the future. This incident has been resolved.

Read the full incident report →

Started Aug 21, 2026, 07:28 PM UTC· resolved Aug 21, 2026, 10:42 PM UTC

1. investigating Aug 21, 2026, 07:28 PM UTC

   We have identified an issue in the Istanbul, Turkey (SAW ) 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. Next update on the incident will be shared no later than 19:41 UTC

2. identified Aug 21, 2026, 08:02 PM UTC

   We have identified an issue in the Istanbul, Turkey (SAW ) 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.

3. identified Aug 21, 2026, 08:56 PM UTC

   Our teams remain actively engaged in the investigation and remediation. Customers may experience increased latency while traffic remains rerouted. We will provide further updates as additional information becomes available.

4. monitoring Aug 21, 2026, 09:41 PM UTC

   A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal.

5. resolved Aug 21, 2026, 10:42 PM UTC

   Monitoring has confirmed that the PoP is stable and operating normally. The incident has been resolved.

Read the full incident report →