Imperva incident

[INC-1166] Service Degradation Affecting Newly Onboarded Sites

Minor Resolved View vendor source →

Imperva experienced a minor incident on October 20, 2026 affecting Cloud Security Management Platform, lasting 7h 38m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2026, 08:43 AM UTC
Resolved
Oct 20, 2026, 04:21 PM UTC
Duration
7h 38m
Detected by Pingoru
Oct 20, 2026, 08:43 AM UTC

Affected components

Cloud Security Management Platform

Update timeline

  1. investigating Oct 20, 2026, 08:43 AM UTC

    We are investigating a service degradation affecting resolution for some newly onboarded sites. Our teams are working to determine the cause and will provide updates as more information becomes available. The next update will be provided by 09:15 UTC.

  2. identified Oct 20, 2026, 09:04 AM UTC

    Our internal teams have identified the service degradation that is affecting the newly onboarded sites. We are currently working to remediate the incident and further updates will be provided as information becomes available. The next update will be before 09:45 UTC

  3. identified Oct 20, 2026, 09:43 AM UTC

    Efforts into mitigating the issue are still ongoing. Further updates will be provided as information becomes available. The next update will be before 11:15 UTC

  4. identified Oct 20, 2026, 10:26 AM UTC

    Efforts to mitigate the issue are still ongoing. Our teams continue working to restore normal service. Further updates will be provided as information becomes available.

  5. identified Oct 20, 2026, 12:54 PM UTC

    Imperva teams continue working to mitigate the issue and restore normal service. We are currently implementing and validating mitigation actions. Further updates will be provided as information becomes available.

  6. identified Oct 20, 2026, 02:28 PM UTC

    Mitigation efforts are ongoing. Our teams have completed additional configuration changes and continue working to restore normal service. Further updates will be provided as information becomes available.

  7. monitoring Oct 20, 2026, 04:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Oct 20, 2026, 04:21 PM UTC

    This incident has been resolved.