Imperva incident

[INC-966] Imperva Management Portal Network Protect Dashboards Issue

Minor Resolved View vendor source →

Imperva experienced a minor incident on February 1, 2026, lasting 2h 47m. The incident has been resolved; the full update timeline is below.

Started
Feb 01, 2026, 12:12 PM UTC
Resolved
Feb 01, 2026, 03:00 PM UTC
Duration
2h 47m
Detected by Pingoru
Feb 01, 2026, 12:12 PM UTC

Update timeline

  1. identified Feb 01, 2026, 12:12 PM UTC

    We have identified a service degradation that is causing the dashboard on the network not to display historical data for Network Protect dashboards. Despite this issue, customers can continue to use the Imperva Management Portal for managing their accounts without interruption. Technical teams are working on a mitigation. 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 Feb 01, 2026, 12:46 PM UTC

    Technical teams are continuing to working on a fix for this issue.

  3. identified Feb 01, 2026, 01:20 PM UTC

    Our engineers are actively working on the fix to resolve this issue. We will provide another update in 2 hours or as soon as more information becomes available.

  4. monitoring Feb 01, 2026, 02:28 PM UTC

    Technical teams have performed remedial actions and the dashboard on the network display historical data for Network Protect dashboards. Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. 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.

  5. monitoring Feb 01, 2026, 02:54 PM UTC

    This issue has been resolved.

  6. resolved Feb 01, 2026, 03:00 PM UTC

    This issue has been resolved.