Incapsula Outage History

Started May 15, 2026, 08:17 AM UTC· resolved May 15, 2026, 11:42 AM UTC

1. investigating May 15, 2026, 08:17 AM UTC

   We have discovered a potential service degradation, affecting Imperva Management Portal. The Management Portal website is slow to respond to user actions and in some cases user login attempts may also fail. All customer websites remain fully protected at this time. Technical teams are investigating. 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. investigating May 15, 2026, 08:53 AM UTC

   The impact has been identified as isolated to the India region. Technical teams are actively investigating the issue and working towards mitigation. The next update on the incident will be shared no later that 09:22 UTC

3. investigating May 15, 2026, 09:21 AM UTC

   Technical teams are continuing to actively troubleshoot the issue and are working to restore normal service levels. The next update on the incident will be shared no later that 09:50 UTC

4. monitoring May 15, 2026, 09:52 AM UTC

   The issue has been identified as ISP-related. Technical teams have taken mitigation actions, and we are observing improvements in service performance. Monitoring will continue to ensure stability.

5. resolved May 15, 2026, 11:42 AM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva Management Portal.

Read the full incident report →

Started May 14, 2026, 07:49 PM UTC· resolved May 15, 2026, 12:32 AM UTC

1. investigating May 14, 2026, 07:49 PM UTC

   Technical teams are investigating a potential issue in the New Delhi (NDL), Mumbai (NAG) Data Center. The next Status Update on this Incident will be provided no later than 20:19 UTC. Further updates to follow.

2. identified May 14, 2026, 08:21 PM UTC

   We have identified the source of the issue in the data center. Technical teams are working on a fix. The next Status Update on this Incident will be provided no later than 20:51 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.

3. identified May 14, 2026, 08:55 PM UTC

   Technical teams are currently investigating the issue and will provide updates as more information becomes available. The next Status Update on this Incident will be provided no later than 21:25 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.

4. identified May 14, 2026, 09:25 PM UTC

   Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 21:55 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.

5. identified May 14, 2026, 09:55 PM UTC

   Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 22:55 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.

6. identified May 14, 2026, 10:55 PM UTC

   Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 23:55 UTC. 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.

7. monitoring May 14, 2026, 11:55 PM UTC

   A fix has been implemented and we are continuing to monitor in order to ensure that service has returned to normal. 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.

8. resolved May 15, 2026, 12:32 AM UTC

   Service in the data center has been restored to normal. 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.

Read the full incident report →

Started May 14, 2026, 05:26 PM UTC· resolved May 14, 2026, 06:28 PM UTC

1. investigating May 14, 2026, 05:26 PM UTC

   We have discovered a potential service degradation, affecting customers ability to use the Imperva Management Portal. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 17:56 UTC. 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. monitoring May 14, 2026, 05:58 PM UTC

   Technical teams have performed remedial actions and the 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.

3. resolved May 14, 2026, 06:28 PM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva Management Portal. 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.

Read the full incident report →

Started May 13, 2026, 01:57 AM UTC· resolved May 13, 2026, 01:57 AM UTC

1. resolved May 13, 2026, 01:57 AM UTC

   We have discovered a service degradation that affected the EZE PoP which may have resulted in customers experiencing impact for Imperva Cloud WAF and DDoS for Networks traffic routed through the EZE PoP. Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts. Services has been restored for EZE PoP.

Read the full incident report →

Started May 12, 2026, 10:56 AM UTC· resolved May 12, 2026, 12:15 PM UTC

1. investigating May 12, 2026, 10:56 AM UTC

   We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. 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. monitoring May 12, 2026, 11:23 AM UTC

   Technical teams have performed remedial actions and the 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.

3. resolved May 12, 2026, 12:15 PM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva Management Portal. 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.

Read the full incident report →

Started May 12, 2026, 07:49 AM UTC· resolved May 12, 2026, 07:49 AM UTC

1. resolved May 12, 2026, 07:49 AM UTC

   We have identified ISP-related connectivity issues in the Vancouver region which affected traffic at 07:03 UTC - 07:21 UTC that may have impacted Imperva Cloud WAF and DDoS for Networks traffic routed through the VAN PoP. Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts.

Read the full incident report →

Started May 11, 2026, 06:32 AM UTC· resolved May 11, 2026, 08:33 AM UTC

1. investigating May 11, 2026, 06:32 AM UTC

   We have discovered a potential service degradation, affecting the Imperva Management Portal. One or more Cloud WAF Dashboards are not responding or returning errors. Customer domains are still fully protected at this time. Technical teams are investigating. 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. investigating May 11, 2026, 06:56 AM UTC

   We have narrowed the issue down to the “WAF Sessions by Country” component in the Security dashboard, which is not functioning as expected. The technical teams are actively working on a fix. The next Status Update on this Incident will be provided no later than 07:26 UTC.

3. investigating May 11, 2026, 07:22 AM UTC

   Our technical teams are actively working to resolve the issue and will share updates as progress is made. The next Status Update on this Incident will be provided no later than 07:52 UTC.

4. monitoring May 11, 2026, 07:26 AM UTC

   A fix has been implemented for the issue impacting the Cloud WAF Dashboards component. The issue has been mitigated, and the team is actively monitoring to ensure continued stability.

5. resolved May 11, 2026, 08:33 AM UTC

   The issue affecting the Cloud WAF Dashboards component has been resolved. All systems are operating normally.

Read the full incident report →

Started May 11, 2026, 12:47 AM UTC· resolved May 11, 2026, 02:22 PM UTC

1. investigating May 11, 2026, 12:47 AM UTC

   Technical teams are investigating a potential issue in the Ashburn, VA (IAD) data center. 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. investigating May 11, 2026, 01:25 AM UTC

   We are continuing to investigate. The next Status Update on this Incident will be provided no later than 01:47 UTC.

3. investigating May 11, 2026, 01:43 AM UTC

   Technical teams are continuing to investigate. The next Status Update on this Incident will be provided no later than 02:17 UTC.

4. investigating May 11, 2026, 02:15 AM UTC

   Technical teams are still working on restoring connectivity within the PoP. The next Status Update on this Incident will be provided no later than 03:17 UTC.

5. identified May 11, 2026, 02:48 AM UTC

   We have identified an issue in the data center and the PoP has been deactivated for now. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.

6. identified May 11, 2026, 03:47 AM UTC

   The PoP remains deactivated while the team is working in restoring connectivity within the PoP. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.

7. monitoring May 11, 2026, 04:43 AM UTC

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

8. monitoring May 11, 2026, 05:46 AM UTC

   We are continuing to monitor for any further issues.

9. monitoring May 11, 2026, 06:47 AM UTC

   Technical teams have performed remedial actions and still monitoring the results.

10. monitoring May 11, 2026, 07:51 AM UTC

    The PoP is still deactivated and traffic is being rerouted through an alternate data center in the region. We are continuing to monitor the PoP before bringing it up again.

11. monitoring May 11, 2026, 10:44 AM UTC

    The PoP remains deactivated , with traffic continuing to be routed through alternate data centers in the region to ensure service continuity. We are closely monitoring the environment. Further updates to follow.

12. monitoring May 11, 2026, 12:03 PM UTC

    The issue has been mitigated. We are currently in the process of activating the Ashburn, VA (IAD) PoP. Pre-checks are being completed as part of the restoration, and traffic will be gradually restored. The next update will be provided once the PoP is ready to be brought online.

13. monitoring May 11, 2026, 12:29 PM UTC

    Pre-checks have been completed, and the PoP is expected to be brought back online within the next 15 minutes. The next update will be shared once the PoP is fully online.

14. monitoring May 11, 2026, 12:39 PM UTC

    The Ashburn, VA (IAD) PoP is now online. Teams will continue to monitor closely to ensure service stability.

15. resolved May 11, 2026, 02:22 PM UTC

    Monitoring has confirmed that the issue has been resolved, and all services are operating normally.

Read the full incident report →

Started May 10, 2026, 01:35 PM UTC· resolved May 10, 2026, 04:21 PM UTC

1. investigating May 10, 2026, 01:35 PM UTC

   A third-party internet service provider is currently experiencing an issue resulting in degradation of CWAF and Network DDoS services. Customers may experience elevated latency or, in some cases, temporary loss of availability for CWAF-protected sites. This impact includes CloudWAF customers using Origin POP and Network DDoS customers utilizing Mesh. Customer websites remain fully protected during this time. The next Status Update on this Incident will be provided no later than 14:05 UTC.

2. monitoring May 10, 2026, 02:54 PM UTC

   Technical teams have performed remedial actions and services are returning to normal operations. 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.

3. monitoring May 10, 2026, 03:02 PM UTC

   We are continuing to monitor for any further issues.

4. resolved May 10, 2026, 04:21 PM UTC

   Monitoring has confirmed that services are stable, and the issue has been resolved. 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.

Read the full incident report →

Started May 10, 2026, 12:10 PM UTC· resolved May 10, 2026, 01:28 PM UTC

1. investigating May 10, 2026, 12:10 PM UTC

   We have discovered a potential service degradation, affecting intermittent issues loading various pages on the Management Console. Technical teams are investigating. 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. investigating May 10, 2026, 12:24 PM UTC

   Investigations indicate that the scope of the impact also includes Imperva APIs, in addition to intermittent issues loading various pages on the Management Console. Technical teams continue to investigate. The next Status Update on this Incident will be provided no later than 12:54 UTC.

3. identified May 10, 2026, 12:36 PM UTC

   We have identified the issue causing intermittent issues with loading various pages on the Imperva Management Console, as well as impacting Imperva APIs. The team is actively working on remediation The next Status Update on this Incident will be provided no later than 13:06 UTC.

4. monitoring May 10, 2026, 01:01 PM UTC

   Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Further updates to follow.The next Status Update on this Incident will be provided no later than 14:02 UTC.

5. resolved May 10, 2026, 01:28 PM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva Management Portal. 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.

Read the full incident report →

Started May 08, 2026, 07:37 PM UTC· resolved May 08, 2026, 09:13 PM UTC

1. identified May 08, 2026, 07:37 PM UTC

   We have discovered a potential issue affecting FP on browser classification. Technical teams are investigating. 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 May 08, 2026, 07:42 PM UTC

   The issue has been identified and a fix is being implemented. The next Status Update on this Incident will be provided no later than 20:10 UTC. 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.

3. identified May 08, 2026, 08:16 PM UTC

   The issue has been identified, and remediation efforts are currently underway. The next Status Update on this Incident will be provided no later than 20:45 UTC. 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.

4. monitoring May 08, 2026, 09:01 PM UTC

   A fix has been implemented and we are monitoring the results. The next Status Update on this Incident will be provided no later than 21:30 UTC. 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. resolved May 08, 2026, 09:13 PM UTC

   The incident has been successfully resolved, and all services are operating normally. 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.

Read the full incident report →

Started May 08, 2026, 02:57 AM UTC· resolved May 08, 2026, 05:45 AM UTC

1. investigating May 08, 2026, 02:57 AM UTC

   We have discovered a potential service degradation, affecting Imperva Management Portal. The dashboards may not be not displaying the latest data. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 3:28 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 08, 2026, 03:36 AM UTC

   We are continuing to investigate. The next Status Update on this Incident will be provided no later than 3:58 UTC.

3. investigating May 08, 2026, 03:57 AM UTC

   Technical teams are continuing to work on a fix for the Imperva Management Portal dashboard issue. The next status update on this incident will be provided no later than 04:28 UTC.

4. investigating May 08, 2026, 04:26 AM UTC

   The technical teams are still working on the recovery for the Imperva Management Portal dashboard issue. The next status update on this incident will be provided no later than 05:28 UTC.

5. identified May 08, 2026, 05:19 AM UTC

   The issue has been identified and a fix is being implemented.

6. monitoring May 08, 2026, 05:37 AM UTC

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

7. resolved May 08, 2026, 05:45 AM UTC

   The incident has been resolved and normal service levels have been restored for the Cloud WAF Dashboards on the Imperva Management Portal.

Read the full incident report →

Started May 06, 2026, 11:36 AM UTC· resolved May 06, 2026, 03:04 PM UTC

1. investigating May 06, 2026, 11:36 AM UTC

   We are investigating a potential issue impacting Cloud WAF Protected Websites. Some websites may fail to load or return errors. Customer domains remain fully protected at this time. Our technical teams are actively working to identify the root cause, and further updates will be shared as more information becomes available. 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 May 06, 2026, 11:53 AM UTC

   We have identified the issue, and a fix is currently being implemented. The next Status Update on this Incident will be provided no later than 12:22 UTC.

3. identified May 06, 2026, 12:25 PM UTC

   We are continuing to actively work on implementing a fix. The next Status Update on this Incident will be provided no later than 12:55 UTC.

4. investigating May 06, 2026, 12:41 PM UTC

   Our investigation has determined that the previously suspected cause may be one contributing factor within a broader underlying root-cause pattern than initially identified. We are continuing to investigate and actively working to identify the underlying cause. The next Status Update on this Incident will be provided no later than 13:11 UTC.

5. investigating May 06, 2026, 01:10 PM UTC

   We are continuing to actively investigate this issue. The next Status Update on this Incident will be provided no later than 13:39 UTC.

6. investigating May 06, 2026, 01:43 PM UTC

   We are actively investigating this issue and continuing our efforts to identify the cause of the issue. The next Status Update on this Incident will be provided no later than 14:13 UTC.

7. monitoring May 06, 2026, 02:04 PM UTC

   A fix has been implemented, and services have returned to normal. We are continuing to monitor the situation closely to ensure stability. The next Status Update on this Incident will be provided no later than 15:04 UTC.

8. resolved May 06, 2026, 03:04 PM UTC

   The issue has been resolved, and monitoring has confirmed service stability.

Read the full incident report →

Started May 03, 2026, 10:48 AM UTC· resolved May 03, 2026, 04:28 PM UTC

1. investigating May 03, 2026, 10:48 AM UTC

   We have discovered a potential service degradation, affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. 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 May 03, 2026, 11:18 AM UTC

   We have identified the source of the service degradation affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 11:48 AM UTC. 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.

3. investigating May 03, 2026, 11:49 AM UTC

   Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 12:18 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.

4. identified May 03, 2026, 11:57 AM UTC

   During the course of the investigation our teams found that the issue also affects the Attack Analytics and Security log delivery via SIEM solution in the APAC region. The next status update on this incident will be provided no later than 12:27 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.

5. identified May 03, 2026, 12:31 PM UTC

   During the course of the investigation our teams found that the issue also affects ABP and Attack Analytics log delivery via SIEM solution in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 13:00 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.

6. identified May 03, 2026, 01:02 PM UTC

   Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 13:30 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.

7. identified May 03, 2026, 01:30 PM UTC

   The teams have identified a component potentially causing the issue. They are currently working to mitigate it. The next Status Update on this Incident will be provided no later than 14:00 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.

8. identified May 03, 2026, 02:03 PM UTC

   Team are actively working to mitigate the issue. The next Status Update on this Incident will be provided no later than 14:33 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

9. identified May 03, 2026, 02:33 PM UTC

   Technical teams are continuing to work on a fix the issue. The next status update on this incident will be provided no later than 15:03 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.

10. identified May 03, 2026, 03:06 PM UTC

    The team has resolved the Security Events page issue on the Management Platform; however, Attack Analytics, threat alert emails, and SIEM integrations may still be impacted. The next Status Update on this Incident will be provided no later than 15: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.

11. monitoring May 03, 2026, 03:28 PM UTC

    The incident has been resolved, and all services have returned to normal operating levels. We will continue to monitor the situation closely. 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.

12. resolved May 03, 2026, 04:28 PM UTC

    The incident has been resolved and normal service levels have been restored. 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.

Read the full incident report →

Started Apr 27, 2026, 11:04 AM UTC· resolved Apr 27, 2026, 11:31 AM UTC

1. investigating Apr 27, 2026, 11:04 AM UTC

   We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 11:34UTC. 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. monitoring Apr 27, 2026, 11:14 AM UTC

   Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. 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.

3. resolved Apr 27, 2026, 11:31 AM UTC

   The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. 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.

Read the full incident report →

Started Apr 24, 2026, 02:43 PM UTC· resolved Apr 25, 2026, 01:14 AM UTC

1. investigating Apr 24, 2026, 02:43 PM UTC

   We have discovered a potential issue affecting My Publishing. Technical teams are investigating. 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. investigating Apr 24, 2026, 03:24 PM UTC

   We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 03:54UTC. 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.

3. investigating Apr 24, 2026, 04:00 PM UTC

   The investigation into the service degradation affecting the Imperva Management Portal is ongoing, and the next update is scheduled for 16:30 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.

4. investigating Apr 24, 2026, 04:35 PM UTC

   The team is actively investigating the service degradation impacting the Imperva Management Portal, with the next update expected at 17:05 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.

5. investigating Apr 24, 2026, 05:05 PM UTC

   We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 18:05 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.

6. investigating Apr 24, 2026, 06:06 PM UTC

   We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 19:06 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.

7. investigating Apr 24, 2026, 07:07 PM UTC

   We are actively investigating a service degradation affecting the Imperva Management Portal. We will provide the next update as soon as more information becomes available. 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.

8. investigating Apr 24, 2026, 10:30 PM UTC

   The team is actively investigating the issue and processed approximately 30% of configuration change. The next update will be provided as soon as more information becomes available. 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.

9. identified Apr 24, 2026, 11:47 PM UTC

   We have identified the source of the service degradation that is causing delays in the propagation of recent configuration changes in the Imperva Management Portal. An additional 20% of configuration changes have been processed, reducing the overall delay. The next update will be provided at 00:47 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.

10. monitoring Apr 25, 2026, 12:02 AM UTC

    Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. 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.

11. resolved Apr 25, 2026, 01:14 AM UTC

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. 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.

Read the full incident report →

Started Apr 21, 2026, 11:21 PM UTC· resolved Apr 22, 2026, 12:08 AM UTC

1. investigating Apr 21, 2026, 11:21 PM UTC

   Technical teams are investigating a potential issue in the Santiago, Chile (STC) Data Center . Further updates to follow. The next Status Update on this Incident will be provided no later than 23:50 UTC.

2. monitoring Apr 21, 2026, 11:34 PM UTC

   A fix has been successfully implemented, and the issue has been remediated. All services are now operating as expected. We are continuing to closely monitor the environment to ensure stability and prevent any recurrence.

3. resolved Apr 22, 2026, 12:08 AM UTC

   The incident has been resolved, and all services have been restored to normal operation.

Read the full incident report →

Started Apr 13, 2026, 03:47 AM UTC· resolved Apr 13, 2026, 05:31 AM UTC

1. investigating Apr 13, 2026, 03:47 AM UTC

   We have discovered a potential service disruption affecting Imperva's API. Technical teams are investigating. 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. investigating Apr 13, 2026, 04:18 AM UTC

   We are continuing to investigate the potential service disruption affecting Imperva's API. The next Status Update on this Incident will be provided no later than 04:47 UTC. Further updates to follow.

3. investigating Apr 13, 2026, 04:47 AM UTC

   We are continuing to investigate the potential service disruption affecting Imperva's API. The next Status Update on this Incident will be provided no later than 5:17 UTC. Further updates to follow.

4. identified Apr 13, 2026, 04:53 AM UTC

   The issue has been identified and a fix is being implemented.

5. monitoring Apr 13, 2026, 04:59 AM UTC

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

6. resolved Apr 13, 2026, 05:31 AM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva's API service.

Read the full incident report →

Started Apr 09, 2026, 07:39 PM UTC· resolved Apr 10, 2026, 10:05 AM UTC

1. investigating Apr 09, 2026, 07:39 PM UTC

   We have identified a potential service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected at this time. Technical teams are actively investigating, and further updates will follow. The next Status Update on this Incident will be provided no later than 20:08 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 Apr 09, 2026, 08:06 PM UTC

   We continue to investigate the service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected, and our engineering teams are actively working toward resolution. The next Status Update on this Incident will be provided no later than 20: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.

3. investigating Apr 09, 2026, 08:36 PM UTC

   We continue to investigate the service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected, and our engineering teams are actively working toward resolution. The next Status Update on this Incident will be provided no later than 21:06 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.

4. identified Apr 09, 2026, 08:49 PM UTC

   We have identified the source of the service degradation impacting the Cloud WAF dashboard, resulting in missing data in the Security Events section. Technical teams are actively working on mitigation. The next status update for this incident will be provided no later than 21:19 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.

5. identified Apr 09, 2026, 09:20 PM UTC

   We have identified the source of the service degradation impacting the Cloud WAF dashboard, resulting in missing data in the Security Events section. A fix is currently being deployed by the technical teams. The next status update for this incident will be provided no later than 21:50 UTC.

6. identified Apr 09, 2026, 09:50 PM UTC

   The fix is currently being deployed by the technical teams. The next status update for this incident will be provided no later than 22:20 UTC.

7. identified Apr 09, 2026, 10:20 PM UTC

   The fix is currently being deployed by the technical teams. The next status update for this incident will be provided no later than 22:50 UTC.

8. identified Apr 09, 2026, 10:57 PM UTC

   The fix is currently being deployed by the technical teams. The next status update for this incident will be provided no later than 23:25 UTC.

9. identified Apr 09, 2026, 11:17 PM UTC

   Data visibility has been restored on the Cloud WAF dashboard, and systems are operating as expected. However, a gap remains for the period from yesterday until now. The data is present, but may not be fully visible across all resolutions. We are actively completing the remaining data processing and backfilling the missing data. New data is being reflected correctly on the dashboard. Full restoration is expected within approximately 10 hours.

10. resolved Apr 10, 2026, 10:05 AM UTC

    Final validation has been completed, data visibility on the Cloud WAF dashboard has been restored, and all systems are now functioning as expected. 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.

Read the full incident report →

Started Apr 09, 2026, 07:49 AM UTC· resolved Apr 10, 2026, 01:16 AM UTC

1. investigating Apr 09, 2026, 07:49 AM UTC

   We have discovered a potential service degradation affecting Advance Bot Protection customers. Customer websites are returning browser errors to some end users. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. 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. investigating Apr 09, 2026, 08:55 AM UTC

   We are continuing to investigate the potential service disruption affecting Advanced Bot Protection. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 09:25 UTC. 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.

3. investigating Apr 09, 2026, 09:26 AM UTC

   We are continuing to investigate the potential service disruption affecting Advanced Bot Protection. Our technical teams are actively investigating the set of contributing factors. The next Status Update on this Incident will be provided no later than 09:55 UTC. 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.

4. investigating Apr 09, 2026, 09:56 AM UTC

   We are continuing to investigate a potential service disruption affecting Advanced Bot Protection. Our technical teams are actively working to identify the cause. The next status update on this incident will be provided no later than 10:25 UTC.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. investigating Apr 09, 2026, 10:26 AM UTC

   We are actively investigating a potential service disruption impacting Advanced Bot Protection. Engineering teams are engaged and working to determine the cause and contributing factors. The next update will be provided by 11:55 UTC.

6. identified Apr 09, 2026, 10:45 AM UTC

   We have identified an issue in key rotation which is affecting tokens for Advance Bot Protection customers. Technical teams are working on a mitigation. The next status update on this incident will be provided no later than 11:15 UTC. 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.

7. identified Apr 09, 2026, 11:19 AM UTC

   Technical teams are working on a FIX. The next status update on this incident will be provided no later than 11:50 UTC. 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.

8. identified Apr 09, 2026, 11:50 AM UTC

   Technical teams are working on a FIX. The next status update on this incident will be provided no later than 12:20 UTC. 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.

9. identified Apr 09, 2026, 12:20 PM UTC

   Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 12:50 UTC. 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.

10. identified Apr 09, 2026, 12:50 PM UTC

    Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 13:20 UTC. 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.

11. identified Apr 09, 2026, 01:20 PM UTC

    Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 13:50 UTC. 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.

12. identified Apr 09, 2026, 01:51 PM UTC

    We are rolling out the fix in a phased manner globally to reduce the risk of additional impact to live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 14:50 UTC. 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.

13. identified Apr 09, 2026, 02:50 PM UTC

    We are rolling out the fix in a phased manner globally to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 15:50 UTC. 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.

14. identified Apr 09, 2026, 03:51 PM UTC

    We are deploying the fix globally in a phased approach to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 16:50 UTC. 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.

15. identified Apr 09, 2026, 04:50 PM UTC

    We are deploying the fix globally in a phased approach to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 17:50 UTC. 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.

16. identified Apr 09, 2026, 05:50 PM UTC

    The phased global deployment is currently in progress. Monitoring is ongoing as we continue with the rollout. The next status update will be provided no later than 18:50 UTC.

17. identified Apr 09, 2026, 06:50 PM UTC

    The phased global rollout is currently underway, with continuous monitoring in place. The next status update will be provided no later than 19:50 UTC.

18. monitoring Apr 09, 2026, 07:12 PM UTC

    The phased global rollout has been successfully completed. Systems are stable, and monitoring is ongoing to ensure continued normal operation.

19. monitoring Apr 09, 2026, 09:37 PM UTC

    Services remain stable. Monitoring has been in progress and will continue for an extended period to ensure sustained stability and normal operation.

20. resolved Apr 10, 2026, 01:16 AM UTC

    The incident has been resolved and normal service levels have been restored for the Imperva Advanced Bot Protection service.

Read the full incident report →

Started Apr 05, 2026, 02:02 PM UTC· resolved Apr 05, 2026, 02:55 PM UTC

1. investigating Apr 05, 2026, 02:02 PM UTC

   Technical teams are investigating a potential CWAF issue in the (DFW, EWR, IAD, LCY, NYC, PAR) Data Center . Further updates to follow.

2. monitoring Apr 05, 2026, 02:39 PM UTC

   The issue appears to be resolved at this time. We are continuing to monitor in order to ensure that service has returned to normal. 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.

3. resolved Apr 05, 2026, 02:55 PM UTC

   Service in the data centers have been restored to normal. 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.

Read the full incident report →

Started Mar 27, 2026, 12:23 PM UTC· resolved Mar 27, 2026, 01:32 PM UTC

1. investigating Mar 27, 2026, 12:23 PM UTC

   Technical teams are investigating a potential issue in the Johannesburg, South Africa (QRA) data center. 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. monitoring Mar 27, 2026, 12:32 PM UTC

   A fix has been implemented, and the issue has been mitigated. We are continuing to monitor in order to ensure that service has returned to normal. 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.

3. resolved Mar 27, 2026, 01:32 PM UTC

   Some customer traffic being processed in Johannesburg, South Africa (QRA) PoP may have experienced higher than expected latency and packet loss due to an upstream provider issue, outside of the Thales Imperva Network. Engineers bypassed two impacted circuits in order to remove them from production, resulting in stabilized traffic. Services are now stable. Additional details will be provided following a completed root cause analysis.

Read the full incident report →

Started Mar 27, 2026, 11:17 AM UTC· resolved Mar 27, 2026, 02:57 PM UTC

1. investigating Mar 27, 2026, 11:17 AM UTC

   We have discovered a degradation in our statistics affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center . Customer domains are still fully protected at this time. Technical teams are investigating. 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. investigating Mar 27, 2026, 12:28 PM UTC

   We are continuing to investigate the degradation affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center. Customer domains are still fully protected at this time. Technical teams are investigating. 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.

3. investigating Mar 27, 2026, 01:06 PM UTC

   Technical teams are continuing to investigate the degradation affecting the Imperva GRE Performance Dashboard across multiple data centers. 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.

4. identified Mar 27, 2026, 01:56 PM UTC

   We have identified the source of the degradation affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center. Customer domains are still fully protected at this time. 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 Mar 27, 2026, 02:02 PM UTC

   Technical teams have performed remedial actions and the Imperva GRE Performance Dashboard are now correctly displaying data. No data has been lost during this event. 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.

6. resolved Mar 27, 2026, 02:57 PM UTC

   The incident has been resolved and normal service levels have been restored for the Imperva GRE Performance Dashboard. 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.

Read the full incident report →

Started Mar 21, 2026, 06:00 AM UTC· resolved Mar 21, 2026, 09:33 AM UTC

1. investigating Mar 21, 2026, 06:00 AM UTC

   Technical teams are investigating a potential issue in the New York 2, NY (EWR) Data Center . 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 Mar 21, 2026, 06:07 AM UTC

   We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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.

3. identified Mar 21, 2026, 06:44 AM UTC

   As a precautionary measure, the New York 2, NY (EWR) Data Center data center will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

4. monitoring Mar 21, 2026, 09:01 AM UTC

   A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. 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. resolved Mar 21, 2026, 09:33 AM UTC

   Service in the data center has been restored to normal. 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.

Read the full incident report →

Started Mar 20, 2026, 08:38 PM UTC· resolved Mar 21, 2026, 03:45 AM UTC

1. investigating Mar 20, 2026, 08:38 PM UTC

   Technical teams are investigating a potential issue in the Dusseldorf, Germany (DUS) data center. 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 Mar 20, 2026, 09:00 PM UTC

   We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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.

3. identified Mar 20, 2026, 09:16 PM UTC

   As a precautionary measure, the Dusseldorf, Germany (DUS) data center will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

4. monitoring Mar 21, 2026, 02:35 AM UTC

   A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. 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. resolved Mar 21, 2026, 03:45 AM UTC

   Service in the data center has been restored to normal. 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.

Read the full incident report →