[INC-1182] Delay of Cloud Security Management Configuration Changes

What to do

• Check whether you use Imperva Cloud Security Management Configuration Changes in apac. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1d 2h it lasted.

  Anything that failed between 2026-11-04 15:00 UTC and 2026-11-05 17:57 UTC may need a replay.

• Subscribe to Imperva's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=imperva works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Imperva 7

1. investigatingNov 4, 2026, 3:00 PM UTC

   We are investigating an incident where some customers may experience delays when applying certain configuration changes. Not all configuration changes or customers are affected. Our teams are actively investigating and we will provide further updates as more information becomes available. The next update will not be after 15:30 UTC

   provider

2. investigatingNov 4, 2026, 3:07 PM UTC

   We are investigating an incident where some customers may experience delays when applying certain configuration changes. Not all configuration changes or customers are affected. Our teams are actively investigating and we will provide further updates as more information becomes available. The next update will not be after 15:30 UTC

   provider

3. identifiedNov 4, 2026, 3:23 PM UTC

   Some customers may continue to experience delays when applying certain configuration changes. The issue remains limited in scope and does not affect all customers or configuration changes. Our teams are actively executing a phased mitigation plan to restore normal processing for the affected services. The phased plan will be applied during low traffic times in our PoPs to minimise any further disruption. We continue to monitor the service closely and will provide further updates as progress is made. The next update will be before 00:00 UTC.

   provider

4. identifiedNov 4, 2026, 11:52 PM UTC

   Our phased mitigation efforts have significantly reduced the scope of the issue. A small portion of service capacity, approximately 5%, may continue to experience the issue and will be addressed during the next phase of remediation. We continue to monitor the service closely and will provide a further update before 08:00 UTC.

   provider

5. identifiedNov 5, 2026, 10:30 AM UTC

   We have made significant progress with our mitigation efforts, and service has improved across most affected locations. Some customers may continue to experience delays with certain configuration changes being applied in the Jakarta (JKT), Kuala Lumpur (KUL), and Manila (MNL) Points of Presence (PoPs). Additional mitigation activities for the remaining affected APAC locations are planned during regional off-hours to minimize potential customer disruption. We continue to monitor the service closely and will provide further updates as progress is made.

   provider

6. monitoringNov 5, 2026, 4:23 PM UTC

   The incident causing delays with certain configuration changes has been mitigated. Configuration processing has returned to expected levels, and our teams are closely monitoring the service to ensure continued stability.

   provider

7. resolvedNov 5, 2026, 5:57 PM UTC

   The incident causing delays with certain configuration changes has been resolved. Configuration processing remains at expected levels, and the service has remained stable following mitigation. We will continue to monitor service health as part of our normal operations.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.