Imperva Outage History

Started Aug 19, 2026, 10:17 PM UTC· resolved Aug 20, 2026, 11:16 AM UTC

1. investigating Aug 19, 2026, 10:17 PM 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 shared no later than 22:45 UTC

2. identified Aug 19, 2026, 10:40 PM 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 teams are actively monitoring the situation and working with the upstream providers. We will provide the next update as more information becomes available.

3. identified Aug 20, 2026, 12:38 AM 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 increased latency during this period. We will provide further updates as more information becomes available.

4. identified Aug 20, 2026, 04:39 AM 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 Aug 20, 2026, 06:37 AM 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 will provide further updates as more information becomes available.

6. identified Aug 20, 2026, 06:55 AM 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 will provide further updates as more information becomes available

7. monitoring Aug 20, 2026, 10:07 AM 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 ensure continued stability and will provide further updates if necessary.

8. monitoring Aug 20, 2026, 10:37 AM 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 ensure continued stability and will provide further updates if necessary.

9. resolved Aug 20, 2026, 11:16 AM 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 observing any impact. This incident is now resolved. We thank you for your patience while we worked to restore normal operations.

Read the full incident report →

Started Aug 19, 2026, 03:04 AM UTC· resolved Aug 19, 2026, 03:55 AM UTC

1. monitoring Aug 19, 2026, 03:04 AM 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, mitigating the impact to customers.

2. resolved Aug 19, 2026, 03:55 AM UTC

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

Read the full incident report →

Started Aug 13, 2026, 04:53 PM UTC· resolved Sep 02, 2026, 05:30 PM UTC

1. investigating Aug 13, 2026, 04:53 PM 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, which is resulting in increased latency for origin fetch, and ultimately reduced performance in website access. While we are working with the third-party CDN on to correct their Geolocation routing information, we are exploring potential workarounds within our equipment to override the sub-optimal routing which is currently in place. We will provide further updates as more information becomes available.

2. investigating Aug 13, 2026, 05:55 PM 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 updates as more information becomes available.

3. investigating Aug 13, 2026, 08:16 PM 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 may be able to implement on a per-customer basis for impacted websites.

4. identified Aug 13, 2026, 09:12 PM 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 Aug 24, 2026, 04:05 PM 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 meantime, if any customer requires urgent assistance, a workaround can be implemented on a case-by-case basis for impacted websites. Further updates will be shared as more information becomes available.

6. monitoring Sep 02, 2026, 01:11 PM 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 closely monitor the service to ensure routing remains stable and customer traffic continues to operate normally.

7. resolved Sep 02, 2026, 05:30 PM 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 remained stable throughout the monitoring period, and the incident is now considered resolved. We appreciate your patience and understanding while we worked with our third-party provider to resolve this issue.

Read the full incident report →

Started Aug 13, 2026, 08:22 AM UTC· resolved Aug 17, 2026, 01:17 PM UTC

1. investigating Aug 13, 2026, 08:22 AM 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 working to identify the root cause. We will provide further updates as more information becomes available. The next update will be before 08:51 UTC

2. monitoring Aug 13, 2026, 08:34 AM 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 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 closely and provide further updates as they become available. The next update will be no later than 09:05 UTC.

3. monitoring Aug 13, 2026, 08:48 AM 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 closely and provide further updates as they become available. The next update will be no later than 09:18 UTC.

4. monitoring Aug 13, 2026, 09:29 AM 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). Traffic continues to be served through alternate locations, and we are not currently observing customer impact. We will continue to work towards restoring the YUL PoP to normal operation and will provide further updates as more information becomes available

5. monitoring Aug 14, 2026, 08:12 AM 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 operation is Monday. We will continue to closely monitor the service and provide further updates as more information becomes available.

6. monitoring Aug 17, 2026, 05:44 AM 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 Presence. Our current target is to complete the remaining activities and restore the YUL PoP to normal operation by Monday. We will continue to closely monitor the service and provide further updates as the work progresses.

7. monitoring Aug 17, 2026, 10:49 AM 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 verify that all services remain fully operational. At this time, no customer impact is expected. We will provide a final update once the incident has been fully resolved.

8. resolved Aug 17, 2026, 01:17 PM 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 will continue to monitor the environment to ensure ongoing stability. Thank you for your patience while we worked to restore full service.

Read the full incident report →

Started Aug 12, 2026, 07:59 PM UTC· resolved Aug 13, 2026, 10:14 AM UTC

1. investigating Aug 12, 2026, 07:59 PM 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 Aug 12, 2026, 08:31 PM 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 Aug 12, 2026, 09:03 PM 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 stability.

4. identified Aug 12, 2026, 10:37 PM 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 Aug 12, 2026, 11:30 PM 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 Aug 13, 2026, 12:14 AM 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 information becomes available.

7. identified Aug 13, 2026, 01:31 AM 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 provide updates as further information becomes available.

8. identified Aug 13, 2026, 02:41 AM 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 as remediation activities continue. Customer sites remain protected. We will provide further updates as more information becomes available.

9. identified Aug 13, 2026, 03:45 AM 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 will continue to provide updates as more information becomes available.

10. monitoring Aug 13, 2026, 05:40 AM 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 provided as they become available.

11. resolved Aug 13, 2026, 10:14 AM 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 investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Started Aug 07, 2026, 05:08 PM UTC· resolved Aug 07, 2026, 07:50 PM UTC

1. investigating Aug 07, 2026, 05:08 PM 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 monitoring the platform to ensure continued stability.

2. investigating Aug 07, 2026, 05:58 PM 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 Aug 07, 2026, 06:57 PM 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 Aug 07, 2026, 07:50 PM UTC

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

Read the full incident report →

Started Aug 05, 2026, 11:56 AM UTC· resolved Aug 05, 2026, 12:56 PM UTC

1. investigating Aug 05, 2026, 11:56 AM 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 assessing the scope and impact of the issue and will provide further updates as more information becomes available. WAF protection remains fully operational. This issue affects real-time alerts only and does not impact traffic inspection or policy enforcement. Our next update will be provided as soon as we have additional information to share.

2. identified Aug 05, 2026, 12:23 PM 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 inspection or policy enforcement. Our teams are working on mitigation and validation efforts. We will provide further updates as we make progress toward resolution. Our next update will be before 12:55 PM UTC

3. monitoring Aug 05, 2026, 12:35 PM 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 inspection or policy enforcement. We are currently monitoring the environment to ensure alert delivery has returned to normal operation and that no further issues are observed. We will continue to provide updates as warranted.

4. resolved Aug 05, 2026, 12:56 PM 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, and traffic inspection and policy enforcement were not impacted. We apologise for any inconvenience caused and appreciate your patience while we worked to resolve this issue.

Read the full incident report →

Started Jul 29, 2026, 01:29 AM UTC· resolved Jul 29, 2026, 08:39 AM UTC

1. investigating Jul 29, 2026, 01:29 AM 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 this Incident will be provided no later than 02:00 UTC The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. investigating Jul 29, 2026, 02:10 AM 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 may cause. The next update on this incident will be provided no later than 02:40 UTC The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region

3. investigating Jul 29, 2026, 03:07 AM 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 support requests with the appropriate severity level for the fastest assistance while our team continues to monitor service stability. The next Status Update on this Incident will be provided no later than 04:00 UTC We apologize for any inconvenience and appreciate your patience. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region

4. identified Jul 29, 2026, 04:32 AM 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 Customer Portal to submit support requests with the appropriate severity level for the fastest assistance while our team continues to monitor service stability. Further updates will be provided as more information becomes available. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

5. monitoring Jul 29, 2026, 05:34 AM 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 appropriate severity level for the fastest assistance. The next Status Update on this Incident will be provided no later than 06:00 UTC The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

6. monitoring Jul 29, 2026, 06:26 AM 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 severity level for the fastest assistance. The next status update for this incident will be provided no later than 07:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

7. monitoring Jul 29, 2026, 07:10 AM 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 severity level for the fastest assistance. The next status update for this incident will be provided no later than 11:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

8. resolved Jul 29, 2026, 08:39 AM 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 monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Started Jul 27, 2026, 06:09 AM UTC· resolved Jul 27, 2026, 08:32 AM UTC

1. investigating Jul 27, 2026, 06:09 AM 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 Jul 27, 2026, 06:49 AM 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 work to resolve the issue.

3. monitoring Jul 27, 2026, 07:45 AM 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 final update once monitoring is complete.

4. resolved Jul 27, 2026, 08:32 AM 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 no further customer impact has been observed. We apologise for the inconvenience and appreciate your patience while we worked to resolve this issue. The incident is now closed.

Read the full incident report →

Started Jul 17, 2026, 05:06 AM UTC· resolved Jul 18, 2026, 06:30 AM UTC

1. identified Jul 17, 2026, 05:06 AM UTC

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

2. identified Jul 17, 2026, 06:06 AM UTC

   The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. Next update on the issue will be shared no later than 6:35 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

3. identified Jul 17, 2026, 06:41 AM 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 be shared no later than 7:10 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

4. identified Jul 17, 2026, 07:14 AM UTC

   Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency. We will provide the next update no later than 7:45 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

5. identified Jul 17, 2026, 07:46 AM 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 region. Customers may continue to experience increased latency while this temporary routing remains in place. Next update on the issue will be shared no later than 8:15 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

6. identified Jul 17, 2026, 08:24 AM 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 next update can be expected around 16:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

7. identified Jul 17, 2026, 03:25 PM 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 be rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. The next update on this incident will be provided no later than 03:15 UTC on 18 July 2026.

8. monitoring Jul 18, 2026, 05:35 AM 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. Next Status Update on this Incident will be provided no later than 6:03 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

9. resolved Jul 18, 2026, 06:30 AM 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 understanding throughout this incident. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Started Jul 10, 2026, 03:38 PM UTC· resolved Jul 10, 2026, 11:38 PM UTC

1. investigating Jul 10, 2026, 03:38 PM 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 an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. identified Jul 10, 2026, 04:04 PM 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 alternate data center in the region. Customers may experience increased latency and intermittent timeouts while the reroute remains in place. The team continues to closely monitor the environment . Next update on the issue will be shared no later than 23:00 UTC.

3. identified Jul 10, 2026, 11:06 PM 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 availability. During this period, customers may experience increased latency and intermittent timeouts. The team continues to closely monitor the environment and is actively working to restore normal service as quickly as possible. Next update on the issue will be shared no later than 23:36 UTC.

4. monitoring Jul 10, 2026, 11:10 PM 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 service. Next Status Update on this Incident will be provided no later than 23:40 UTC.

5. resolved Jul 10, 2026, 11:38 PM 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 throughout this incident.

Read the full incident report →

Started Jul 01, 2026, 09:40 PM UTC· resolved Jul 02, 2026, 08:18 AM UTC

1. investigating Jul 01, 2026, 09:40 PM 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 transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. identified Jul 01, 2026, 09:54 PM 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 normally through an alternate PoP. Engineering teams remain engaged in the investigation. The next Status Update on this Incident will be provided no later than 05:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

3. identified Jul 01, 2026, 10:52 PM 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 normally through an alternate PoP. Engineering teams remain engaged in the investigation. The next Status Update on this Incident will be provided no later than 05:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

4. identified Jul 02, 2026, 04:59 AM 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 without interruption through an alternate PoP. Engineering teams are actively investigating the issue and working toward a resolution. The next status update will be provided no later than 07:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

5. monitoring Jul 02, 2026, 07:15 AM 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. The next Status Update on this Incident will be provided no later than 8:13 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

6. resolved Jul 02, 2026, 08:18 AM 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 understanding throughout this incident. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Started Jun 11, 2026, 08:07 AM UTC· resolved Jun 11, 2026, 08:39 AM UTC

1. investigating Jun 11, 2026, 08:07 AM 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 the cause and working to mitigate the impact. We will provide another update as more information becomes available. The next update will be at 08:36 UTC at the latest.

2. monitoring Jun 11, 2026, 08:15 AM 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. Please note service impact continued for approximately 10 minutes.

3. resolved Jun 11, 2026, 08:39 AM 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 you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Jun 10, 2026, 06:53 PM UTC· resolved Jun 11, 2026, 12:43 AM UTC

1. investigating Jun 10, 2026, 06:53 PM 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 Jun 10, 2026, 07:24 PM 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 update on the issue will be provided no later than 19:54 UTC.

3. investigating Jun 10, 2026, 07:54 PM 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 Jun 10, 2026, 08:19 PM 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 restoration across the impacted components. Next update on the issue will be provided no later than 20:50 UTC.

5. monitoring Jun 10, 2026, 08:42 PM 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 Jun 10, 2026, 09:43 PM 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 Jun 10, 2026, 11:47 PM 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 UTC on 11 June 2026.

8. resolved Jun 11, 2026, 12:43 AM 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.

Read the full incident report →

Started Jun 03, 2026, 01:29 PM UTC· resolved Jun 03, 2026, 02:55 PM UTC

1. identified Jun 03, 2026, 01:29 PM 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 updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. investigating Jun 03, 2026, 01:59 PM 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 than 14:30 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

3. monitoring Jun 03, 2026, 02:25 PM UTC

   A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. Next update will be shared no later than 14:56 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

4. resolved Jun 03, 2026, 02:55 PM 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 affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Started Jun 03, 2026, 08:36 AM UTC· resolved Jun 03, 2026, 09:40 AM UTC

1. investigating Jun 03, 2026, 08:36 AM 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 and working to restore normal service performance. We will provide additional updates as more information becomes available. Next update will be shared no later then 09:00 UTC.

2. identified Jun 03, 2026, 08:59 AM 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 shared no later then 09:30 UTC. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

3. monitoring Jun 03, 2026, 09:11 AM 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 integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

4. resolved Jun 03, 2026, 09:40 AM 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 status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Started May 29, 2026, 01:24 PM UTC· resolved Jun 04, 2026, 06:30 AM UTC

1. investigating May 29, 2026, 01:24 PM 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 shared no later than 13:55 UTC.

2. investigating May 29, 2026, 01:56 PM 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 May 29, 2026, 02:29 PM 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 rerouted through an alternate data center in the region to minimize customer impact while the root cause is being identified. The next update on the incident will be shared no later than 15:28 UTC.

4. investigating May 29, 2026, 03:27 PM 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 incident will be shared no later than 16:27 UTC.

5. investigating May 29, 2026, 04:25 PM 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 troubleshooting efforts and root cause analysis proceed. The next update on the incident will be shared no later than 17:25 UTC.

6. investigating May 29, 2026, 05:25 PM 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 served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed. Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information. becomes available. The next update on the incident will be shared no later than 18:25 UTC.

7. investigating May 29, 2026, 05:28 PM 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 served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed. Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information becomes available. The next update on the incident will be shared no later than 18:25 UTC.

8. investigating May 29, 2026, 06:26 PM 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 through alternate regional PoPs to maintain service continuity while mitigation efforts and root cause analysis are in progress. Next update will be shared no later then 19:26 UTC.

9. investigating May 29, 2026, 07:37 PM 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 update will be shared no later then 20:07 UTC.

10. investigating May 29, 2026, 08:20 PM 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 May 29, 2026, 09:34 PM 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 May 29, 2026, 10:46 PM 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 May 29, 2026, 11:41 PM 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 May 30, 2026, 03:19 PM UTC

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

15. identified Jun 03, 2026, 11:01 AM 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 Jun 04, 2026, 04:31 AM 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 Jun 04, 2026, 05:00 AM 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 Update on this Incident will be provided no later than 06:01 UTC.

18. monitoring Jun 04, 2026, 06:01 AM 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 data center. The next Status Update on this Incident will be provided no later than 06:31 UTC.

19. resolved Jun 04, 2026, 06:30 AM 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 understanding throughout this incident.

Read the full incident report →

Started May 28, 2026, 07:08 PM UTC· resolved May 29, 2026, 11:05 AM UTC

1. identified May 28, 2026, 07:08 PM 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 May 28, 2026, 07:24 PM 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 May 28, 2026, 07:54 PM 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 update will be provided no later than 20:24 UTC.

4. identified May 28, 2026, 08:44 PM 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 additional updates will be provided as changes occur or once the PoP is restored to normal operation.

5. identified May 28, 2026, 09:55 PM 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 normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

6. monitoring May 29, 2026, 10:18 AM 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 May 29, 2026, 11:05 AM UTC

   Service in the data center has been restored to normal.

Read the full incident report →

Started May 28, 2026, 06:09 PM UTC· resolved May 29, 2026, 12:01 PM UTC

1. identified May 28, 2026, 06:09 PM 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 May 28, 2026, 06:23 PM 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 May 28, 2026, 06:57 PM 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 will be provided no later than 19:27 UTC.

4. identified May 28, 2026, 07:30 PM 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 May 28, 2026, 08:17 PM 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 additional updates will be provided as changes occur or once the PoP is restored to normal operation.

6. identified May 28, 2026, 09:54 PM 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 normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

7. monitoring May 29, 2026, 07:25 AM 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 communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

8. investigating May 29, 2026, 08:41 AM 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 May 29, 2026, 09:12 AM 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 May 29, 2026, 09:48 AM 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 May 29, 2026, 10:16 AM UTC

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

12. monitoring May 29, 2026, 10:57 AM 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 May 29, 2026, 12:01 PM UTC

    Service in the data center has been restored to normal.

Read the full incident report →

Started May 27, 2026, 07:22 PM UTC· resolved May 27, 2026, 10:52 PM UTC

1. investigating May 27, 2026, 07:22 PM 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. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

2. investigating May 27, 2026, 08:04 PM 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 May 27, 2026, 08:47 PM 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 May 27, 2026, 10:23 PM 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 May 27, 2026, 10:52 PM 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.

Read the full incident report →

Started May 22, 2026, 10:56 PM UTC· resolved May 22, 2026, 11:59 PM UTC

1. investigating May 22, 2026, 10:56 PM 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 of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. investigating May 22, 2026, 11:39 PM 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 May 22, 2026, 11:53 PM 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 May 22, 2026, 11:59 PM UTC

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

Read the full incident report →

Started May 19, 2026, 09:06 PM UTC· resolved May 22, 2026, 09:20 PM UTC

1. investigating May 19, 2026, 09:06 PM 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 proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. investigating May 19, 2026, 09:44 PM 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 22:14 UTC.

3. investigating May 19, 2026, 10:18 PM 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 May 19, 2026, 10:46 PM 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 May 19, 2026, 11:27 PM 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 May 19, 2026, 11:58 PM 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 next update will be communicated at 00:27 UTC.

7. identified May 20, 2026, 12:36 AM 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. The next update will be communicated at 01:04 UTC.

8. monitoring May 20, 2026, 01:12 AM 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 May 20, 2026, 03:12 AM 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 at 05:12 UTC.

10. monitoring May 20, 2026, 05:12 AM 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 May 20, 2026, 07:14 AM 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 be provided no later than 08:12 UTC.

12. monitoring May 20, 2026, 08:13 AM 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 than expected to propagate and become active. Existing configurations and protections remain in place. Additional remediation actions have been identified to support a stable return to normal operations. The environment remains under active monitoring, and the next update will be provided no later than 09:12 UTC.

13. monitoring May 20, 2026, 09:12 AM 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 new websites, as this process depends on the same configuration publishing flow. Existing configurations and active protections remain in place. Our technical teams remain actively engaged and are continuing to work toward full restoration. The next Status Update on this issue will be provided no later than 10:12 UTC.

14. monitoring May 20, 2026, 10:10 AM 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 Status Update on this issue will be provided no later than 11:10 UTC.

15. monitoring May 20, 2026, 11:10 AM 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 status update will be provided no later than 12:10 UTC.

16. monitoring May 20, 2026, 12:11 PM 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 and duration of the disruption. The backlog is currently being processed, and recovery efforts continue to make progress. Existing configurations and active protections remain in place and continue to operate as expected. The next status update will be provided no later than 13:11 UTC.

17. monitoring May 20, 2026, 12:56 PM 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 May 20, 2026, 02:10 PM 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 no later than 03:10 UTC.

19. investigating May 20, 2026, 03:03 PM 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 publishing new or updated configurations, where changes may appear successfully published but are not fully propagated across the environment. Our engineering teams remain actively engaged and are continuing investigation and remediation efforts to restore normal functionality as quickly as possible. The next status update will be provided no later than 16:03 UTC.

20. investigating May 20, 2026, 04:02 PM 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 will be provided no later than 17:02 UTC.

21. investigating May 20, 2026, 05:00 PM 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 normal service functionality as quickly as possible. Existing configurations and active protections remain in place. The next status update will be provided no later than 18:00 UTC.

22. investigating May 20, 2026, 06:25 PM 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 restore full service functionality as soon as possible. Existing configurations and currently active protections remain unaffected and operational. The next status update will be provided no later than 19:25 UTC.

23. investigating May 20, 2026, 07:30 PM 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 provided no later than 20:30 UTC.

24. investigating May 20, 2026, 08:37 PM 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 than 21:37 UTC.

25. investigating May 20, 2026, 09:49 PM 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 May 20, 2026, 10:32 PM 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 configuration changes are being published successfully. The next update will be communicated at 23:32 UTC.

27. identified May 21, 2026, 12:00 AM 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 on this issue will be provided no later than 01:00 UTC.

28. identified May 21, 2026, 01:56 AM 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 May 21, 2026, 08:30 AM 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 periodic publishing process is continuing to work through the remaining backlog of previously queued configuration changes. While this recovery work continues, some customers may still observe delays related to earlier changes, and some website onboarding flows may remain affected until the backlog is fully cleared. Existing configurations and active protections remain in place and continue to operate as expected. Customers with concerns regarding specific configuration changes are welcome to contact Imperva Support through the Customer Support Portal. We will continue working through the backlog and will provide further updates as progress continues. We will provide a further update on backlog progress no later than 16:00UTC.

30. identified May 21, 2026, 01:52 PM 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 yet be reflected in the cWAF traffic handling. These pending changes are being published in batches and this is expected to complete within 24-36hrs. Customers with concerns regarding specific configuration changes are welcome to contact Imperva Support through the Customer Support Portal. We will continue working through the backlog and will provide further updates as progress continues. We will provide a further update on backlog progress no later than 08:00UTC on Friday 22nd May 2026.

31. identified May 21, 2026, 04:23 PM 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 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes continue to be processed in batches by the Platform team. Customers with concerns regarding specific configuration changes are welcome to contact Imperva Support through the Customer Support Portal. Our teams remain actively engaged in backlog processing and environment monitoring. We will provide a further update on backlog progress no later than 08:00UTC on Friday 22nd May 2026.

32. identified May 21, 2026, 04:55 PM 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 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes continue to be processed in batches by the Platform team. We will provide a further update on backlog progress no later than 08:00UTC on Friday 22nd May 2026.

33. identified May 21, 2026, 06:45 PM 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 the last 36 hours including Custom TLS Certificate uploads, Rule or Policy creations, updates or deletions, and Site configuration modifications may not yet be fully reflected in CWAF traffic handling. These remaining pending changes are still being processed in batches by the Technical team. We will provide a further update on backlog progress no later than 08:00UTC on Friday 22nd May 2026.

34. identified May 21, 2026, 08:53 PM 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 the next update regarding backlog progress no later than 08:00 UTC on Friday, 22 May 2026.

35. identified May 22, 2026, 07:37 AM 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 indicated timeframe. Imperva is fully aware of the impact this incident has had on our customers, and apologises unreservedly for it. A further update on the progress of applying pending config changes will be provided no later than 15:00UTC.

36. identified May 22, 2026, 02:42 PM 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 May 22, 2026, 03:31 PM 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 closely monitor the platform to ensure ongoing stability and promptly address any unexpected issues. The next Status Update on this issue will be provided no later than 21:30 UTC.

38. resolved May 22, 2026, 09:20 PM 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.

Read the full incident report →

Started May 16, 2026, 08:50 PM UTC· resolved May 17, 2026, 06:36 AM UTC

1. investigating May 16, 2026, 08:50 PM 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 investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. investigating May 16, 2026, 09:23 PM 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 May 16, 2026, 10:01 PM 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 May 16, 2026, 10:47 PM 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 May 16, 2026, 11:43 PM 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 May 17, 2026, 12:12 AM 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 May 17, 2026, 12:45 AM 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 May 17, 2026, 01:21 AM 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 May 17, 2026, 01:51 AM 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 May 17, 2026, 02:23 AM 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 May 17, 2026, 02:53 AM 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 May 17, 2026, 03:24 AM 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 May 17, 2026, 03:54 AM 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 shared no later than 04:23 UTC.

14. identified May 17, 2026, 04:46 AM 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 May 17, 2026, 05:10 AM 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 May 17, 2026, 05:35 AM 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 May 17, 2026, 05:42 AM 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 May 17, 2026, 06:36 AM UTC

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

Read the full incident report →

Started May 15, 2026, 07:22 PM UTC· resolved May 15, 2026, 11:29 PM UTC

1. investigating May 15, 2026, 07:22 PM 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 about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

2. investigating May 15, 2026, 07:51 PM 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 May 15, 2026, 08:21 PM 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 May 15, 2026, 09:00 PM 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 May 15, 2026, 09:33 PM 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 no later than 22:00 UTC.

6. investigating May 15, 2026, 10:13 PM 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 will be shared no later than 22:42 UTC.

7. identified May 15, 2026, 10:14 PM 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 will be shared no later than 22:44 UTC.

8. identified May 15, 2026, 10:47 PM 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 to the publisher service are still being observed, and active efforts are ongoing to fully stabilize the environment. The next update for this incident will be shared no later than 23:17 UTC.

9. monitoring May 15, 2026, 11:08 PM 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 May 15, 2026, 11:29 PM UTC

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

Read the full incident report →

Started May 15, 2026, 07:14 PM UTC· resolved May 15, 2026, 07:14 PM UTC

1. resolved May 15, 2026, 07:16 PM UTC

   We have discovered a potential service degradation, affecting customers ability to use the Imperva Management Portal. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 19:44UTC. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →