Incapsula outage history

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

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

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

We have identified an issue in the Rio de Janeiro, Brazi data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Further updates will be shared as more information becomes available.

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

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

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

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

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

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

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

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

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

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

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

We have identified an issue in the Istanbul, Turkey (SAW ) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Next update on the incident will be shared no later than 19:41 UTC

We have identified an issue in the Istanbul, Turkey (SAW ) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.

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

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.

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

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

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.