Major incident

Imperva: [INC-1105] YUL PoP Service Degradation

Affected: Montreal, Canada (YUL)

Current status of Imperva: Under maintenance — live Imperva status

Timeline

1. Aug 13, 2026, 08:22 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
2. Aug 13, 2026, 08:34 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.
3. Aug 13, 2026, 08:48 UTC
   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.
4. Aug 13, 2026, 09:29 UTC
   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
5. Aug 14, 2026, 08:12 UTC
   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.
6. Aug 17, 2026, 05:44 UTC
   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.
7. Aug 17, 2026, 10:49 UTC
   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.
8. Aug 17, 2026, 13:17 UTC
   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.

Updates as published by Imperva (original).