Imperva incident

[INC-938] Potential issue on GVA PoP

Minor Resolved View vendor source →

Imperva experienced a minor incident on November 24, 2025 affecting Zurich, Switzerland (GVA), lasting 2h 28m. The incident has been resolved; the full update timeline is below.

Started
Nov 24, 2025, 02:22 PM UTC
Resolved
Nov 24, 2025, 04:50 PM UTC
Duration
2h 28m
Detected by Pingoru
Nov 24, 2025, 02:22 PM UTC

Affected components

Zurich, Switzerland (GVA)

Update timeline

  1. investigating Nov 24, 2025, 02:22 PM UTC

    We have bypassed GVA PoP due to an issue detected with CWAF. Technical teams are investigating. 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.

  2. identified Nov 24, 2025, 03:11 PM 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.

  3. monitoring Nov 24, 2025, 03:16 PM 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.

  4. identified Nov 24, 2025, 03:31 PM 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.

  5. monitoring Nov 24, 2025, 04:21 PM UTC

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

  6. resolved Nov 24, 2025, 04:50 PM UTC

    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.