Imperva outage of 29 Oct 2026: what happened and how long it lasted
Imperva’s outage of 29 Oct 2026 was open on Imperva’s status page for 9 h 5 min, from 00:09 to 09:14 UTC, and affected Queretaro, Mexico (QRO).
Last changed . Last checked . Source: stspg.io/gj85p9x27wg7.
Imperva's updatesOldest first, in the vendor's own words. Times are 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. 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.
Traffic remains rerouted through alternate PoPs in the region. Customers may experience increased latency while the reroute is in place.
Third-party upstream providers in the region are experiencing issues, and our teams remain in close contact with them for updates. Traffic will continue to be rerouted through alternate PoPs in the region while the providers work to resolve the issue.
Our upstream providers have confirmed that corrective measures have been implemented and are reporting improvements in network performance. We are also observing improvements, and our teams will continue to closely monitor the situation to ensure sustained stability before reactivating the Queretaro, Mexico (QRO) PoP and restoring normal traffic routing.
Our teams continue to monitor network stability and coordinate with upstream providers to confirm full service restoration before reactivating the Queretaro, Mexico (QRO) PoP.
Following confirmation of resolution from our upstream providers and verification of network stability, the Queretaro, Mexico (QRO) PoP has been reactivated. Our team will continue to monitor performance to ensure ongoing stability.
Monitoring has confirmed that network performance is stable and services are operating normally.
CauseIn Imperva's words only
Imperva's updates on this incident do not name a cause.
Imperva has not published a post-mortem on its incident page.