Is Incapsula down?

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