[INC-1045] Imperva Management Portal Configuration Changes Issue
Incident Lifecycle
Incident Timeline
Monitoring
Monitoring has confirmed that all services are operating normally, including new provisioning activities and configuration changes across sites and accounts.
Processing of all previously pending configuration items has now been fully completed and verified. We will continue to closely monitor the platform to ensure ongoing stability and promptly address any unexpected issues.
The next Status Update on this issue will be provided no later than 21:30 UTC.
Processing of all previously pending configuration items has now been fully completed and verified. We will continue to closely monitor the platform to ensure ongoing stability and promptly address any unexpected issues.
The next Status Update on this issue will be provided no later than 21:30 UTC.
May 22, 2026 at 3:31 PM UTC
Identified
We expect to complete the processing of all pending config changes within the next hour.
Once this is completed and verified, we'll monitor the platform for some time to make sure there are no other issues.
We will post the next update no later than 1700UTC.
Once this is completed and verified, we'll monitor the platform for some time to make sure there are no other issues.
We will post the next update no later than 1700UTC.
May 22, 2026 at 2:42 PM UTC
Identified
Monitoring has confirmed that all services are operating as normal with any new provisioning or changes to any site or account configuration.
The tasks to work through the previous pending configuration items is still on-going and is expected to complete within the previously indicated timeframe.
Imperva is fully aware of the impact this incident has had on our customers, and apologises unreservedly for it.
A further update on the progress of applying pending config changes will be provide...
The tasks to work through the previous pending configuration items is still on-going and is expected to complete within the previously indicated timeframe.
Imperva is fully aware of the impact this incident has had on our customers, and apologises unreservedly for it.
A further update on the progress of applying pending config changes will be provide...
May 22, 2026 at 7:37 AM UTC
Identified
Our technical teams have confirmed that configuration changes are now propagating normally. Remaining backlog processing activities are still ongoing and are expected to complete within approximately one day.
The environment continues to be closely monitored, and we will provide the next update regarding backlog progress no later than 08:00 UTC on Friday, 22 May 2026.
The environment continues to be closely monitored, and we will provide the next update regarding backlog progress no later than 08:00 UTC on Friday, 22 May 2026.
May 21, 2026 at 8:53 PM UTC
Identified
The Technical team confirmed that the pending queue has been successfully cleared and is currently executing a script to process the events that were skipped yesterday. Current configuration changes are now publishing as expected.
However, some configuration changes made within the last 36 hours including Custom TLS Certificate uploads, Rule or Policy creations, updates or deletions, and Site configuration modifications may not yet be fully reflected in CWAF traffic handling. These remaining...
However, some configuration changes made within the last 36 hours including Custom TLS Certificate uploads, Rule or Policy creations, updates or deletions, and Site configuration modifications may not yet be fully reflected in CWAF traffic handling. These remaining...
May 21, 2026 at 6:45 PM UTC
Identified
Currently, new configuration changes made in the UMC are continuing to be applied successfully. However, we are presently observing an approximate propagation delay of 40 minutes while backlog processing activities continue.
Some configuration changes made during the last 36 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes con...
Some configuration changes made during the last 36 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes con...
May 21, 2026 at 4:55 PM UTC
Identified
Currently, new configuration changes made in the UMC are continuing to be applied successfully. However, we are presently observing an approximate propagation delay of 40 minutes while backlog processing activities continue.
Some configuration changes made during the last 36 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes con...
Some configuration changes made during the last 36 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes con...
May 21, 2026 at 4:23 PM UTC
Identified
Currently, any new configuration changes made in the UMC are being applied as expected without any extra delay.
Some config changes (including Custom TLS Cert Uploads, Rule or Policy creations, deletions or updates, and Site config edits) made during the last 36 hours may not yet be reflected in the cWAF traffic handling. These pending changes are being published in batches and this is expected to complete within 24-36hrs.
Customers with concerns regarding specific configuration changes are...
Some config changes (including Custom TLS Cert Uploads, Rule or Policy creations, deletions or updates, and Site config edits) made during the last 36 hours may not yet be reflected in the cWAF traffic handling. These pending changes are being published in batches and this is expected to complete within 24-36hrs.
Customers with concerns regarding specific configuration changes are...
May 21, 2026 at 1:52 PM UTC
Identified
We apologize for the extended time since the last update. Our teams remain actively engaged and continue remediation efforts for the Management Console configuration publishing service.
At this stage, newly created or updated configurations are being published without delay. The periodic publishing process is continuing to work through the remaining backlog of previously queued configuration changes. While this recovery work continues, some customers may still observe delays related to earli...
At this stage, newly created or updated configurations are being published without delay. The periodic publishing process is continuing to work through the remaining backlog of previously queued configuration changes. While this recovery work continues, some customers may still observe delays related to earli...
May 21, 2026 at 8:30 AM UTC
Identified
Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. Backlog items are still being processed, while new configuration changes are currently published successfully.
May 21, 2026 at 1:56 AM UTC
Identified
The Technical teams remain engaged in ongoing validation and analysis efforts to evaluate the impact on overall service performance. While certain backlog items are still awaiting processing, new configuration changes are currently publishing successfully.
The next Status Update on this issue will be provided no later than 01:00 UTC.
The next Status Update on this issue will be provided no later than 01:00 UTC.
May 21, 2026 at 12:00 AM UTC
Identified
The investigation has identified a possible contributing factor related to the issue, and the engineering teams are continuing validation and analysis to assess its impact on overall service performance. Meanwhile, although some backlog items are still pending, current configuration changes are being published successfully.
The next update will be communicated at 23:32 UTC.
The next update will be communicated at 23:32 UTC.
May 20, 2026 at 10:32 PM UTC
Investigating
Technical team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance.
The next status update will be provided no later than 22:49 UTC.
The next status update will be provided no later than 22:49 UTC.
May 20, 2026 at 9:49 PM UTC
Investigating
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.
The next status update will be provided no later than 21:37 UTC.
May 20, 2026 at 8:37 PM UTC
Investigating
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.
The next status update will be provided no later than 20:30 UTC.
May 20, 2026 at 7:30 PM UTC
Investigating
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.
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.
May 20, 2026 at 6:25 PM UTC
Investigating
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.
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.
May 20, 2026 at 5:00 PM UTC
Investigating
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.
The next status update will be provided no later than 17:02 UTC.
May 20, 2026 at 4:02 PM UTC
Investigating
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...
Our engineering teams remain actively engaged and are continuing investigation and...
May 20, 2026 at 3:03 PM UTC
Monitoring
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 15:10 UTC.
The next status update will be provided no later than 15:10 UTC.
May 20, 2026 at 2:10 PM UTC
Monitoring
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.
We will continue to closely monitor the service until 13:56 UTC.
May 20, 2026 at 12:56 PM UTC
Monitoring
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 expec...
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 expec...
May 20, 2026 at 12:11 PM UTC
Monitoring
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.
Existing configurations and active protections continue to remain in place.
The next status update will be provided no later than 12:10 UTC.
May 20, 2026 at 11:10 AM UTC
Monitoring
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.
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.
May 20, 2026 at 10:10 AM UTC
Monitoring
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...
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...
May 20, 2026 at 9:12 AM UTC
Monitoring
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 environmen...
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 environmen...
May 20, 2026 at 8:13 AM UTC
Monitoring
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.
The next Status Update on this issue will be provided no later than 08:12 UTC.
May 20, 2026 at 7:14 AM UTC
Monitoring
Technical teams are still actively working to restore the service following the remediation actions. The next update will be communicated at 07:12 UTC.
May 20, 2026 at 5:12 AM UTC
Monitoring
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.
May 20, 2026 at 3:12 AM UTC
Monitoring
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.
May 20, 2026 at 1:12 AM UTC
Identified
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.
The next update will be communicated at 01:04 UTC.
May 20, 2026 at 12:36 AM UTC
Identified
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.
The next update will be communicated at 00:27 UTC.
May 19, 2026 at 11:58 PM UTC
Identified
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.
The next update will be communicated at 23:56 UTC.
May 19, 2026 at 11:27 PM UTC
Identified
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.
The next update will be communicated at 23:16 UTC.
May 19, 2026 at 10:46 PM UTC
Investigating
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.
The next status update will be shared no later than 22:47 UTC.
May 19, 2026 at 10:18 PM UTC
Investigating
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.
The next status update will be shared no later than 22:14 UTC.
May 19, 2026 at 9:44 PM UTC
Investigating
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.
...
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.
...
May 19, 2026 at 9:06 PM UTC
Was your business affected by this Imperva outage?
Set up instant alerts for Imperva, be the first to know about outages via email, Slack, Teams, or Discord.