Imperva

Affected: Cloud Security Management Platform

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 08:43 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 2026-10-20 09:04 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 2026-10-20 09:43 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 2026-10-20 10:26 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 2026-10-20 12:54 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 2026-10-20 14:28 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 2026-10-20 16:12 UTC

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

8. resolved 2026-10-20 16:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Imperva's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 17:38 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 18:30 UTC.

2. investigating 2026-10-19 18:34 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 2026-10-19 19:10 UTC

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

4. identified 2026-10-19 19:27 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.

5. identified 2026-10-19 20:30 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 2026-10-19 21:29 UTC

   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.

7. monitoring 2026-10-19 21:35 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 2026-10-19 22:47 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 21:49 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 2026-10-15 22:36 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 2026-10-15 23:05 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 15:18 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 15:30 UTC.

2. identified 2026-10-13 15:30 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 2026-10-13 15:58 UTC

   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. monitoring 2026-10-13 16:28 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...

5. resolved 2026-10-13 17:29 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-13 13:29 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...

2. identified 2026-10-13 13:58 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 2026-10-13 15:38 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 18:00 UTC

4. resolved 2026-10-13 17:44 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Dallas, TX (DAL)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 22:16 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...

2. investigating 2026-10-09 22:42 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 2026-10-09 22:43 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 2026-10-09 22:46 UTC

   We are continuing to investigate this issue.

5. identified 2026-10-09 23:21 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 2026-10-09 23:46 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...

7. monitoring 2026-10-10 09:18 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 2026-10-10 10:11 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Atlanta, GA (ATL), Detroit, MI (DET), Singapore (XSP), Tokyo, Japan (NRT), Warsaw, Poland (WAR)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 08:41 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...

2. investigating 2026-10-05 09:07 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 2026-10-05 09:32 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...

4. investigating 2026-10-05 09:57 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...

5. investigating 2026-10-05 10:26 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...

6. investigating 2026-10-05 11:02 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...

7. investigating 2026-10-05 11:34 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 2026-10-05 11:45 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 2026-10-05 12:11 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...

10. monitoring 2026-10-05 13:06 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...

11. monitoring 2026-10-06 00:42 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...

12. resolved 2026-10-06 01:48 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Frankfurt, Germany (HHN)

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 20:07 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...

2. investigating 2026-10-01 20:39 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...

3. investigating 2026-10-01 21:26 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...

4. investigating 2026-10-01 22:44 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...

5. identified 2026-10-02 00:37 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...

6. resolved 2026-10-02 02:50 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: SIEM Logs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 11:27 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....

2. monitoring 2026-10-01 11:40 UTC

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

3. resolved 2026-10-01 11:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: London 1, UK (LCY)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-09-28 11:42 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Madrid, Spain (MAD)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-28 09:53 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...

2. investigating 2026-09-28 10:06 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...

3. identified 2026-09-28 16:22 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...

4. identified 2026-09-28 23:49 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 2026-09-29 01:01 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 2026-09-29 02:05 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Singapore (XSP)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 07:42 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...

2. monitoring 2026-09-28 07:47 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...

3. identified 2026-09-28 08:26 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...

4. identified 2026-09-28 08:39 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...

5. monitoring 2026-09-28 09:11 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...

6. resolved 2026-09-28 09:56 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Advanced BOT Protection

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 04:42 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...

2. investigating 2026-09-23 05:20 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 2026-09-23 05:40 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 2026-09-23 05:52 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 2026-09-23 06:00 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Chicago 1, IL (CHI), Detroit, MI (DET), Houston, TX (HOU), Los Angeles, CA (SNA), Miami, FL (FLL), Montreal, Canada (YUL), New York 2, NY (EWR), Seattle, WA (SEA), Toronto, Canada (TOR), Vancouver, Canada (VAN)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-22 11:29 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....

2. monitoring 2026-09-22 11:38 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 2026-09-22 14:45 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 2026-09-23 07:57 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...

5. resolved 2026-09-23 07:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: SIEM Logs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 23:11 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...

2. investigating 2026-09-17 23:52 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...

3. identified 2026-09-18 00:25 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...

4. monitoring 2026-09-18 00:59 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....

5. resolved 2026-09-18 01:30 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: CDN and WAF Management

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 18:57 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...

2. investigating 2026-09-17 19:39 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...

3. identified 2026-09-17 19:50 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...

4. identified 2026-09-17 20:24 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 2026-09-17 20:55 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 2026-09-17 21:34 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 2026-09-17 22:04 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 2026-09-18 00:09 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 09:45 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...

2. monitoring 2026-09-17 09:56 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...

3. resolved 2026-09-17 10:19 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 17:34 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 2026-09-10 17:59 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 2026-09-10 18:30 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 2026-09-10 19:29 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....

5. investigating 2026-09-10 20:01 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...

6. monitoring 2026-09-10 20:32 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...

7. monitoring 2026-09-10 21:09 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 2026-09-10 21:31 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 2026-09-10 21:59 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 2026-09-10 22:31 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Account and User Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 12:45 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...

2. investigating 2026-09-10 13:13 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...

3. investigating 2026-09-10 13:34 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...

4. investigating 2026-09-10 13:54 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...

5. investigating 2026-09-10 14:16 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...

6. investigating 2026-09-10 14:38 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...

7. investigating 2026-09-10 15:01 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...

8. investigating 2026-09-10 15:25 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...

9. investigating 2026-09-10 15:49 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 2026-09-10 16:11 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 2026-09-10 16:58 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...

12. investigating 2026-09-10 17:29 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...

13. investigating 2026-09-10 18:04 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...

14. investigating 2026-09-10 18:30 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...

15. identified 2026-09-10 19:05 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...

16. identified 2026-09-10 20:24 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...

17. identified 2026-09-10 20:42 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...

18. monitoring 2026-09-10 22:03 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...

19. resolved 2026-09-11 01:50 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 17:31 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 2026-09-09 18:03 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 2026-09-09 18:16 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...

4. investigating 2026-09-09 18:53 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...

5. investigating 2026-09-09 19:24 UTC

   Login to the Management Portal has been restored, and users are currently able to access the portal. Most core functionality is available; however, SSL Certificate Management functionality remains unavailable while our technical teams continue to investigate and work toward full...

6. identified 2026-09-09 19:33 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...

7. identified 2026-09-09 20:33 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...

8. monitoring 2026-09-09 21:18 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...

9. resolved 2026-09-09 22:29 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Madrid, Spain (MAD)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-08 05:03 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...

2. identified 2026-09-08 05:22 UTC

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

3. monitoring 2026-09-08 05:26 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 2026-09-08 05:37 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Chicago 1, IL (CHI), Detroit, MI (DET), Houston, TX (HOU), Los Angeles, CA (SNA), Miami, FL (FLL), Montreal, Canada (YUL), New York 2, NY (EWR)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-02 20:21 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...

2. monitoring 2026-09-02 20:46 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 2026-09-03 00:33 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Rio de Janeiro, Brazil (RIO)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 04:56 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...

2. investigating 2026-09-02 05:34 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...

3. investigating 2026-09-02 06:18 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...

4. investigating 2026-09-02 06:59 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 2026-09-02 07:00 UTC

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

6. monitoring 2026-09-02 07:03 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 2026-09-02 07:16 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.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: CDN and WAF Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-30 09:05 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...

2. investigating 2026-08-30 09:27 UTC

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

3. identified 2026-08-30 09:37 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...

4. identified 2026-08-30 10:01 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...

5. monitoring 2026-08-30 10:30 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...

6. resolved 2026-08-30 10:57 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Istanbul, Turkey (SAW)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-21 19:28 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...

2. identified 2026-08-21 20:02 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 2026-08-21 20:56 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 2026-08-21 21:41 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 2026-08-21 22:42 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Queretaro, Mexico (QRO)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-19 22:17 UTC

   We have identified an issue in the Queretaro, Mexico (QRO) 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...

2. identified 2026-08-19 22:40 UTC

   We are experiencing issues with upstream providers in the region. To minimize customer impact, the affected PoP has been bypassed and traffic is being rerouted through an alternate data center. Customers may experience some increased latency while the reroute is in place. Our...

3. identified 2026-08-20 00:38 UTC

   We continue to work closely with our upstream providers, who have acknowledged the issue and are actively working to restore normal service. To maintain service continuity, the affected PoP will remain bypassed while the providers work on restoration. Customers may experience...

4. identified 2026-08-20 04:39 UTC

   The Queretaro, Mexico (QRO) PoP remains bypassed while our upstream providers continue working on service restoration. We will provide the next update as more information becomes available.

5. identified 2026-08-20 06:37 UTC

   One of our upstream providers has now restored service, and connectivity through that provider is back online. Work is currently in progress with the remaining upstream provider to restore full connectivity. The QRO PoP remains bypassed as restoration activities continue. We...

6. identified 2026-08-20 06:55 UTC

   One of our upstream providers has now restored service, and connectivity through that provider is back online. Work is currently in progress with the remaining upstream provider to restore full connectivity. The QRO PoP remains bypassed as restoration activities continue. We...

7. monitoring 2026-08-20 10:07 UTC

   Traffic has been restored to the affected QRO PoP and the bypass has been removed. Upstream providers continue to monitor the previously reported network issue, and service remains stable and operational at this time. We are closely monitoring performance and connectivity to...

8. monitoring 2026-08-20 10:37 UTC

   Traffic has been restored to the affected QRO PoP and the bypass has been removed. Upstream providers continue to monitor the previously reported network issue, and service remains stable and operational at this time. We are closely monitoring performance and connectivity to...

9. resolved 2026-08-20 11:16 UTC

   The issue affecting connectivity through the QRO PoP has been resolved. Following confirmation of stable network conditions, traffic has been restored to the QRO PoP and the bypass has been removed. We have continued to monitor service following the restoration and are no longer...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Frankfurt, Germany (HHN)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-19 03:04 UTC

   We have discovered a service degradation that affected the Frankfurt (HHN) Data Center Issue which may have resulted in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Service was restored in the PoP,...

2. resolved 2026-08-19 03:55 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. We appreciate your patience and understanding...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Ashburn, VA (WDC)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-13 16:53 UTC

   We have identified a condition where a subset of customer origin fetch traffic from our proxy servers in the WDC PoP is experiencing sub-optimal routing. In these cases, origin fetch is getting routed to specific third-party CDN networks in the APAC region instead of Eastern US,...

2. investigating 2026-08-13 17:55 UTC

   We are actively exploring potential mitigation options to address the sub-optimal routing and reduce the impact on affected origin fetch traffic. In parallel, we are working with the third-party provider to address the underlying geolocation issue. We will provide further...

3. investigating 2026-08-13 20:16 UTC

   We have confirmed with the third-party CDN provider that they have begun to work on a configuration update which will correct the sub-optimal routing, with an ETA of up to 2 weeks before it is globally deployed. In the meantime, we continue to explore mitigation steps which we...

4. identified 2026-08-13 21:12 UTC

   We have confirmed a solution which mitigates the sub-optimal routing and can be implemented by request on a per-customer basis for impacted websites while we continue to await the permanent fix by the third-party CDN provider.

5. identified 2026-08-24 16:05 UTC

   We are currently seeing an unexpected delay from the third-party CDN provider, and there is a possibility that the timeline for the complete remediation may be extended. We continue to actively engage with and push the provider while they work on the permanent fix. In the...

6. monitoring 2026-09-02 13:11 UTC

   The third-party CDN provider has implemented a fix to address the routing issue. Based on our current observations and log data, traffic is routing as expected, and origin fetch traffic is operating normally, with latency levels within expected ranges. We are continuing to...

7. resolved 2026-09-02 17:30 UTC

   The third-party CDN provider has completed the remediation for the routing issue. We have confirmed through our observations and log data that traffic continues to route as expected, with origin fetch traffic operating normally and latency within expected ranges. The service has...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Montreal, Canada (YUL)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-13 08:22 UTC

   We are investigating an issue affecting traffic reaching our YUL (Montreal, Canada) PoP. Customers may experience connectivity issues, increased latency, or service disruptions when traffic is routed through this location. Our teams are actively investigating the issue and...

2. monitoring 2026-08-13 08:34 UTC

   We have mitigated the issue affecting the YUL (Montreal, Canada) PoP by removing the affected PoP from service and redirecting traffic to alternate locations. Traffic is now being served by other PoPs, and service has stabilised. Our teams continue to investigate the underlying...

3. monitoring 2026-08-13 08:48 UTC

   Traffic is now being served by other PoPs, and service has stabilised. Our teams continue to investigate the underlying cause of the issue affecting the YUL infrastructure and are working towards restoring the PoP to normal operation. We will continue to monitor the environment...

4. monitoring 2026-08-13 09:29 UTC

   We have identified the source of the issue affecting the YUL (Montreal, Canada) PoP and are working on remediation. While completing the remediation may take an extended period of time, service has been stabilised by rerouting traffic through alternate Points of Presence (PoPs)....

5. monitoring 2026-08-14 08:12 UTC

   We have identified the source of the issue affecting the YUL (Montreal, Canada) PoP and continue to work on remediation. Service remains stable as traffic is being served through alternate Points of Presence (PoPs). Our updated expected ETA for restoring the YUL PoP to normal...

6. monitoring 2026-08-17 05:44 UTC

   Remediation is nearing completion, with the majority of the required work now finished. Only a few final activities remain before the YUL PoP can be safely reactivated. In the meantime, service remains stable as traffic continues to be routed through alternate Points of...

7. monitoring 2026-08-17 10:49 UTC

   Remediation activities have been completed, and the YUL (Montreal, Canada) PoP has been successfully restored and returned to service. Traffic is once again being served through the YUL PoP as normal. We are continuing to closely monitor the environment to ensure stability and...

8. resolved 2026-08-17 13:17 UTC

   The issue affecting the YUL (Montreal, Canada) PoP has been resolved, and the PoP has been successfully returned to normal operation. Traffic is once again being served through the YUL PoP, and validation and monitoring have confirmed that services are operating as expected. We...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Configuration Changes, CDN and WAF Management

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-12 19:59 UTC

   We have discovered a service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. Customer sites are still fully protected at this time. Technical teams are investigating. Further updates to follow.

2. identified 2026-08-12 20:31 UTC

   Technical teams have identified the underlying issue and are actively working on a fix to restore normal configuration publishing. The next update will be provided no later than 21:00 UTC.

3. monitoring 2026-08-12 21:03 UTC

   The technical team has applied a fix to address the issue, and the Publisher has returned to normal operation. Configuration changes are now being processed as expected, and the service has returned to a stable state. The team continues to monitor the system to ensure ongoing...

4. identified 2026-08-12 22:37 UTC

   During our ongoing monitoring, we observed another instance of delayed configuration publishing. The technical team is actively investigating and working on remediation. Customer sites remain protected, and we continue to closely monitor the service.

5. identified 2026-08-12 23:30 UTC

   Our technical teams are actively engaged and working to remediate the issue. We are continuing to monitor the affected services closely and will provide further updates as more information becomes available. Customer sites remain protected.

6. identified 2026-08-13 00:14 UTC

   Our technical teams continue to actively work on the issue affecting configuration publishing. Remediation efforts are underway, and we are closely monitoring the service to ensure a stable recovery. Customer sites remain protected. We will provide further updates as more...

7. identified 2026-08-13 01:31 UTC

   Our technical teams remain actively engaged in addressing the configuration publishing issue. Remediation activities are ongoing, and we continue to closely monitor the service to ensure a stable and sustained recovery. Customer sites remain protected. We will continue to...

8. identified 2026-08-13 02:41 UTC

   Our technical teams continue to actively work on the configuration publishing issue. Remediation is progressing in a controlled manner, with the team working to restore the processing of affected configurations. We are closely monitoring the service and validating the recovery...

9. identified 2026-08-13 03:45 UTC

   Our technical teams continue to actively investigate the configuration publishing issue. Remediation and validation activities are ongoing, and the team is working to restore normal publishing operations while closely monitoring the service. Customer sites remain protected. We...

10. monitoring 2026-08-13 05:40 UTC

    Technical teams have completed the necessary remediation, and configuration propagation through the Imperva Management Portal has returned to normal operating levels. The teams will continue to closely monitor the system to ensure ongoing stability. Further updates will be...

11. resolved 2026-08-13 10:14 UTC

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Denver, CO (DEN), New York 2, NY (EWR), San Jose, CA (SFO), Seattle, WA (SEA)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 17:08 UTC

   We identified a brief issue impacting our Points of Presence (PoPs), which may have caused infrastructure tunnel disconnections and intermittent website timeouts for some customers. The issue has now recovered, and services are operating normally. Our teams are actively...

2. investigating 2026-08-07 17:58 UTC

   Services remain stable across all previously affected Points of Presence (PoPs). Our teams continue to closely monitor the environment and analyze the event to confirm the underlying cause and ensure the continued stability of our services.

3. monitoring 2026-08-07 18:57 UTC

   A potential contributing factor has been identified. Services remain stable across all affected Points of Presence (PoPs), and no further issues have been observed since recovery. Our teams continue to closely monitor the environment to ensure ongoing service stability.

4. resolved 2026-08-07 19:50 UTC

   The incident has been resolved, and services have remained stable across all affected Points of Presence (PoPs).

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: CDN and WAF Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 11:56 UTC

   We are currently investigating reports of a potential issue affecting the generation and/or delivery of real-time WAF alerts. Some customers may experience delays in receiving WAF alerts or observe that expected real-time notifications are not being triggered. We are actively...

2. identified 2026-08-05 12:23 UTC

   We have identified the underlying cause of the issue affecting real-time WAF alerts. Our investigation indicates that the impact is limited to a subset of customers. WAF protection remains fully operational. This issue affects real-time alerting only and does not impact traffic...

3. monitoring 2026-08-05 12:35 UTC

   A fix has been implemented to address the issue affecting real-time WAF alerts, and we are observing recovery across impacted services. WAF protection remained fully operational throughout the incident. The issue was limited to real-time alerting and did not impact traffic...

4. resolved 2026-08-05 12:56 UTC

   The issue affecting real-time WAF alerts has been resolved. Following the implementation of a fix and a period of monitoring, we have confirmed that real-time WAF alert delivery has returned to normal operation. WAF protection remained fully operational throughout the incident,...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Support Phone Systems

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-29 01:29 UTC

   We are aware of an issue affecting our support phone system globally. Users may be unable to reach support by phone. Our team is actively investigating the issue and working to restore service as quickly as possible. We apologize for the inconvenience . The next Status Update on...

2. investigating 2026-07-29 02:10 UTC

   We are currently aware of a global issue impacting our support phone system. As a result, users may be unable to contact Support by phone. Our team is actively investigating the issue and working to restore service as quickly as possible. We apologize for any inconvenience this...

3. investigating 2026-07-29 03:07 UTC

   We are currently investigating reports of a global issue impacting access to our support phone system. At this time, support phone numbers are operating normally, and users should be able to contact Support by phone. Customers are encouraged to use the Customer Portal to submit...

4. identified 2026-07-29 04:32 UTC

   The issue has been identified, and our team is actively implementing corrective actions while monitoring the recovery progress. Support phone numbers are currently operating normally, and users should be able to contact Support by phone. Customers are encouraged to use the...

5. monitoring 2026-07-29 05:34 UTC

   Our team is actively monitoring the service to ensure stability and continued availability. Support phone numbers are operating normally, and users should be able to contact Support by phone. Customers can continue to use the Customer Portal to submit support requests with the...

6. monitoring 2026-07-29 06:26 UTC

   Our team continues to monitor the service to ensure stability and ongoing availability. Support phone numbers are operating normally, and users can contact Support by phone. Customers may continue to use the Customer Portal to submit support requests with the appropriate...

7. monitoring 2026-07-29 07:10 UTC

   Our team continues to monitor the service to ensure stability and ongoing availability. Support phone numbers are operating normally, and users can contact Support by phone. Customers may continue to use the Customer Portal to submit support requests with the appropriate...

8. resolved 2026-07-29 08:39 UTC

   The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. We appreciate your patience and understanding throughout this incident. The status updates are an integral part of proactive...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Support Ticketing System

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 06:09 UTC

   We are investigating a potential issue affecting the Support Ticketing System. Customers may be experiencing issues logging into the Support Portal. Our technical teams are actively investigating the issue. The next update on the issue will be shared no later than 6:39 UTC.

2. investigating 2026-07-27 06:49 UTC

   Our teams are actively working to restore access to the Support Ticketing System. While this work is ongoing, customers experiencing issues accessing the Support Portal can reach our Support team for urgent assistance by calling +1 410 469 1651. Thank you for your patience as we...

3. monitoring 2026-07-27 07:45 UTC

   The issue preventing some customers from logging in to the Customer Support Portal has been resolved. Technical teams have completed remedial actions, and the portal has returned to normal operation. We are continuing to monitor the service to ensure stability and will provide a...

4. resolved 2026-07-27 08:32 UTC

   The issue that prevented some customers from logging in to the Customer Support Portal has been fully resolved. Technical teams implemented corrective actions and validated that normal login functionality has been restored. The Customer Support Portal is operating normally, and...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Rio de Janeiro, Brazil (RIO)

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-17 05:06 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. The status updates are an integral part of...

2. identified 2026-07-17 06:06 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. Next update on the...

3. identified 2026-07-17 06:41 UTC

   Our team is actively working to resolve the issue. To maintain service availability, traffic has been rerouted through an alternate data center in the region. Customers may experience increased latency while this temporary routing remains in place. Next update on the issue will...

4. identified 2026-07-17 07:14 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. We will provide the next...

5. identified 2026-07-17 07:46 UTC

   Our team has identified a hardware issue within the routing infrastructure and is actively working with the vendor to troubleshoot and resolve the issue. To maintain service availability, traffic continues to be temporarily rerouted through an alternate data center in the...

6. identified 2026-07-17 08:24 UTC

   We are actively working with Hardware vendor to resolve 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. The...

7. identified 2026-07-17 15:25 UTC

   We have worked with the hardware vendor to address the underlying issue. Based on the current assessment and successful health checks, the team has scheduled the affected PoP to be reactivated at 03:00 UTC on 18 July 2026. To maintain service availability, traffic continues to...

8. monitoring 2026-07-18 05:35 UTC

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

9. resolved 2026-07-18 06:30 UTC

   The technical team has implemented the required fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally, and the PoP has been fully restored to normal operation. We appreciate your patience and...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Johannesburg, South Africa (QRA)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 15:38 UTC

   We have identified a potential issue in the Johannesburg, South Africa (QRA) 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...

2. identified 2026-07-10 16:04 UTC

   The team has identified the underlying issue and implemented a fix. To ensure business continuity and validate service stability, the Johannesburg, South Africa (QRA) PoP is scheduled to be reactivated at 23:00 UTC . In the meantime, traffic is being rerouted through an...

3. identified 2026-07-10 23:06 UTC

   Our team is currently working to reactivate the affected Point of Presence (PoP). We will provide another update once the PoP has been successfully restored. In the meantime, traffic is being rerouted through an alternate data center within the region to maintain service...

4. monitoring 2026-07-10 23:10 UTC

   Technical team has successfully activated the PoP, and traffic has been restored to the Johannesburg, South Africa (QRA) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for...

5. resolved 2026-07-10 23:38 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. We appreciate your patience and understanding...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Queretaro, Mexico (QRO)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-01 21:40 UTC

   Technical teams are investigating a potential issue in the Querétaro, MX (QRO) data center. The next Status Update on this Incident will be provided no later than 10:11 UTC. Further updates to follow. The status updates are an integral part of proactive monitoring and...

2. identified 2026-07-01 21:54 UTC

   The technical teams have identified an issue affecting the Querétaro, MX (QRO) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served...

3. identified 2026-07-01 22:52 UTC

   The technical teams have identified an issue affecting the Querétaro, MX (QRO) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served...

4. identified 2026-07-02 04:59 UTC

   The technical teams have identified an issue impacting the Querétaro, Mexico (QRO) data center. To maintain service stability, the PoP will remain in bypass mode as a precaution and is scheduled to be restored during off-peak hours. Customer traffic continues to be served...

5. monitoring 2026-07-02 07:15 UTC

   Technical team has successfully activated the PoP, and traffic has been restored to the Querétaro, MX (QRO) data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service....

6. resolved 2026-07-02 08:18 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Web Application Performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-11 08:07 UTC

   We are currently investigating increased latency affecting Imperva Cloud WAF protected sites. At this time, a portion of Imperva Cloud WAF customers may experience slower response times when accessing protected applications through Imperva. Our teams are actively investigating...

2. monitoring 2026-06-11 08:15 UTC

   The issue causing increased latency for Imperva Cloud WAF protected sites has been mitigated. Service performance has returned to normal, and our teams are continuing to monitor closely to ensure continued stability. We will provide a final update once monitoring is complete....

3. resolved 2026-06-11 08:39 UTC

   This issue has been resolved. Our teams have confirmed that service performance for Imperva Cloud WAF protected sites has returned to normal and remained stable following mitigation. We will continue to monitor service health as part of our standard operational processes. Thank...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 18:53 UTC

   We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next update on the issue will be provided no later than 19:23 UTC.

2. investigating 2026-06-10 19:24 UTC

   The team continues to actively investigate the issue and work toward resolution. At this time, the impact is limited to customer access to the Management Portal. Customer websites and protection services remain fully operational and continue to be protected as expected. Next...

3. investigating 2026-06-10 19:54 UTC

   Technical teams continue to actively investigate the issue. A potential contributing factor has been identified, and teams are currently working to validate and address it. Next update on the issue will be provided no later than 20:24 UTC.

4. identified 2026-06-10 20:19 UTC

   We have identified the underlying cause of the issue and have applied a fix. The issue affected access to the Management Portal and a subset of API requests. We are seeing signs of recovery following the implementation of the fix, and our teams are actively validating service...

5. monitoring 2026-06-10 20:42 UTC

   A fix has been successfully implemented, and services have been restored. Our teams have validated the recovery and are continuing to closely monitor the environment to ensure ongoing stability. Next update on the issue will be provided no later than 21:42 UTC.

6. monitoring 2026-06-10 21:43 UTC

   Services remain stable following the implementation of the fix, and no further issues have been observed. Our teams will continue to closely monitor the environment for an extended period to ensure stability. Next update on the issue will be provided no later than 23:43 UTC.

7. monitoring 2026-06-10 23:47 UTC

   Services remain stable, and no further issues have been observed. Our teams will continue to closely monitor the environment to ensure ongoing stability and verify that all services continue to operate as expected. Next update on the issue will be provided no later than 01:45...

8. resolved 2026-06-11 00:43 UTC

   Monitoring has confirmed that services remain stable following the implementation of the fix and the completion of validation activities. No further issues have been observed.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Sao Paulo, Brazil (SAO)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-03 13:29 UTC

   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. Next update will be shared no later than 14:00 UTC. The status...

2. investigating 2026-06-03 13:59 UTC

   Technical teams are continuing to working on a fix for the data center issue. 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 will be shared no later...

3. monitoring 2026-06-03 14:25 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. Next update will be shared no later than 14:56 UTC. The status updates are an integral part of proactive monitoring...

4. resolved 2026-06-03 14:55 UTC

   Service in the data center has been restored to normal. 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform, Web Application Performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-03 08:36 UTC

   We are currently investigating an issue causing slowness on the Management Platform and Customers accessing onboarded sites from the APAC region may experience intermittent latency or delays when reaching their protected websites. Our teams are actively investigating the cause...

2. identified 2026-06-03 08:59 UTC

   We have identified the source of the service degradation causing slowness on the Management Platform and customers accessing onboarded sites from the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Next update will be...

3. monitoring 2026-06-03 09:11 UTC

   Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Next update will be shared no later than 09:42 UTC. Further updates to follow. The status updates are an...

4. resolved 2026-06-03 09:40 UTC

   The incident has been resolved and normal service levels have been restored for the Management Portal. 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...

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: New York 2, NY (EWR)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-29 13:24 UTC

   We are investigating an issue in the New York 2, NY (EWR) 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 next update on the incident will be...

2. investigating 2026-05-29 13:56 UTC

   We continue to investigate the issue affecting the data center. Traffic remains rerouted through an alternate data center in the region while troubleshooting efforts are ongoing. The next update on the incident will be shared no later than 14:25 UTC.

3. investigating 2026-05-29 14:29 UTC

   Investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting and analysis efforts. Teams are also investigating a recent increase in anomalous traffic to determine whether it is contributing to the observed behavior. Traffic continues to be...

4. investigating 2026-05-29 15:27 UTC

   The investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting. Customer traffic continues to be served through an alternate PoP in the region to minimize impact while investigation and mitigation efforts continue. The next update on the...

5. investigating 2026-05-29 16:25 UTC

   The investigation remains ongoing, with multiple technical teams continuing to analyze the available data and evaluate potential contributing factors. Customer traffic continues to be served through alternate PoPs in the region to maintain service continuity while...

6. investigating 2026-05-29 17:25 UTC

   Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active. Customer traffic continues to be...

7. investigating 2026-05-29 17:28 UTC

   Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active. Customer traffic continues to be...

8. investigating 2026-05-29 18:26 UTC

   The investigation is still ongoing, with multiple technical teams actively reviewing available data and evaluating possible contributing factors. At this stage, there are no major developments to report, and troubleshooting activities continue. Customer traffic remains routed...

9. investigating 2026-05-29 19:37 UTC

   We are still investigating an issue affecting one of our points of presence (EWR), which may cause intermittent connectivity or latency. Traffic has been rerouted through alternate locations to maintain service continuity while our teams continue working toward resolution. Next...

10. investigating 2026-05-29 20:20 UTC

    Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center. The next update will be provided no later than 21:20 UTC.

11. investigating 2026-05-29 21:34 UTC

    Our Network Engineering teams remain actively engaged in investigating and mitigating the connectivity issues impacting the New York 2, NY (EWR) data center. The next update will be provided no later than 22:34 UTC.

12. identified 2026-05-29 22:46 UTC

    The technical teams have localized the problem and addressed it. The EWR PoP will remain bypassed until a scheduled maintenance window of 0400 to 0800 UTC on 1 June 2026. The next update will be provided following the reactivation of the EWR PoP.

13. identified 2026-05-29 23:41 UTC

    Technical teams have identified and remediated the underlying issue. As a precautionary measure, the EWR PoP will remain bypassed while monitoring continues. An estimated timeline for reactivation will be provided shortly.

14. identified 2026-05-30 15:19 UTC

    The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.

15. identified 2026-06-03 11:01 UTC

    The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.

16. identified 2026-06-04 04:31 UTC

    A fix has been implemented, and traffic has been restored to the data center. We are continuing to monitor to ensure that service has returned to normal. The next update will be provided no later than 05:01 UTC.

17. monitoring 2026-06-04 05:00 UTC

    Technical team has successfully activated the PoP, and traffic has been restored to the EWR data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. The next Status...

18. monitoring 2026-06-04 06:01 UTC

    The technical team identified and resolved an unexpected issue affecting range advertisements. Continuous monitoring is underway to validate service stability and will confirm full operational readiness of the PoP. The PoP is now active, and traffic has been restored to the EWR...

19. resolved 2026-06-04 06:30 UTC

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

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Vancouver, Canada (VAN)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-28 19:08 UTC

   We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center. The next update will be provided no later than 19:38 UTC.

2. identified 2026-05-28 19:24 UTC

   We have identified connectivity issues in our Vancouver, Canada (VAN) data center. Traffic is being re-routed to an alternate data center. The next update will be provided no later than 19:54 UTC.

3. identified 2026-05-28 19:54 UTC

   We have identified intermittent connectivity issues affecting the Vancouver, Canada (VAN) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next...

4. identified 2026-05-28 20:44 UTC

   As a precautionary measure, the Vancouver, Canada (VAN) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and...

5. identified 2026-05-28 21:55 UTC

   The technical teams have identified an issue affecting the Vancouver, Canada (VAN) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served...

6. monitoring 2026-05-29 10:18 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. The next update will be provided no later than 11:18 UTC.

7. resolved 2026-05-29 11:05 UTC

   Service in the data center has been restored to normal.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: New York 2, NY (EWR)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-28 18:09 UTC

   We have identified connectivity issues in our New York 2, NY (EWR). traffic is being re-routed to an alternate data-center. Next update will be shared no later then 18:37.

2. identified 2026-05-28 18:23 UTC

   We have identified connectivity issues affecting our New York 2, NY (EWR) data center. Traffic is currently being re-routed to an alternate data center to minimize customer impact. The next update will be provided no later than 18:53 UTC.

3. identified 2026-05-28 18:57 UTC

   We have identified intermittent connectivity issues affecting the New York 2, NY (EWR) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next update...

4. identified 2026-05-28 19:30 UTC

   Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center. The next update will be provided no later than 20:00 UTC.

5. identified 2026-05-28 20:17 UTC

   As a precautionary measure, the New York 2, NY (EWR) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and...

6. identified 2026-05-28 21:54 UTC

   The technical teams have identified an issue affecting the New York 2, NY (EWR) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served...

7. monitoring 2026-05-29 07:25 UTC

   A fix has been implemented, and customer traffic continues to be served normally through the New York 2, NY (EWR) PoP. We will continue to monitor the situation to ensure that service remains normal. The status updates are an integral part of proactive monitoring and transparent...

8. investigating 2026-05-29 08:41 UTC

   During monitoring, the team identified some abnormalities in the network. The engineering team is currently re-investigating the issue, and traffic is being re-routed to an alternate data center. Next update will be shared no later then 09:11 UTC.

9. investigating 2026-05-29 09:12 UTC

   The investigation is ongoing, and technical teams continue to actively troubleshoot and analyze the issue to determine the underlying cause. Next update will be shared no later then 09:42 UTC.

10. investigating 2026-05-29 09:48 UTC

    Investigation is ongoing. Technical teams continue to analyze the issue and validate findings. Customer traffic continues to be served normally through an alternate PoP. Next update will be shared no later then 10:18 UTC.

11. identified 2026-05-29 10:16 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 10:46 UTC.

12. monitoring 2026-05-29 10:57 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. The next update will be provided no later than 12:00 UTC.

13. resolved 2026-05-29 12:01 UTC

    Service in the data center has been restored to normal.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: ABP Management, Advanced BOT Protection

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-27 19:22 UTC

   We have discovered a potential service degradation, affecting some ABP dashboards. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. Further updates to follow. Next update will be shared no later then 19:52 UTC....

2. investigating 2026-05-27 20:04 UTC

   Investigation and remediation activities are currently in progress, with engineering teams actively working to identify the root cause and restore service stability. Next update will be shared no later then 20:33 UTC.

3. monitoring 2026-05-27 20:47 UTC

   Technical teams have implemented mitigation measures and the ABP dashboards are now operating normally. Teams will continue to closely monitor the environment, and further updates will be shared as they become available.

4. monitoring 2026-05-27 22:23 UTC

   The technical team remains in the monitoring phase to ensure service stability and confirm that the issue does not recur. The next update will be shared no later then 22:53 UTC.

5. resolved 2026-05-27 22:52 UTC

   No abnormalities were observed during the monitoring period. The incident has been resolved, and normal service levels have been fully restored for the Imperva Advanced Bot Protection service.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-22 22:56 UTC

   We have discovered a potential issue affecting sites certificates validation. Technical teams are investigating. The next update will be shared no later then 23:25 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status...

2. investigating 2026-05-22 23:39 UTC

   Remediation efforts are ongoing and teams are actively working to stabilize the services. The next update will be communicated at 00:10 UTC.

3. identified 2026-05-22 23:53 UTC

   Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance.

4. resolved 2026-05-22 23:59 UTC

   A fix has been implemented and all services are operating normally. The incident has been successfully resolved,

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Configuration Changes

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 21:06 UTC

   We have discovered a potential service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. The next Status Update on this Incident will be provided no later than 21:36 UTC. The status updates are an integral part of...

2. investigating 2026-05-19 21:44 UTC

   The investigation into the service degradation impacting the Imperva Management Portal is ongoing. Recent configuration changes are experiencing propagation delays, and technical teams are actively investigating the issue. The next status update will be shared no later than...

3. investigating 2026-05-19 22:18 UTC

   The ongoing service degradation affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. remains under active investigation by the Engineering team. The next status update will be shared no later than 22:47 UTC.

4. identified 2026-05-19 22:46 UTC

   Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance. The next update will be communicated at 23:16 UTC.

5. identified 2026-05-19 23:27 UTC

   Technical team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance. The next update will be communicated at 23:56 UTC.

6. identified 2026-05-19 23:58 UTC

   Technical teams have identified the root cause and applied corrective actions. System performance is steadily improving; however, some delays may still be experienced while publishing activity gradually returns to normal. Full synchronization may take a few additional hours. The...

7. identified 2026-05-20 00:36 UTC

   System performance is continuing to recover following the remediation actions implemented by the technical teams. Overall service stability is improving; however, still we're observing delay in publishing. The environment remains under active monitoring by the technical teams....

8. monitoring 2026-05-20 01:12 UTC

   System performance is continuing to recover and is expected to recover in the next few hours. The environment remains under active monitoring by the technical teams. The next update will be communicated at 03:12 UTC.

9. monitoring 2026-05-20 03:12 UTC

   Technical teams are actively working to restore the service following the remediation actions. Some delays may still be experienced while publishing activity gradually returns to normal. Full synchronization may take a few additional hours. The next update will be communicated...

10. monitoring 2026-05-20 05:12 UTC

    Technical teams are still actively working to restore the service following the remediation actions. The next update will be communicated at 07:12 UTC.

11. monitoring 2026-05-20 07:14 UTC

    While base remediation is still on-going, some additional actions have been identified as required in order to restore full service. These actions are required to ensure longer term stability and a seamless return to regular operations. The next Status Update on this issue will...

12. monitoring 2026-05-20 08:13 UTC

    Technical teams continue working to fully restore the Management Console configuration publishing service. Customers may experience delays when publishing new or updated configurations from the Management Console. During this time, recent configuration changes may take longer...

13. monitoring 2026-05-20 09:12 UTC

    We are continuing remediation efforts for the Management Console configuration publishing service. Customers may still experience delays when publishing new or updated configurations from the Management Console. In addition, some customers may experience issues when onboarding...

14. monitoring 2026-05-20 10:10 UTC

    Remediation activities for the Management Console configuration publishing service are ongoing. Multiple teams remain actively engaged and are working to fully restore service functionality. Existing configurations and active protections continue to remain in place. The next...

15. monitoring 2026-05-20 11:10 UTC

    Remediation efforts for the Management Console configuration publishing service are still underway. Multiple teams remain actively engaged and are working to fully restore service functionality. Existing configurations and active protections continue to remain in place. The next...

16. monitoring 2026-05-20 12:11 UTC

    Remediation activities for the Management Console configuration publishing service are ongoing, with multiple teams actively engaged in restoring full service functionality. Imperva is aware of the impact this incident has had on our customers and apologizes for both the scope...

17. monitoring 2026-05-20 12:56 UTC

    Processing of the backlog is complete. We are monitoring the situation carefully, but all changes saved in the UMC are now being published as expected and all pending configuration changes have been applied. We will continue to closely monitor the service until 13:56 UTC.

18. monitoring 2026-05-20 14:10 UTC

    Our monitoring has identified that some configuration changes have not propagated as expected. Engineering teams are actively investigating the issue and continuing remediation efforts to restore normal configuration publishing behavior. The next status update will be provided...

19. investigating 2026-05-20 15:03 UTC

    Following the earlier remediation activities related to the Management Console configuration publishing service, we are currently investigating an additional issue affecting the propagation of configuration changes. Customers may experience delays or inconsistencies when...

20. investigating 2026-05-20 16:02 UTC

    Remediation efforts are ongoing for the issue affecting Management Console configuration propagation. Our engineering teams have identified a potential cause impacting the functionality and are actively working on remediation and validation activities. The next status update...

21. investigating 2026-05-20 17:00 UTC

    We continue to investigate issues affecting the propagation of configuration changes. Customers may experience delays or inconsistencies when publishing new or updated configurations. Our engineering teams remain actively engaged and are continuing remediation efforts to restore...

22. investigating 2026-05-20 18:25 UTC

    Our teams are actively investigating an issue impacting the propagation of configuration updates. Customers may encounter delays or inconsistent behavior while publishing new or modified configurations. Engineering teams continue to work on mitigation and recovery efforts to...

23. investigating 2026-05-20 19:30 UTC

    Our engineering teams are actively working to mitigate the issue and restore full service functionality as quickly as possible. At this time, existing configurations and active protections continue to operate normally and remain fully in effect. The next status update will be...

24. investigating 2026-05-20 20:37 UTC

    Engineering teams are continuing remediation efforts to restore full platform functionality at the earliest opportunity. Meanwhile, all existing configurations and active security protections remain stable and fully operational. The next status update will be provided no later...

25. investigating 2026-05-20 21:49 UTC

    Technical team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance. The next status update will be provided no later than 22:49 UTC.

26. identified 2026-05-20 22:32 UTC

    The investigation has identified a possible contributing factor related to the issue, and the engineering teams are continuing validation and analysis to assess its impact on overall service performance. Meanwhile, although some backlog items are still pending, current...

27. identified 2026-05-21 00:00 UTC

    The Technical teams remain engaged in ongoing validation and analysis efforts to evaluate the impact on overall service performance. While certain backlog items are still awaiting processing, new configuration changes are currently publishing successfully. The next Status Update...

28. identified 2026-05-21 01:56 UTC

    Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. Backlog items are still being processed, while new configuration changes are currently published successfully.

29. identified 2026-05-21 08:30 UTC

    We apologize for the extended time since the last update. Our teams remain actively engaged and continue remediation efforts for the Management Console configuration publishing service. At this stage, newly created or updated configurations are being published without delay. The...

30. identified 2026-05-21 13:52 UTC

    Currently, any new configuration changes made in the UMC are being applied as expected without any extra delay. Some config changes (including Custom TLS Cert Uploads, Rule or Policy creations, deletions or updates, and Site config edits) made during the last 36 hours may not...

31. identified 2026-05-21 16:23 UTC

    Currently, new configuration changes made in the UMC are continuing to be applied successfully. However, we are presently observing an approximate propagation delay of 40 minutes while backlog processing activities continue. Some configuration changes made during the last 36...

32. identified 2026-05-21 16:55 UTC

    Currently, new configuration changes made in the UMC are continuing to be applied successfully. However, we are presently observing an approximate propagation delay of 40 minutes while backlog processing activities continue. Some configuration changes made during the last 36...

33. identified 2026-05-21 18:45 UTC

    The Technical team confirmed that the pending queue has been successfully cleared and is currently executing a script to process the events that were skipped yesterday. Current configuration changes are now publishing as expected. However, some configuration changes made within...

34. identified 2026-05-21 20:53 UTC

    Our technical teams have confirmed that configuration changes are now propagating normally. Remaining backlog processing activities are still ongoing and are expected to complete within approximately one day. The environment continues to be closely monitored, and we will provide...

35. identified 2026-05-22 07:37 UTC

    Monitoring has confirmed that all services are operating as normal with any new provisioning or changes to any site or account configuration. The tasks to work through the previous pending configuration items is still on-going and is expected to complete within the previously...

36. identified 2026-05-22 14:42 UTC

    We expect to complete the processing of all pending config changes within the next hour. Once this is completed and verified, we'll monitor the platform for some time to make sure there are no other issues. We will post the next update no later than 1700UTC.

37. monitoring 2026-05-22 15:31 UTC

    Monitoring has confirmed that all services are operating normally, including new provisioning activities and configuration changes across sites and accounts. Processing of all previously pending configuration items has now been fully completed and verified. We will continue to...

38. resolved 2026-05-22 21:20 UTC

    During the close monitoring period, no further deviations were observed. The incident has been resolved, and normal service operations for the Imperva Management Portal have been fully restored.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Configuration Changes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-16 20:50 UTC

   We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 21:20 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva...

2. investigating 2026-05-16 21:23 UTC

   Engineering team actively investigating the ongoing service degradation impacting the Imperva Management Portal. The next update will be provided at 21:53 UTC.

3. investigating 2026-05-16 22:01 UTC

   The ongoing service degradation affecting the Imperva Management Portal remains under active investigation by the Engineering team. The next update will be communicated at 22:30 UTC.

4. investigating 2026-05-16 22:47 UTC

   Mitigation activities are still in progress, and teams continue working to restore service stability. The next update will be shared once a significant development is available.

5. investigating 2026-05-16 23:43 UTC

   The Imperva Management Portal will be unavailable for the next 30 minutes; however, all applications will remain protected by Cloud WAF. The next update will be communicated at 00:11 UTC.

6. investigating 2026-05-17 00:12 UTC

   Technical team continue to work on remediation activities to restore service stability. The next update will be communicated at 00:42 UTC.

7. investigating 2026-05-17 00:45 UTC

   Investigation is ongoing, and our technical teams are actively working to restore full service stability. The next update will be communicated at 01:15 UTC.

8. investigating 2026-05-17 01:21 UTC

   Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance. The next update will be communicated at 01:50 UTC.

9. investigating 2026-05-17 01:51 UTC

   The investigation is ongoing, and the team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance. The next update will be communicated at 02:20 UTC.

10. investigating 2026-05-17 02:23 UTC

    The investigation is ongoing, and the team continues to actively work towards remediation. The next update will be shared no later than 02:53 UTC.

11. investigating 2026-05-17 02:53 UTC

    Investigation is in progress, and our teams are actively engaged in working toward resolving the issue. The next update will be shared no later than 03:23 UTC.

12. identified 2026-05-17 03:24 UTC

    Technical teams have identified the issue and implemented fixes. We are seeing steady improvements in system performance. Some delays may still persist, and it may take a few hours for publishing activity to fully catch up. The next update will be shared no later than 03:53 UTC.

13. identified 2026-05-17 03:54 UTC

    We continue to see improvements in system performance following the fixes implemented by our technical teams. Service stability is improving, although some delays may still persist as publishing activity continues to catch up over the next few hours. The next update will be...

14. identified 2026-05-17 04:46 UTC

    We continue to work on improving system performance. While some progress has been made, certain delays may still persist. Our teams remain actively engaged in resolving the issue and restoring full service stability. The next update will be shared no later than 05:15 UTC.

15. identified 2026-05-17 05:10 UTC

    We are taking additional actions to improve system performance. These steps are expected to help accelerate recovery and reduce remaining delays. We will continue to share updates as progress continues. The next update will be shared no later than 05:40 UTC.

16. identified 2026-05-17 05:35 UTC

    We are seeing continued progress, with the backlog steadily decreasing and system performance improving. The next update will be shared no later than 06:05 UTC.

17. monitoring 2026-05-17 05:42 UTC

    The backlog has been fully processed, and the system is now operating as expected. We will continue to monitor to ensure ongoing stability.

18. resolved 2026-05-17 06:36 UTC

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Cloud Security Management Platform

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-15 19:22 UTC

   We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication...

2. investigating 2026-05-15 19:51 UTC

   Our technical teams are actively investigating the issue and working on remediation. Next update on this incident will be shared no later than 20:21 UTC.

3. investigating 2026-05-15 20:21 UTC

   Investigations are currently in progress, and the team is actively working on the issue. Next update on this incident will be shared no later than 20:51 UTC.

4. investigating 2026-05-15 21:00 UTC

   Remediation efforts are ongoing, and we are seeing a reduction in login errors. The issue remains intermittent, and teams are actively working to stabilize the services. Next update on this incident will be shared no later than 21:30 UTC.

5. investigating 2026-05-15 21:33 UTC

   Teams continue to work on remediation activities, and a decrease in login-related errors has been observed. While the issue is still occurring intermittently, active efforts are ongoing to restore full service stability. The next update regarding this incident will be provided...

6. investigating 2026-05-15 22:13 UTC

   Teams have identified a possible cause behind the service degradation affecting customers ability to log in to the Imperva Management Portal. Engineering teams are actively engaged in mitigation and recovery efforts to restore service stability. The next update for this incident...

7. identified 2026-05-15 22:14 UTC

   Teams have identified a possible cause behind the service degradation affecting customers ability to log in to the Imperva Management Portal. Engineering teams are actively engaged in mitigation and recovery efforts to restore service stability. The next update for this incident...

8. identified 2026-05-15 22:47 UTC

   Technical teams have completed mitigation actions, and access to the Imperva Support Portal is returning to normal levels. Teams will continue to closely monitor system operations. Rest assured, all applications continue to remain protected by Cloud WAF. However, issues related...

9. monitoring 2026-05-15 23:08 UTC

   Technical teams have performed remedial actions and the Imperva Support Portal access is returning to normal operations. Technical teams will continue monitoring the system.

10. resolved 2026-05-15 23:29 UTC

    The incident has been resolved and normal service levels have been restored for the Imperva Management Portal.

Excerpts are shortened. Read the full incident on Imperva's status page.

Affected: Account and User Management

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-15 08:17 UTC

   We have discovered a potential service degradation, affecting Imperva Management Portal. The Management Portal website is slow to respond to user actions and in some cases user login attempts may also fail. All customer websites remain fully protected at this time. Technical...

2. investigating 2026-05-15 08:53 UTC

   The impact has been identified as isolated to the India region. Technical teams are actively investigating the issue and working towards mitigation. The next update on the incident will be shared no later that 09:22 UTC

3. investigating 2026-05-15 09:21 UTC

   Technical teams are continuing to actively troubleshoot the issue and are working to restore normal service levels. The next update on the incident will be shared no later that 09:50 UTC

4. monitoring 2026-05-15 09:52 UTC

   The issue has been identified as ISP-related. Technical teams have taken mitigation actions, and we are observing improvements in service performance. Monitoring will continue to ensure stability.

5. resolved 2026-05-15 11:42 UTC

   The incident has been resolved and normal service levels have been restored for the Imperva Management Portal.

Excerpts are shortened. Read the full incident on Imperva's status page.