- Detected by Pingoru
- Jun 11, 2026, 08:07 AM UTC
- Resolved
- Jun 11, 2026, 08:39 AM UTC
- Duration
- 32m
Affected: Web Application Performance
Timeline · 3 updates
-
investigating Jun 11, 2026, 08:07 AM UTC
We are currently investigating increased latency affecting Imperva Cloud WAF protected sites. At this time, a portion of Imperva Cloud WAF customers may experience slower response times when accessing protected applications through Imperva. Our teams are actively investigating the cause and working to mitigate the impact. We will provide another update as more information becomes available. The next update will be at 08:36 UTC at the latest.
-
monitoring Jun 11, 2026, 08:15 AM UTC
The issue causing increased latency for Imperva Cloud WAF protected sites has been mitigated. Service performance has returned to normal, and our teams are continuing to monitor closely to ensure continued stability. We will provide a final update once monitoring is complete. Please note service impact continued for approximately 10 minutes.
-
resolved Jun 11, 2026, 08:39 AM UTC
This issue has been resolved. Our teams have confirmed that service performance for Imperva Cloud WAF protected sites has returned to normal and remained stable following mitigation. We will continue to monitor service health as part of our standard operational processes. Thank you for your patience while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:53 PM UTC
- Resolved
- Jun 11, 2026, 12:43 AM UTC
- Duration
- 5h 49m
Affected: Cloud Security Management Platform
Timeline · 8 updates
-
investigating Jun 10, 2026, 06:53 PM 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. Next update on the issue will be provided no later than 19:23 UTC.
-
investigating Jun 10, 2026, 07:24 PM UTC
The team continues to actively investigate the issue and work toward resolution. At this time, the impact is limited to customer access to the Management Portal. Customer websites and protection services remain fully operational and continue to be protected as expected. Next update on the issue will be provided no later than 19:54 UTC.
-
investigating Jun 10, 2026, 07:54 PM UTC
Technical teams continue to actively investigate the issue. A potential contributing factor has been identified, and teams are currently working to validate and address it. Next update on the issue will be provided no later than 20:24 UTC.
-
identified Jun 10, 2026, 08:19 PM UTC
We have identified the underlying cause of the issue and have applied a fix. The issue affected access to the Management Portal and a subset of API requests. We are seeing signs of recovery following the implementation of the fix, and our teams are actively validating service restoration across the impacted components. Next update on the issue will be provided no later than 20:50 UTC.
-
monitoring Jun 10, 2026, 08:42 PM UTC
A fix has been successfully implemented, and services have been restored. Our teams have validated the recovery and are continuing to closely monitor the environment to ensure ongoing stability. Next update on the issue will be provided no later than 21:42 UTC.
-
monitoring Jun 10, 2026, 09:43 PM UTC
Services remain stable following the implementation of the fix, and no further issues have been observed. Our teams will continue to closely monitor the environment for an extended period to ensure stability. Next update on the issue will be provided no later than 23:43 UTC.
-
monitoring Jun 10, 2026, 11:47 PM UTC
Services remain stable, and no further issues have been observed. Our teams will continue to closely monitor the environment to ensure ongoing stability and verify that all services continue to operate as expected. Next update on the issue will be provided no later than 01:45 UTC on 11 June 2026.
-
resolved Jun 11, 2026, 12:43 AM UTC
Monitoring has confirmed that services remain stable following the implementation of the fix and the completion of validation activities. No further issues have been observed.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 01:29 PM UTC
- Resolved
- Jun 03, 2026, 02:55 PM UTC
- Duration
- 1h 25m
Affected: Sao Paulo, Brazil (SAO)
Timeline · 4 updates
-
identified Jun 03, 2026, 01:29 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. Next update will be shared 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.
-
investigating Jun 03, 2026, 01:59 PM UTC
Technical teams are continuing to working on a fix for the data center issue. 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. Next update will be shared no later than 14: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.
-
monitoring Jun 03, 2026, 02:25 PM 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. Next update will be shared no later than 14:56 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.
-
resolved Jun 03, 2026, 02:55 PM 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 →
- Detected by Pingoru
- Jun 03, 2026, 08:36 AM UTC
- Resolved
- Jun 03, 2026, 09:40 AM UTC
- Duration
- 1h 4m
Affected: Cloud Security Management PlatformWeb Application Performance
Timeline · 4 updates
-
investigating Jun 03, 2026, 08:36 AM UTC
We are currently investigating an issue causing slowness on the Management Platform and Customers accessing onboarded sites from the APAC region may experience intermittent latency or delays when reaching their protected websites. Our teams are actively investigating the cause and working to restore normal service performance. We will provide additional updates as more information becomes available. Next update will be shared no later then 09:00 UTC.
-
identified Jun 03, 2026, 08:59 AM UTC
We have identified the source of the service degradation causing slowness on the Management Platform and customers accessing onboarded sites from the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Next update will be shared no later then 09: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.
-
monitoring Jun 03, 2026, 09:11 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. Next update will be shared no later than 09:42 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.
-
resolved Jun 03, 2026, 09:40 AM UTC
The incident has been resolved and normal service levels have been restored for the 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 →
- Detected by Pingoru
- May 29, 2026, 05:25 PM UTC
- Resolved
- Jun 04, 2026, 06:30 AM UTC
- Duration
- 5d 13h
Affected: New York 2, NY (EWR)
Timeline · 19 updates
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 07:08 PM UTC
- Resolved
- May 29, 2026, 11:05 AM UTC
- Duration
- 15h 57m
Affected: Vancouver, Canada (VAN)
Timeline · 7 updates
-
identified May 28, 2026, 07:08 PM UTC
We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center. The next update will be provided no later than 19:38 UTC.
-
identified May 28, 2026, 07:24 PM UTC
We have identified connectivity issues in our Vancouver, Canada (VAN) data center. Traffic is being re-routed to an alternate data center. The next update will be provided no later than 19:54 UTC.
-
identified May 28, 2026, 07:54 PM UTC
We have identified intermittent connectivity issues affecting the Vancouver, Canada (VAN) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next update will be provided no later than 20:24 UTC.
-
identified May 28, 2026, 08:44 PM UTC
As a precautionary measure, the Vancouver, Canada (VAN) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.
-
identified May 28, 2026, 09:55 PM UTC
The technical teams have identified an issue affecting the Vancouver, Canada (VAN) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.
-
monitoring May 29, 2026, 10:18 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 next update will be provided no later than 11:18 UTC.
-
resolved May 29, 2026, 11:05 AM UTC
Service in the data center has been restored to normal.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 06:09 PM UTC
- Resolved
- May 29, 2026, 12:01 PM UTC
- Duration
- 17h 51m
Affected: New York 2, NY (EWR)
Timeline · 13 updates
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 07:22 PM UTC
- Resolved
- May 27, 2026, 10:52 PM UTC
- Duration
- 3h 29m
Affected: ABP ManagementAdvanced BOT Protection
Timeline · 5 updates
-
investigating May 27, 2026, 07:22 PM UTC
We have discovered a potential service degradation, affecting some ABP dashboards. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. Further updates to follow. Next update will be shared no later then 19:52 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.
-
investigating May 27, 2026, 08:04 PM UTC
Investigation and remediation activities are currently in progress, with engineering teams actively working to identify the root cause and restore service stability. Next update will be shared no later then 20:33 UTC.
-
monitoring May 27, 2026, 08:47 PM UTC
Technical teams have implemented mitigation measures and the ABP dashboards are now operating normally. Teams will continue to closely monitor the environment, and further updates will be shared as they become available.
-
monitoring May 27, 2026, 10:23 PM UTC
The technical team remains in the monitoring phase to ensure service stability and confirm that the issue does not recur. The next update will be shared no later then 22:53 UTC.
-
resolved May 27, 2026, 10:52 PM UTC
No abnormalities were observed during the monitoring period. The incident has been resolved, and normal service levels have been fully restored for the Imperva Advanced Bot Protection service.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 10:56 PM UTC
- Resolved
- May 22, 2026, 11:59 PM UTC
- Duration
- 1h 3m
Affected: Cloud Security Management Platform
Timeline · 4 updates
-
investigating May 22, 2026, 10:56 PM UTC
We have discovered a potential issue affecting sites certificates validation. Technical teams are investigating. The next update will be shared no later then 23: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.
-
investigating May 22, 2026, 11:39 PM UTC
Remediation efforts are ongoing and teams are actively working to stabilize the services. The next update will be communicated at 00:10 UTC.
-
identified May 22, 2026, 11:53 PM UTC
Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance.
-
resolved May 22, 2026, 11:59 PM UTC
A fix has been implemented and all services are operating normally. The incident has been successfully resolved,
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 09:06 PM UTC
- Resolved
- May 22, 2026, 09:20 PM UTC
- Duration
- 3d
Affected: Cloud Security Management Configuration Changes
Timeline · 38 updates
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 08:50 PM UTC
- Resolved
- May 17, 2026, 06:36 AM UTC
- Duration
- 9h 46m
Affected: Cloud Security Management Configuration Changes
Timeline · 18 updates
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 07:22 PM UTC
- Resolved
- May 15, 2026, 11:29 PM UTC
- Duration
- 4h 6m
Affected: Cloud Security Management Platform
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 07:16 PM UTC
- Resolved
- May 15, 2026, 07:14 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 15, 2026, 07:16 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 19:44UTC. 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.
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 08:17 AM UTC
- Resolved
- May 15, 2026, 11:42 AM UTC
- Duration
- 3h 24m
Affected: Account and User Management
Timeline · 5 updates
-
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.
-
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
-
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
-
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.
-
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 →
- Detected by Pingoru
- May 14, 2026, 07:49 PM UTC
- Resolved
- May 15, 2026, 12:32 AM UTC
- Duration
- 4h 43m
Affected: Mumbai, India (NAG)New Delhi, India (NDL)
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 05:26 PM UTC
- Resolved
- May 14, 2026, 06:28 PM UTC
- Duration
- 1h 1m
Affected: Cloud Security Management Platform
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- May 13, 2026, 01:57 AM UTC
- Resolved
- May 13, 2026, 01:57 AM UTC
- Duration
- —
Affected: Buenos Aires, Argentina (EZE)
Timeline · 1 update
-
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 →
- Detected by Pingoru
- May 12, 2026, 10:56 AM UTC
- Resolved
- May 12, 2026, 12:15 PM UTC
- Duration
- 1h 18m
Affected: Cloud Security Management Platform
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- May 12, 2026, 07:49 AM UTC
- Resolved
- May 12, 2026, 07:49 AM UTC
- Duration
- —
Affected: Vancouver, Canada (VAN)
Timeline · 1 update
-
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 →
- Detected by Pingoru
- May 11, 2026, 06:32 AM UTC
- Resolved
- May 11, 2026, 08:33 AM UTC
- Duration
- 2h 1m
Affected: Cloud Security Management Platform
Timeline · 5 updates
-
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.
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- May 11, 2026, 12:47 AM UTC
- Resolved
- May 11, 2026, 02:22 PM UTC
- Duration
- 13h 34m
Affected: Ashburn, VA (IAD)
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- May 10, 2026, 01:35 PM UTC
- Resolved
- May 10, 2026, 04:21 PM UTC
- Duration
- 2h 45m
Affected: Ashburn, VA (IAD)Cloud WAF ProtectionBarcelona, Spain (BCN)Amsterdam, Netherlands (RTM)Frankfurt, Germany (HHN)Copenhagen, Denmark (CPH)Dallas, TX (DFW)Queretaro, Mexico (QRO)Denver, CO (DEN)Detroit, MI (DET)Houston, TX (HOU)L3/4 Network DDoS ProtectionLondon, UK (LCY)Madrid, Spain (MAD)Paris, France (PAR)Vienna, Austria (GRZ)Warsaw, Poland (WAR)
Timeline · 4 updates
-
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.
-
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.
-
monitoring May 10, 2026, 03:02 PM UTC
We are continuing to monitor for any further issues.
-
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 →
- Detected by Pingoru
- May 10, 2026, 12:10 PM UTC
- Resolved
- May 10, 2026, 01:28 PM UTC
- Duration
- 1h 18m
Affected: Cloud Security Management Platform
Timeline · 5 updates
-
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.
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- May 08, 2026, 07:37 PM UTC
- Resolved
- May 08, 2026, 09:13 PM UTC
- Duration
- 1h 36m
Affected: Cloud WAF Protection
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 02:57 AM UTC
- Resolved
- May 08, 2026, 05:45 AM UTC
- Duration
- 2h 47m
Affected: CDN and WAF ManagementNetwork DDoS ManagementAttack Analytic
Timeline · 7 updates
-
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.
-
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.
-
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.
-
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.
-
identified May 08, 2026, 05:19 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 08, 2026, 05:37 AM UTC
A fix has been implemented and we are monitoring the results.
-
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 →