Our teams have successfully implemented mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. The observed impact has been mitigated, and services are operating as expected at this time.
We are continuing to closely monitor the environment to ensure ongoing stability and confirm the effectiveness of the mitigation.
The next update on the issue will be shared no later than 01:30 UTC.
identified
Our teams continue to work on implementing mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use.
Efforts remain focused on reducing customer impact and restoring expected behavior. We will provide additional updates as progress is made.
The next update on the issue will be shared no later than 01:00 UTC.
investigating
We have identified the source of the issue affecting a subset of customers, resulting in SIEM logs being received from IP addresses that are no longer expected to be in use.
Our teams are actively implementing mitigation measures to reduce customer impact and restore expected behavior. We will provide further updates as they become available.
The next update on the issue will be shared no later than 00:30 UTC.
investigating
We are investigating an issue where some customers may receive SIEM logs from IP addresses that are no longer expected to be in use.
Our teams are actively investigating the issue and working to identify the cause.
We will provide further updates as more information becomes available.
[INC-1135] Service Degradation Causing Intermittent DNS Resolution Issues
The team has completed the mitigation, and the affected services have been validated to be operating as expected.
We will continue to closely monitor the service to ensure the fix remains effective and services remains stable.
identified
Mitigation and validation efforts remain ongoing. The team continues to apply the targeted fix to the remaining affected systems while closely monitoring the service and validating recovery.
The next update on the issue will be shared no later than 22:05 UTC.
identified
Mitigation and validation efforts are continuing. The team is closely monitoring the service while applying the targeted fix across the remaining affected systems and validating recovery.
The next update on the issue will be shared no later than 21:25 UTC.
identified
Mitigation efforts are continuing. We are seeing recovery as the targeted fix is progressively applied to the affected services.
The next update on the issue will be shared no later than 20:55 UTC.
identified
The issue has been identified, and our teams have confirmed the cause of the intermittent DNS resolution failures.
The team is currently applying the mitigation in a controlled manner across the affected services.
The issue remains intermittent and limited in scope.
The next update on the issue will be shared no later that 20:20 UTC.
investigating
We continue to investigate intermittent DNS resolution issues that may affect a small number of requests.
The issue is highly intermittent and remains limited in scope. Our teams are actively investigating the issue and working to identify the cause and ensure consistent DNS resolution.
The next update on this issue will be shared no later than 20:10 UTC.
investigating
We are currently investigating an issue that may cause intermittent DNS resolution failures for some customers.
Our teams are actively investigating the issue and working to identify the cause and restore consistent DNS resolution.
We will provide further updates as more information becomes available.
[INC-1134] Degradation of performance in Imperva Management Console
The issue affecting the Imperva Management Console (MY) has been resolved, and service has been restored.
Customers should now be able to access and use the console normally. Our team will continue to closely monitor the service to ensure stability.
The next update will be no later than 10:30 UTC
investigating
We are investigating an issue affecting the performance of the Imperva Management Console (MY). Customers may encounter elevated latency, login failures, or degraded console performance.
Our engineering teams are engaged and investigating the issue with high priority. We will continue to provide updates as our investigation progresses.
The next update will not be later than 10:15 UTC.
The issue affecting user management and preventing new user invitations on the My Management platform has been resolved. The relevant teams have completed the required remediation, and user management functionality has been restored.
The platform is currently being monitored closely to confirm continued stability.
identified
The issue affecting new user invitations remains under investigation, with the relevant teams continuing to work towards a resolution.
Access for existing users to the My Management platform has been restored. The technical teams have completed the required remedial actions, and the platform is currently being monitored closely to confirm stability.
We will provide further updates as more information becomes available.
identified
The relevant teams continue to actively investigate the issue affecting new user invitations and are working towards implementing a resolution.
Separately, for the issue affecting some customers who experienced difficulties accessing or loading the My Management platform, our technical teams have identified the issue and implemented mitigation measures to restore service. Management Portal functionality is currently being validated, and we continue to monitor the environment closely to confirm stability.
We will provide further updates as more information becomes available.
identified
We have identified a potential cause for the issue preventing new user invitations on the My Management platform. The relevant teams are actively investigating and working towards implementing a resolution.
Separately, the investigation into the issue affecting some customers who may experience difficulties accessing or loading the My Management platform continues. The relevant teams remain engaged in identifying the cause and restoring normal functionality.
We will provide further updates as more information becomes available.
investigating
Our investigation into the issue preventing new user invitations on the My Management platform is continuing. The teams have identified a potential contributing factor related to the user management functionality and are continuing to investigate to confirm the root cause and determine the appropriate resolution.
Separately, we continue to investigate the issue affecting some customers who may experience difficulties accessing or loading the My Management platform. The relevant teams remain actively engaged in identifying the cause and working towards restoring normal functionality.
The next update on the issue will be provided no later than 19:05 UTC.
investigating
Our investigation into the issue preventing new user invitations on the My Management platform is continuing. The relevant teams remain engaged in identifying the root cause and working towards a resolution.
Separately, we continue to investigate the issue affecting some customers who may experience difficulties accessing or loading the My Management platform. The relevant teams are actively working to identify the cause and restore normal functionality.
Next update on the issue will be shared no later than 18:35 UTC
investigating
Our investigation into the issue preventing new user invitations on the My Management platform is ongoing. The relevant teams continue to work on identifying the root cause and implementing a resolution.
Additionally, due to a separate issue, some customers may experience difficulties accessing or loading the My Management platform. Our teams are actively investigating this issue as well and working to identify the root cause.
Next update on the issue will be shared no later than 18:00 UTC.
investigating
We are continuing to investigate an issue preventing new user invitations on the My Management platform.
Additionally, due to a separate issue, some customers may experience difficulties accessing or loading the My Management platform. Our teams are actively investigating this issue as well and working to identify the root cause.
Next update on the issue will be shared no later that 17:27 UTC.
investigating
We are continuing to investigate the issue preventing new user invitations on the My Management platform. Existing users can continue using the platform as normal. We will provide another update as more information becomes available.
Next update: no later than 16:30 UTC.
investigating
We are continuing to investigate the issue preventing new user invitations on the My Management platform. Existing users can continue using the platform as normal. We will provide another update as more information becomes available.
Next update: no later than 16:09 UTC.
investigating
We continue to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems and working to identify the root cause.
Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available.
Next update: no later than 15:44 UTC.
investigating
We continue to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems and working to identify the root cause. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available.
Next update: no later than 15:20 UTC.
investigating
We are continuing to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems to identify the root cause and determine the appropriate resolution. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available.
Next update: no later than 14:58 UTC.
investigating
We are continuing to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems to identify the root cause and determine the appropriate resolution. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available.
Next update: no later than 14:35 UTC.
investigating
We continue to actively investigate the issue affecting the ability to invite new users to the My Management platform. Our teams are reviewing the relevant systems and working to identify the root cause. Existing users can continue to access and use the platform as normal. We will provide another update as soon as more information becomes available.
Next update: no later than 14:15 UTC.
investigating
We continue to investigate an issue affecting the creation of new users in the Imperva Management Platform.
At this time, we are assessing whether the issue is intermittent rather than limited to a specific subset of customers. Our teams remain actively engaged in the investigation and are working to better understand the scope and underlying cause of the issue.
We apologise for the inconvenience and will provide further updates as soon as additional information becomes available.
Next update: no later than 13:55 UTC.
investigating
We are continuing to investigate an issue affecting the creation of new users in the Imperva Management Platform. The impact currently appears to be limited to a subset of customers.
Our teams are actively working to identify the cause and restore normal functionality. We apologise for the inconvenience and will provide further updates as soon as additional information becomes available.
Next update: no later than 13:35.
investigating
We are currently investigating an issue affecting the ability to invite new users to the Imperva Management platform. Existing users may continue to access and use the platform as normal. Our team is actively working to identify the cause and restore full functionality. We will provide further updates as more information becomes available. The next update will not be later than 13:15 UTC
[ INC - 1129 ]Service Degradation Impacting Login to the Imperva Management Portal
The issues affecting Management Portal login and SSL Certificate Management have been remediated, and all functionality is currently operating as expected.
Our technical teams are actively monitoring the environment to confirm service stability and ensure continued normal operation.
The next update will be provided as further information becomes available.
identified
Our technical teams continue to work toward fully restoring SSL Certificate Management functionality.
Management Portal login and other core functionality are operating as expected. The remaining impact is limited to SSL Certificate Management. Customer websites and traffic remain fully covered by SSL and protected at this time.
Further updates will be provided as we continue to work toward full remediation.
identified
Our technical teams have identified the issue and are actively working toward full service restoration.
At this time, login access to the Management Portal has been restored. However, SSL Certificate Management functionality remains unavailable, and the team is working to apply a fix and restore this functionality.
Customer websites and traffic remain fully covered by SSL and protected at this time.
investigating
Login to the Management Portal has been restored, and users are currently able to access the portal. Most core functionality is available; however, SSL Certificate Management functionality remains unavailable while our technical teams continue to investigate and work toward full service restoration.
Customer websites and traffic remain fully protected at this time.
Next update on this incident will be shared no later than 19:55 UTC.
investigating
Our technical teams continue to investigate the issue affecting access to the Management Portal. Following adjustments to the affected services, we are seeing signs of improvement, including successful login attempts.
The teams are continuing to investigate the underlying root cause and work toward a permanent resolution. Customer websites and traffic remain fully protected at this time.
Further updates will be provided as the investigation progresses.
investigating
Our technical teams continue to actively investigate an issue affecting the ability to log in to the Management Portal.
Customer sites remain fully protected at this time, with no impact to their protection services.
Next update on the incident will be shared no later than 18:46 UTC.
investigating
Our technical teams are actively investigating an issue affecting access to the Management Portal. The teams are working to identify the cause and restore services. Next update on the incident will be shared no later than 18:32 UTC.
investigating
We have discovered a service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow.
Next Update on this incident will be shared no later than 18:00 UTC
Traffic has been restored to the Madrid, Spain (MAD) Data Center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.
identified
The issue has been identified and a fix is being implemented.
investigating
We have identified an issue in the Madrid, Spain 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.
_ _
Further updates will be shared as more information becomes available.
[INC-1120 ] Service Degradation affecting a subset of customers in North America region
Chicago 2, IL (CHI)Detroit, MI (DET)Houston, TX (HOU)Los Angeles, CA (SNA)Miami, FL (FLL)Montreal, Canada (YUL)New York 2, NY (EWR)
monitoring
We have rerouted traffic away from the affected carrier in the impacted PoPs, mitigating customer impact. We will continue to closely monitor the environment to ensure ongoing service stability.
investigating
Imperva has been alerted to the fact that there have been two major fiber cuts in North America. These fiber cuts are within the network of a major upstream carrier. A subset of customer traffic coming to or going from the Imperva network may transit this infrastructure and as a result of this issue, customers may experience connectivity issues, increased latency, or service degradation.
We will provide further updates as more information becomes available.
The next update will be before 20...
[INC-1118] Rio de Janeiro, Brazil (RIO) Data Center Issue
Technical team has successfully activated the PoP, and traffic has been restored to the Janeiro, Brazil (RIO) Data Center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.
identified
The issue has been identified and a fix is being implemented.
investigating
The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP.
The next update will be provided no later than 07:30 UTC.
investigating
Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency.
Further updates will be shared as more information becomes available.
investigating
The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect.
Further updates will be shared as more information becomes available.
investigating
We have identified an issue in the Rio de Janeiro, Brazi 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.
Further updates will be shared as more information becomes available.
We have implemented mitigation measures and are observing recovery in email notification delivery. Current monitoring indicates notification volumes have returned to expected levels, and email notifications are being processed successfully.
We will continue to monitor the service closely to ensure recovery is sustained and to identify any residual impact.
identified
Our investigation into the email notification degradation is ongoing. We have identified the affected notification flow and are actively working to restore normal delivery rates. While mitigation efforts continue, some customers may still experience delays or failures in receiving email notifications.
We will continue to monitor the effectiveness of the mitigation efforts and provide further updates as additional information becomes available.
The next update will be provided before 10:35 UTC.
identified
We have identified a potential source of the issue affecting email notifications and are actively validating our findings. Our teams are working to implement and verify corrective actions while closely monitoring system behaviour. Customers may continue to experience delays or failures in receiving notification and confirmation emails during this period.
We will continue to monitor the effectiveness of the mitigation efforts and provide further updates as additional information becomes avail...
investigating
Our teams continue to actively investigate the issue affecting email notifications. We are working to identify the underlying cause and restore normal notification delivery as quickly as possible. Customers may continue to experience delays or failures in receiving notification and confirmation emails during this time.
We will provide our next update no later than 09:30 UTC
investigating
We are currently investigating an issue affecting email notifications. Customers may experience delays or failures in receiving notification and confirmation emails. Our engineering teams are actively working to identify the cause and restore normal notification delivery as quickly as possible. We will provide additional updates as more information becomes available. The next update will be before 09:05 UTC.
[INC-1106] Elevated Latency for a Subset of Origin Fetch Traffic in Ashburn, VA (WDC)
The third-party CDN provider has implemented a fix to address the routing issue. Based on our current observations and log data, traffic is routing as expected, and origin fetch traffic is operating normally, with latency levels within expected ranges.
We are continuing to closely monitor the service to ensure routing remains stable and customer traffic continues to operate normally.
identified
We are currently seeing an unexpected delay from the third-party CDN provider, and there is a possibility that the timeline for the complete remediation may be extended. We continue to actively engage with and push the provider while they work on the permanent fix.
In the meantime, if any customer requires urgent assistance, a workaround can be implemented on a case-by-case basis for impacted websites. Further updates will be shared as more information becomes available.
identified
We have confirmed a solution which mitigates the sub-optimal routing and can be implemented by request on a per-customer basis for impacted websites while we continue to await the permanent fix by the third-party CDN provider.
investigating
We have confirmed with the third-party CDN provider that they have begun to work on a configuration update which will correct the sub-optimal routing, with an ETA of up to 2 weeks before it is globally deployed. In the meantime, we continue to explore mitigation steps which we may be able to implement on a per-customer basis for impacted websites.
investigating
We are actively exploring potential mitigation options to address the sub-optimal routing and reduce the impact on affected origin fetch traffic. In parallel, we are working with the third-party provider to address the underlying geolocation issue. We will provide further updates as more information becomes available.
investigating
We have identified a condition where a subset of customer origin fetch traffic from our proxy servers in the WDC PoP is experiencing sub-optimal routing. In these cases, origin fetch is getting routed to specific third-party CDN networks in the APAC region instead of Eastern US, which is resulting in increased latency for origin fetch, and ultimately reduced performance in website access. While we are working with the third-party CDN on to correct their Geolocation routing information, we are...
Legacy Incident Archive
46 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
[INC-1076] Querétaro, MX (QRO) Data Center Issue
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Technical team has successfully activated the PoP, and traffic has been restored to the Querétaro, MX (QRO) data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.
The next Status Update on this Incident will be provided no later than 8:13 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. I...
identified
The technical teams have identified an issue impacting the Querétaro, Mexico (QRO) data center. To maintain service stability, the PoP will remain in bypass mode as a precaution and is scheduled to be restored during off-peak hours. Customer traffic continues to be served without interruption through an alternate PoP.
Engineering teams are actively investigating the issue and working toward a resolution. The next status update will be provided no later than 07:00 UTC.
The status updates ar...
identified
The technical teams have identified an issue affecting the Querétaro, MX (QRO) 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. The next Status Update on this Incident will be provided no later than 05:00 UTC.
The status updates are an integral part of proa...
identified
The technical teams have identified an issue affecting the Querétaro, MX (QRO) 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. The next Status Update on this Incident will be provided no later than 05:00 UTC.
The status updates are an integral part of proa...
investigating
Technical teams are investigating a potential issue in the Querétaro, MX (QRO) data center. The next Status Update on this Incident will be provided no later than 10:11 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 disrup...
June 2026
[INC-1066] Increased Latency for a portion of Imperva Cloud WAF Protected Sites
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 15 minutes.
investigating
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.
[INC-1065 ] Imperva Management Portal Login Issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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
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.
identified
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.
investigating
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.
investigating
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
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.
[INC-1062] Sao Paulo 2 Data Center Issue
majorSource not attested
Last archived state: resolved
View archived record details
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. 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 serv...
investigating
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 event...
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. 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 a...
[INC-1059] Latency Issue on the Management Console
minorSource not attested
Last archived state: resolved
View archived record details
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. 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 o...
identified
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 at...
investigating
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.
May 2026
[INC-1054] Connectivity issue in VAN POP.
minorSource not attested
Last archived state: resolved
View archived record details
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 next update will be provided no later than 11:18 UTC.
identified
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.
identified
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
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
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
We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center.
The next update will be provided no later than 19:38 UTC.
[INC-1053] Connectivity issue in EWR
minorSource not attested
Last archived state: resolved
View archived record details
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 next update will be provided no later than 12:00 UTC.
identified
The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP.
The next update will be provided no later than 10:46 UTC.
investigating
Investigation is ongoing. Technical teams continue to analyze the issue and validate findings. Customer traffic continues to be served normally through an alternate PoP.
Next update will be shared no later then 10:18 UTC.
investigating
The investigation is ongoing, and technical teams continue to actively troubleshoot and analyze the issue to determine the underlying cause.
Next update will be shared no later then 09:42 UTC.
investigating
During monitoring, the team identified some abnormalities in the network. The engineering team is currently re-investigating the issue, and traffic is being re-routed to an alternate data center.
Next update will be shared no later then 09:11 UTC.
monitoring
A fix has been implemented, and customer traffic continues to be served normally through the New York 2, NY (EWR) PoP.
We will continue to monitor the situation to ensure that service remains 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 disruptio...
identified
The technical teams have identified an issue affecting the New York 2, NY (EWR) 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.
identified
As a precautionary measure, the New York 2, NY (EWR) 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
Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center.
The next update will be provided no later than 20:00 UTC.
identified
We have identified intermittent connectivity issues affecting the New York 2, NY (EWR) 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 19:27 UTC.
identified
We have identified connectivity issues affecting our New York 2, NY (EWR) data center. Traffic is currently being re-routed to an alternate data center to minimize customer impact.
The next update will be provided no later than 18:53 UTC.
identified
We have identified connectivity issues in our New York 2, NY (EWR). traffic is being re-routed to an alternate data-center.
Next update will be shared no later then 18:37.
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.
monitoring
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.
investigating
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.
investigating
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 ma...
[INC-1049] Issue with creation of the site certificates.
majorSource not attested
Last archived state: resolved
View archived record details
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.
investigating
Remediation efforts are ongoing and teams are actively working to stabilize the services.
The next update will be communicated at 00:10 UTC.
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...
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.
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.
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...
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.
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...
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...
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...
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...
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...
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.
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.
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.
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.
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.
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.
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.
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.
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.
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...
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.
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.
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...
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.
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.
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...
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...
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
...
