[INC-1045] Imperva Management Portal Configuration Changes Issue

Update timeline

1. investigating May 19, 2026, 09:06 PM UTC

   We have discovered a potential service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. The next Status Update on this Incident will be provided no later than 21:36 UTC. 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. investigating May 19, 2026, 09:44 PM UTC

   The investigation into the service degradation impacting the Imperva Management Portal is ongoing. Recent configuration changes are experiencing propagation delays, and technical teams are actively investigating the issue. The next status update will be shared no later than 22:14 UTC.

3. investigating May 19, 2026, 10:18 PM UTC

   The ongoing service degradation affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. remains under active investigation by the Engineering team. The next status update will be shared no later than 22:47 UTC.

4. identified May 19, 2026, 10:46 PM UTC

   Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance. The next update will be communicated at 23:16 UTC.

5. identified May 19, 2026, 11:27 PM UTC

   Technical team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance. The next update will be communicated at 23:56 UTC.

6. identified May 19, 2026, 11:58 PM UTC

   Technical teams have identified the root cause and applied corrective actions. System performance is steadily improving; however, some delays may still be experienced while publishing activity gradually returns to normal. Full synchronization may take a few additional hours. The next update will be communicated at 00:27 UTC.

7. identified May 20, 2026, 12:36 AM UTC

   System performance is continuing to recover following the remediation actions implemented by the technical teams. Overall service stability is improving; however, still we're observing delay in publishing. The environment remains under active monitoring by the technical teams. The next update will be communicated at 01:04 UTC.

8. monitoring May 20, 2026, 01:12 AM UTC

   System performance is continuing to recover and is expected to recover in the next few hours. The environment remains under active monitoring by the technical teams. The next update will be communicated at 03:12 UTC.

9. monitoring May 20, 2026, 03:12 AM UTC

   Technical teams are actively working to restore the service following the remediation actions. Some delays may still be experienced while publishing activity gradually returns to normal. Full synchronization may take a few additional hours. The next update will be communicated at 05:12 UTC.

10. monitoring May 20, 2026, 05:12 AM UTC

    Technical teams are still actively working to restore the service following the remediation actions. The next update will be communicated at 07:12 UTC.

11. monitoring May 20, 2026, 07:14 AM UTC

    While base remediation is still on-going, some additional actions have been identified as required in order to restore full service. These actions are required to ensure longer term stability and a seamless return to regular operations. The next Status Update on this issue will be provided no later than 08:12 UTC.

12. monitoring May 20, 2026, 08:13 AM UTC

    Technical teams continue working to fully restore the Management Console configuration publishing service. Customers may experience delays when publishing new or updated configurations from the Management Console. During this time, recent configuration changes may take longer than expected to propagate and become active. Existing configurations and protections remain in place. Additional remediation actions have been identified to support a stable return to normal operations. The environment remains under active monitoring, and the next update will be provided no later than 09:12 UTC.

13. monitoring May 20, 2026, 09:12 AM UTC

    We are continuing remediation efforts for the Management Console configuration publishing service. Customers may still experience delays when publishing new or updated configurations from the Management Console. In addition, some customers may experience issues when onboarding new websites, as this process depends on the same configuration publishing flow. Existing configurations and active protections remain in place. Our technical teams remain actively engaged and are continuing to work toward full restoration. The next Status Update on this issue will be provided no later than 10:12 UTC.

14. monitoring May 20, 2026, 10:10 AM UTC

    Remediation activities for the Management Console configuration publishing service are ongoing. Multiple teams remain actively engaged and are working to fully restore service functionality. Existing configurations and active protections continue to remain in place. The next Status Update on this issue will be provided no later than 11:10 UTC.

15. monitoring May 20, 2026, 11:10 AM UTC

    Remediation efforts for the Management Console configuration publishing service are still underway. Multiple teams remain actively engaged and are working to fully restore service functionality. Existing configurations and active protections continue to remain in place. The next status update will be provided no later than 12:10 UTC.

16. monitoring May 20, 2026, 12:11 PM UTC

    Remediation activities for the Management Console configuration publishing service are ongoing, with multiple teams actively engaged in restoring full service functionality. Imperva is aware of the impact this incident has had on our customers and apologizes for both the scope and duration of the disruption. The backlog is currently being processed, and recovery efforts continue to make progress. Existing configurations and active protections remain in place and continue to operate as expected. The next status update will be provided no later than 13:11 UTC.

17. monitoring May 20, 2026, 12:56 PM UTC

    Processing of the backlog is complete. We are monitoring the situation carefully, but all changes saved in the UMC are now being published as expected and all pending configuration changes have been applied. We will continue to closely monitor the service until 13:56 UTC.

18. monitoring May 20, 2026, 02:10 PM UTC

    Our monitoring has identified that some configuration changes have not propagated as expected. Engineering teams are actively investigating the issue and continuing remediation efforts to restore normal configuration publishing behavior. The next status update will be provided no later than 03:10 UTC.

19. investigating May 20, 2026, 03:03 PM UTC

    Following the earlier remediation activities related to the Management Console configuration publishing service, we are currently investigating an additional issue affecting the propagation of configuration changes. Customers may experience delays or inconsistencies when publishing new or updated configurations, where changes may appear successfully published but are not fully propagated across the environment. Our engineering teams remain actively engaged and are continuing investigation and remediation efforts to restore normal functionality as quickly as possible. The next status update will be provided no later than 16:03 UTC.

20. investigating May 20, 2026, 04:02 PM UTC

    Remediation efforts are ongoing for the issue affecting Management Console configuration propagation. Our engineering teams have identified a potential cause impacting the functionality and are actively working on remediation and validation activities. The next status update will be provided no later than 17:02 UTC.

21. investigating May 20, 2026, 05:00 PM UTC

    We continue to investigate issues affecting the propagation of configuration changes. Customers may experience delays or inconsistencies when publishing new or updated configurations. Our engineering teams remain actively engaged and are continuing remediation efforts to restore normal service functionality as quickly as possible. Existing configurations and active protections remain in place. The next status update will be provided no later than 18:00 UTC.

22. investigating May 20, 2026, 06:25 PM UTC

    Our teams are actively investigating an issue impacting the propagation of configuration updates. Customers may encounter delays or inconsistent behavior while publishing new or modified configurations. Engineering teams continue to work on mitigation and recovery efforts to restore full service functionality as soon as possible. Existing configurations and currently active protections remain unaffected and operational. The next status update will be provided no later than 19:25 UTC.

23. investigating May 20, 2026, 07:30 PM UTC

    Our engineering teams are actively working to mitigate the issue and restore full service functionality as quickly as possible. At this time, existing configurations and active protections continue to operate normally and remain fully in effect. The next status update will be provided no later than 20:30 UTC.

24. investigating May 20, 2026, 08:37 PM UTC

    Engineering teams are continuing remediation efforts to restore full platform functionality at the earliest opportunity. Meanwhile, all existing configurations and active security protections remain stable and fully operational. The next status update will be provided no later than 21:37 UTC.