Imperva Status

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

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

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

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

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

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

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

Identified: 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

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

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

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

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

Investigating: 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

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

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

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.

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

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

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

Monitoring: 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

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

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

Investigating: 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