Imperva Outage History
Uptime record, past incidents, and downtime history for Imperva.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 0% | 25 | 25 |
| April 2026 | 0% | 30 | 30 |
| March 2026 | 3.2% | 31 | 30 |
| February 2026 | 40% | 5 | 3 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
[INC-1049] Issue with creation of the site certificates.
Started: May 22, 10:56 PM
identified
Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance.
May 22, 11:53 PM
investigating
Remediation efforts are ongoing and teams are actively working to stabilize the services.
The next update will be communicated at 00:10 UTC.
May 22, 11:39 PM
investigating
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 pot...
May 22, 10:56 PM
[INC-1045] Imperva Management Portal Configuration Changes Issue
Started: May 19, 9:06 PM
monitoring
Monitoring has confirmed that all services are operating normally, including new provisioning activities and configuration changes across sites and accounts.
Processing of all previously pending configuration items has now been fully completed and verified. We will continue to closely monitor the platform to ensure ongoing stability and promptly address any unexpected issues.
The next Status Update on this issue will be provided no later than 21:30 UTC.
May 22, 3:31 PM
identified
We expect to complete the processing of all pending config changes within the next hour.
Once this is completed and verified, we'll monitor the platform for some time to make sure there are no other issues.
We will post the next update no later than 1700UTC.
May 22, 2:42 PM
identified
Monitoring has confirmed that all services are operating as normal with any new provisioning or changes to any site or account configuration.
The tasks to work through the previous pending configuration items is still on-going and is expected to complete within the previously indicated timeframe.
Imperva is fully aware of the impact this incident has had on our customers, and apologises unreservedly for it.
A further update on the progress of applying pending config changes will be provide...
May 22, 7:37 AM
identified
Our technical teams have confirmed that configuration changes are now propagating normally. Remaining backlog processing activities are still ongoing and are expected to complete within approximately one day.
The environment continues to be closely monitored, and we will provide the next update regarding backlog progress no later than 08:00 UTC on Friday, 22 May 2026.
May 21, 8:53 PM
identified
The Technical team confirmed that the pending queue has been successfully cleared and is currently executing a script to process the events that were skipped yesterday. Current configuration changes are now publishing as expected.
However, some configuration changes made within the last 36 hours including Custom TLS Certificate uploads, Rule or Policy creations, updates or deletions, and Site configuration modifications may not yet be fully reflected in CWAF traffic handling. These remaining...
May 21, 6:45 PM
identified
Currently, new configuration changes made in the UMC are continuing to be applied successfully. However, we are presently observing an approximate propagation delay of 40 minutes while backlog processing activities continue.
Some configuration changes made during the last 36 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes con...
May 21, 4:55 PM
identified
Currently, new configuration changes made in the UMC are continuing to be applied successfully. However, we are presently observing an approximate propagation delay of 40 minutes while backlog processing activities continue.
Some configuration changes made during the last 36 hours — including Custom TLS Certificate uploads, Rule or Policy creations, deletions or updates, and Site configuration edits — may still not yet be fully reflected in cWAF traffic handling. These pending changes con...
May 21, 4:23 PM
identified
Currently, any new configuration changes made in the UMC are being applied as expected without any extra delay.
Some config changes (including Custom TLS Cert Uploads, Rule or Policy creations, deletions or updates, and Site config edits) made during the last 36 hours may not yet be reflected in the cWAF traffic handling. These pending changes are being published in batches and this is expected to complete within 24-36hrs.
Customers with concerns regarding specific configuration changes are...
May 21, 1:52 PM
identified
We apologize for the extended time since the last update. Our teams remain actively engaged and continue remediation efforts for the Management Console configuration publishing service.
At this stage, newly created or updated configurations are being published without delay. The periodic publishing process is continuing to work through the remaining backlog of previously queued configuration changes. While this recovery work continues, some customers may still observe delays related to earli...
May 21, 8:30 AM
identified
Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. Backlog items are still being processed, while new configuration changes are currently published successfully.
May 21, 1:56 AM
identified
The Technical teams remain engaged in ongoing validation and analysis efforts to evaluate the impact on overall service performance. While certain backlog items are still awaiting processing, new configuration changes are currently publishing successfully.
The next Status Update on this issue will be provided no later than 01:00 UTC.
May 21, 12:00 AM
identified
The investigation has identified a possible contributing factor related to the issue, and the engineering teams are continuing validation and analysis to assess its impact on overall service performance. Meanwhile, although some backlog items are still pending, current configuration changes are being published successfully.
The next update will be communicated at 23:32 UTC.
May 20, 10:32 PM
investigating
Technical team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance.
The next status update will be provided no later than 22:49 UTC.
May 20, 9:49 PM
investigating
Engineering teams are continuing remediation efforts to restore full platform functionality at the earliest opportunity. Meanwhile, all existing configurations and active security protections remain stable and fully operational.
The next status update will be provided no later than 21:37 UTC.
May 20, 8:37 PM
investigating
Our engineering teams are actively working to mitigate the issue and restore full service functionality as quickly as possible. At this time, existing configurations and active protections continue to operate normally and remain fully in effect.
The next status update will be provided no later than 20:30 UTC.
May 20, 7:30 PM
investigating
Our teams are actively investigating an issue impacting the propagation of configuration updates. Customers may encounter delays or inconsistent behavior while publishing new or modified configurations.
Engineering teams continue to work on mitigation and recovery efforts to restore full service functionality as soon as possible. Existing configurations and currently active protections remain unaffected and operational.
The next status update will be provided no later than 19:25 UTC.
May 20, 6:25 PM
investigating
We continue to investigate issues affecting the propagation of configuration changes. Customers may experience delays or inconsistencies when publishing new or updated configurations.
Our engineering teams remain actively engaged and are continuing remediation efforts to restore normal service functionality as quickly as possible.
Existing configurations and active protections remain in place.
The next status update will be provided no later than 18:00 UTC.
May 20, 5:00 PM
investigating
Remediation efforts are ongoing for the issue affecting Management Console configuration propagation. Our engineering teams have identified a potential cause impacting the functionality and are actively working on remediation and validation activities.
The next status update will be provided no later than 17:02 UTC.
May 20, 4:02 PM
investigating
Following the earlier remediation activities related to the Management Console configuration publishing service, we are currently investigating an additional issue affecting the propagation of configuration changes. Customers may experience delays or inconsistencies when publishing new or updated configurations, where changes may appear successfully published but are not fully propagated across the environment.
Our engineering teams remain actively engaged and are continuing investigation and...
May 20, 3:03 PM
monitoring
Our monitoring has identified that some configuration changes have not propagated as expected. Engineering teams are actively investigating the issue and continuing remediation efforts to restore normal configuration publishing behavior.
The next status update will be provided no later than 15:10 UTC.
May 20, 2:10 PM
monitoring
Processing of the backlog is complete. We are monitoring the situation carefully, but all changes saved in the UMC are now being published as expected and all pending configuration changes have been applied.
We will continue to closely monitor the service until 13:56 UTC.
May 20, 12:56 PM
monitoring
Remediation activities for the Management Console configuration publishing service are ongoing, with multiple teams actively engaged in restoring full service functionality.
Imperva is aware of the impact this incident has had on our customers and apologizes for both the scope and duration of the disruption.
The backlog is currently being processed, and recovery efforts continue to make progress. Existing configurations and active protections remain in place and continue to operate as expec...
May 20, 12:11 PM
monitoring
Remediation efforts for the Management Console configuration publishing service are still underway. Multiple teams remain actively engaged and are working to fully restore service functionality.
Existing configurations and active protections continue to remain in place.
The next status update will be provided no later than 12:10 UTC.
May 20, 11:10 AM
monitoring
Remediation activities for the Management Console configuration publishing service are ongoing. Multiple teams remain actively engaged and are working to fully restore service functionality.
Existing configurations and active protections continue to remain in place.
The next Status Update on this issue will be provided no later than 11:10 UTC.
May 20, 10:10 AM
monitoring
We are continuing remediation efforts for the Management Console configuration publishing service.
Customers may still experience delays when publishing new or updated configurations from the Management Console. In addition, some customers may experience issues when onboarding new websites, as this process depends on the same configuration publishing flow.
Existing configurations and active protections remain in place.
Our technical teams remain actively engaged and are continuing to work...
May 20, 9:12 AM
monitoring
Technical teams continue working to fully restore the Management Console configuration publishing service.
Customers may experience delays when publishing new or updated configurations from the Management Console. During this time, recent configuration changes may take longer than expected to propagate and become active.
Existing configurations and protections remain in place.
Additional remediation actions have been identified to support a stable return to normal operations. The environmen...
May 20, 8:13 AM
monitoring
While base remediation is still on-going, some additional actions have been identified as required in order to restore full service. These actions are required to ensure longer term stability and a seamless return to regular operations.
The next Status Update on this issue will be provided no later than 08:12 UTC.
May 20, 7:14 AM
monitoring
Technical teams are still actively working to restore the service following the remediation actions. The next update will be communicated at 07:12 UTC.
May 20, 5:12 AM
monitoring
Technical teams are actively working to restore the service following the remediation actions. Some delays may still be experienced while publishing activity gradually returns to normal. Full synchronization may take a few additional hours. The next update will be communicated at 05:12 UTC.
May 20, 3:12 AM
monitoring
System performance is continuing to recover and is expected to recover in the next few hours. The environment remains under active monitoring by the technical teams. The next update will be communicated at 03:12 UTC.
May 20, 1:12 AM
identified
System performance is continuing to recover following the remediation actions implemented by the technical teams. Overall service stability is improving; however, still we're observing delay in publishing. The environment remains under active monitoring by the technical teams.
The next update will be communicated at 01:04 UTC.
May 20, 12:36 AM
identified
Technical teams have identified the root cause and applied corrective actions. System performance is steadily improving; however, some delays may still be experienced while publishing activity gradually returns to normal. Full synchronization may take a few additional hours.
The next update will be communicated at 00:27 UTC.
May 19, 11:58 PM
identified
Technical team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance.
The next update will be communicated at 23:56 UTC.
May 19, 11:27 PM
identified
Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance.
The next update will be communicated at 23:16 UTC.
May 19, 10:46 PM
investigating
The ongoing service degradation affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. remains under active investigation by the Engineering team.
The next status update will be shared no later than 22:47 UTC.
May 19, 10:18 PM
investigating
The investigation into the service degradation impacting the Imperva Management Portal is ongoing. Recent configuration changes are experiencing propagation delays, and technical teams are actively investigating the issue.
The next status update will be shared no later than 22:14 UTC.
May 19, 9:44 PM
investigating
We have discovered a potential service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay.
The next Status Update on this Incident will be provided no later than 21:36 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
...
May 19, 9:06 PM
[INC-1042] Issues with Imperva Management Portal Configuration Changes
Started: May 16, 8:50 PM
monitoring
The backlog has been fully processed, and the system is now operating as expected. We will continue to monitor to ensure ongoing stability.
May 17, 5:42 AM
identified
We are seeing continued progress, with the backlog steadily decreasing and system performance improving.
The next update will be shared no later than 06:05 UTC.
May 17, 5:35 AM
identified
We are taking additional actions to improve system performance. These steps are expected to help accelerate recovery and reduce remaining delays. We will continue to share updates as progress continues.
The next update will be shared no later than 05:40 UTC.
May 17, 5:10 AM
identified
We continue to work on improving system performance. While some progress has been made, certain delays may still persist. Our teams remain actively engaged in resolving the issue and restoring full service stability. The next update will be shared no later than 05:15 UTC.
May 17, 4:46 AM
identified
We continue to see improvements in system performance following the fixes implemented by our technical teams. Service stability is improving, although some delays may still persist as publishing activity continues to catch up over the next few hours.
The next update will be shared no later than 04:23 UTC.
May 17, 3:54 AM
identified
Technical teams have identified the issue and implemented fixes. We are seeing steady improvements in system performance. Some delays may still persist, and it may take a few hours for publishing activity to fully catch up.
The next update will be shared no later than 03:53 UTC.
May 17, 3:24 AM
investigating
Investigation is in progress, and our teams are actively engaged in working toward resolving the issue.
The next update will be shared no later than 03:23 UTC.
May 17, 2:53 AM
investigating
The investigation is ongoing, and the team continues to actively work towards remediation.
The next update will be shared no later than 02:53 UTC.
May 17, 2:23 AM
investigating
The investigation is ongoing, and the team is actively analyzing potential contributing factors. Efforts are focused on reducing the impact and stabilizing service performance.
The next update will be communicated at 02:20 UTC.
May 17, 1:51 AM
investigating
Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance.
The next update will be communicated at 01:50 UTC.
May 17, 1:21 AM
investigating
Investigation is ongoing, and our technical teams are actively working to restore full service stability.
The next update will be communicated at 01:15 UTC.
May 17, 12:45 AM
investigating
Technical team continue to work on remediation activities to restore service stability.
The next update will be communicated at 00:42 UTC.
May 17, 12:12 AM
investigating
The Imperva Management Portal will be unavailable for the next 30 minutes; however, all applications will remain protected by Cloud WAF. The next update will be communicated at 00:11 UTC.
May 16, 11:43 PM
investigating
Mitigation activities are still in progress, and teams continue working to restore service stability. The next update will be shared once a significant development is available.
May 16, 10:47 PM
investigating
The ongoing service degradation affecting the Imperva Management Portal remains under active investigation by the Engineering team. The next update will be communicated at 22:30 UTC.
May 16, 10:01 PM
investigating
Engineering team actively investigating the ongoing service degradation impacting the Imperva Management Portal. The next update will be provided at 21:53 UTC.
May 16, 9:23 PM
investigating
We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 21:20 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.
May 16, 8:50 PM
[INC-1040] Imperva Management Portal Login Issue
Started: May 15, 7:22 PM
monitoring
Technical teams have performed remedial actions and the Imperva Support Portal access is returning to normal operations.
Technical teams will continue monitoring the system.
May 15, 11:08 PM
identified
Technical teams have completed mitigation actions, and access to the Imperva Support Portal is returning to normal levels. Teams will continue to closely monitor system operations.
Rest assured, all applications continue to remain protected by Cloud WAF.
However, issues related to the publisher service are still being observed, and active efforts are ongoing to fully stabilize the environment.
The next update for this incident will be shared no later than 23:17 UTC.
May 15, 10:47 PM
identified
Teams have identified a possible cause behind the service degradation affecting customers ability to log in to the Imperva Management Portal.
Engineering teams are actively engaged in mitigation and recovery efforts to restore service stability.
The next update for this incident will be shared no later than 22:44 UTC.
May 15, 10:14 PM
investigating
Teams have identified a possible cause behind the service degradation affecting customers ability to log in to the Imperva Management Portal.
Engineering teams are actively engaged in mitigation and recovery efforts to restore service stability.
The next update for this incident will be shared no later than 22:42 UTC.
May 15, 10:13 PM
investigating
Teams continue to work on remediation activities, and a decrease in login-related errors has been observed. While the issue is still occurring intermittently, active efforts are ongoing to restore full service stability.
The next update regarding this incident will be provided no later than 22:00 UTC.
May 15, 9:33 PM
investigating
Remediation efforts are ongoing, and we are seeing a reduction in login errors. The issue remains intermittent, and teams are actively working to stabilize the services.
Next update on this incident will be shared no later than 21:30 UTC.
May 15, 9:00 PM
investigating
Investigations are currently in progress, and the team is actively working on the issue.
Next update on this incident will be shared no later than 20:51 UTC.
May 15, 8:21 PM
investigating
Our technical teams are actively investigating the issue and working on remediation.
Next update on this incident will be shared no later than 20:21 UTC.
May 15, 7:51 PM
investigating
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 w...
May 15, 7:22 PM
[INC-1038] Imperva Management Portal UI Performance Degradation
Started: May 15, 8:17 AM
monitoring
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.
May 15, 9:52 AM
investigating
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
May 15, 9:21 AM
investigating
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
May 15, 8:53 AM
investigating
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 attribute...
May 15, 8:17 AM
[INC-1037] New Delhi, Mumbai Data Center Issue
Started: May 14, 7:49 PM
monitoring
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.
May 14, 11:55 PM
identified
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 impact...
May 14, 10:55 PM
identified
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 i...
May 14, 9:55 PM
identified
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 i...
May 14, 9:25 PM
identified
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 disruptio...
May 14, 8:55 PM
identified
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 wil...
May 14, 8:21 PM
investigating
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.
May 14, 7:49 PM
[INC-1036] Imperva Management Portal Slowness Issue
Started: May 14, 5:26 PM
monitoring
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 disruptio...
May 14, 5:58 PM
investigating
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 avail...
May 14, 5:26 PM
[INC-1034] Imperva Management Portal Login Issue
Started: May 12, 10:56 AM
monitoring
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 disruptio...
May 12, 11:23 AM
investigating
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 w...
May 12, 10:56 AM
[INC-1031] Imperva Management Portal Cloud WAF Security Dashboard Degradation
Started: May 11, 6:32 AM
monitoring
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.
May 11, 7:26 AM
investigating
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.
May 11, 7:22 AM
investigating
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.
May 11, 6:56 AM
investigating
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 ...
May 11, 6:32 AM
[INC-1030] Ashburn, VA (IAD) Data Center Issue
Started: May 11, 12:47 AM
monitoring
The Ashburn, VA (IAD) PoP is now online. Teams will continue to monitor closely to ensure service stability.
May 11, 12:39 PM
monitoring
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.
May 11, 12:29 PM
monitoring
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.
May 11, 12:03 PM
monitoring
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.
May 11, 10:44 AM
monitoring
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.
May 11, 7:51 AM
monitoring
Technical teams have performed remedial actions and still monitoring the results.
May 11, 6:47 AM
monitoring
We are continuing to monitor for any further issues.
May 11, 5:46 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 11, 4:43 AM
identified
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.
May 11, 3:47 AM
identified
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.
May 11, 2:48 AM
investigating
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.
May 11, 2:15 AM
investigating
Technical teams are continuing to investigate. The next Status Update on this Incident will be provided no later than 02:17 UTC.
May 11, 1:43 AM
investigating
We are continuing to investigate. The next Status Update on this Incident will be provided no later than 01:47 UTC.
May 11, 1:25 AM
investigating
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.
May 11, 12:47 AM
[INC-1028]Third-Party Network Issue Impacting CWAF and DDoS Protection Services
Started: May 10, 1:35 PM
monitoring
We are continuing to monitor for any further issues.
May 10, 3:02 PM
monitoring
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.
May 10, 2:54 PM
investigating
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.
May 10, 1:35 PM
[INC-1027] Issues with the Imperva Management Portal
Started: May 10, 12:10 PM
monitoring
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.
May 10, 1:01 PM
identified
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.
May 10, 12:36 PM
investigating
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.
May 10, 12:24 PM
investigating
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 u...
May 10, 12:10 PM
[INC -1026] Issue in FP on browser classification
Started: May 8, 7:37 PM
monitoring
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 pot...
May 8, 9:01 PM
identified
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...
May 8, 8:16 PM
identified
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 pot...
May 8, 7:42 PM
identified
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 r...
May 8, 7:37 PM
[INC-1024] Imperva Management Portal Dashboard Issue
Started: May 8, 2:57 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 8, 5:37 AM
identified
The issue has been identified and a fix is being implemented.
May 8, 5:19 AM
investigating
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.
May 8, 4:26 AM
investigating
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.
May 8, 3:57 AM
investigating
We are continuing to investigate. The next Status Update on this Incident will be provided no later than 3:58 UTC.
May 8, 3:36 AM
investigating
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 avai...
May 8, 2:57 AM
[INC-1022] Issue with Cloud WAF Protected Websites
Started: May 6, 11:36 AM
monitoring
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.
May 6, 2:04 PM
investigating
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.
May 6, 1:43 PM
investigating
We are continuing to actively investigate this issue.
The next Status Update on this Incident will be provided no later than 13:39 UTC.
May 6, 1:10 PM
investigating
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.
May 6, 12:41 PM
identified
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.
May 6, 12:25 PM
identified
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.
May 6, 11:53 AM
investigating
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...
May 6, 11:36 AM
[INC-1021] Imperva Management Portal Cloud WAF Dashboard Issue
Started: May 3, 10:48 AM
monitoring
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 affecte...
May 3, 3:28 PM
identified
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 availabili...
May 3, 3:06 PM
identified
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...
May 3, 2:33 PM
identified
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
May 3, 2:03 PM
identified
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...
May 3, 1:30 PM
identified
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.
May 3, 1:02 PM
identified
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 att...
May 3, 12:31 PM
identified
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 t...
May 3, 11:57 AM
investigating
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 pot...
May 3, 11:49 AM
identified
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.
...
May 3, 11:18 AM
investigating
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 communica...
May 3, 10:48 AM
April 2026
[INC-1019] Imperva Management Portal Configuration Changes Issue
Started: Apr 27, 11:04 AM
monitoring
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 eve...
Apr 27, 11:14 AM
investigating
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.
Apr 27, 11:04 AM
[INC-1018] Imperva Management Portal Configuration Changes Issue
Started: Apr 24, 2:43 PM
monitoring
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 eve...
Apr 25, 12:02 AM
identified
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 detec...
Apr 24, 11:47 PM
investigating
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 ...
Apr 24, 10:30 PM
investigating
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 po...
Apr 24, 7:07 PM
investigating
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 upda...
Apr 24, 6:06 PM
investigating
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 upda...
Apr 24, 5:05 PM
investigating
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 affect...
Apr 24, 4:35 PM
investigating
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 aff...
Apr 24, 4:00 PM
investigating
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.
Apr 24, 3:24 PM
investigating
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.
Apr 24, 2:43 PM
[INC-1015] Santiago, Chile (STC) Data Center Issue
Started: Apr 21, 11:21 PM
monitoring
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.
Apr 21, 11:34 PM
investigating
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.
Apr 21, 11:21 PM
[INC-1011] Imperva API Issue
Started: Apr 13, 3:47 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 13, 4:59 AM
identified
The issue has been identified and a fix is being implemented.
Apr 13, 4:53 AM
investigating
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.
Apr 13, 4:47 AM
investigating
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.
Apr 13, 4:18 AM
investigating
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 reg...
Apr 13, 3:47 AM
[INC-1009] Imperva Management Portal Cloud WAF Dashboard Issue
Started: Apr 9, 7:39 PM
identified
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.
Apr 9, 11:17 PM
identified
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.
Apr 9, 10:57 PM
identified
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.
Apr 9, 10:20 PM
identified
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.
Apr 9, 9:50 PM
identified
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.
Apr 9, 9:20 PM
identified
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...
Apr 9, 8:49 PM
investigating
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. I...
Apr 9, 8:36 PM
investigating
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. I...
Apr 9, 8:06 PM
investigating
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 ...
Apr 9, 7:39 PM
[INC-1008] Advanced Bot Protection Issue
Started: Apr 9, 7:49 AM
monitoring
Services remain stable. Monitoring has been in progress and will continue for an extended period to ensure sustained stability and normal operation.
Apr 9, 9:37 PM
monitoring
The phased global rollout has been successfully completed. Systems are stable, and monitoring is ongoing to ensure continued normal operation.
Apr 9, 7:12 PM
identified
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.
Apr 9, 6:50 PM
identified
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.
Apr 9, 5:50 PM
identified
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...
Apr 9, 4:50 PM
identified
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...
Apr 9, 3:51 PM
identified
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...
Apr 9, 2:50 PM
identified
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 attri...
Apr 9, 1:51 PM
identified
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 impact...
Apr 9, 1:20 PM
identified
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 impact...
Apr 9, 12:50 PM
identified
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 impact...
Apr 9, 12:20 PM
identified
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 af...
Apr 9, 11:50 AM
identified
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 af...
Apr 9, 11:19 AM
identified
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 avai...
Apr 9, 10:45 AM
investigating
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.
Apr 9, 10:26 AM
investigating
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 aff...
Apr 9, 9:56 AM
investigating
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...
Apr 9, 9:26 AM
investigating
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 se...
Apr 9, 8:55 AM
investigating
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 detec...
Apr 9, 7:49 AM
[INC-1004] Potential CWAF issue on multiple Data Center
Started: Apr 5, 2:02 PM
monitoring
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.
Apr 5, 2:39 PM
investigating
Technical teams are investigating a potential CWAF issue in the (DFW, EWR, IAD, LCY, NYC, PAR) Data Center . Further updates to follow.
Apr 5, 2:02 PM
March 2026
[INC-1002] Johannesburg, South Africa (QRA) Data Center Issue
Started: Mar 27, 12:23 PM
monitoring
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 af...
Mar 27, 12:32 PM
investigating
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.
Mar 27, 12:23 PM
[INC-1001] Imperva GRE Performance Dashboard Issue across Multiple Data Center
Started: Mar 27, 11:17 AM
monitoring
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 s...
Mar 27, 2:02 PM
identified
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 up...
Mar 27, 1:56 PM
investigating
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 ...
Mar 27, 1:06 PM
investigating
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 ...
Mar 27, 12:28 PM
investigating
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 availabilit...
Mar 27, 11:17 AM
[INC-997] New York 2, NY (EWR) Data Center Issue
Started: Mar 21, 6:00 AM
monitoring
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 im...
Mar 21, 9:01 AM
identified
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.
Mar 21, 6:44 AM
identified
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 serv...
Mar 21, 6:07 AM
investigating
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.
Mar 21, 6:00 AM
[INC-996] DUS traffic degradation
Started: Mar 20, 8:38 PM
monitoring
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 im...
Mar 21, 2:35 AM
identified
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.
Mar 20, 9:16 PM
identified
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 serv...
Mar 20, 9:00 PM
investigating
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.
Mar 20, 8:38 PM
[INC-994] Issue with Imperva Managed Certificates
Started: Mar 15, 5:37 AM
monitoring
We are observing signs of recovery, and certificate issuance is beginning to function again. Our teams are currently validating system stability and monitoring the process closely.
Mar 15, 3:38 PM
identified
We are continuing to work with our certificate authority provider to restore certificate issuance functionality. Existing certificates and active services remain unaffected.
Further updates will be shared as more information becomes available.
Mar 15, 1:08 PM
identified
We are continuing to work closely with our certificate authority provider to resolve the issue affecting certificate issuance. Efforts are ongoing to restore normal functionality as quickly as possible.
We will provide further updates as additional information becomes available.
Mar 15, 10:14 AM
identified
We are continuing to work with our certificate authority provider to resolve the issue affecting the ability to order or issue new certificates. Remediation efforts are currently in progress.
Existing certificates and active services remain unaffected. Further updates will be provided as more information becomes available.
Mar 15, 8:05 AM
identified
Our engineering team is actively working with the third-party certificate authority provider to resolve the issue affecting the issuance of new certificates.
We will continue to provide updates as progress is made toward restoring normal certificate ordering and issuance functionality.
Mar 15, 6:22 AM
investigating
We are currently experiencing an issue with the certificate issuance process with our upstream certificate authority provider. As a result, ordering or issuing new certificates is temporarily unavailable at this time.
This issue impacts all certificates managed through Imperva that require new issuance. Existing certificates and active services remain unaffected.
Our engineering team is actively working with the relevant provider to investigate and resolve the issue as quickly as possible. Fu...
Mar 15, 5:37 AM