A fix has been implemented and we are monitoring the results.
identified
Mitigation efforts are ongoing. Our teams have completed additional configuration changes and continue working to restore normal service. Further updates will be provided as information becomes available.
identified
Imperva teams continue working to mitigate the issue and restore normal service. We are currently implementing and validating mitigation actions. Further updates will be provided as information becomes available.
identified
Efforts to mitigate the issue are still ongoing. Our teams continue working to restore normal service. Further updates will be provided as information becomes available.
identified
Efforts into mitigating the issue are still ongoing. Further updates will be provided as information becomes available. The next update will be before 11:15 UTC
identified
Our internal teams have identified the service degradation that is affecting the newly onboarded sites. We are currently working to remediate the incident and further updates will be provided as information becomes available.
The next update will be before 09:45 UTC
investigating
We are investigating a service degradation affecting resolution for some newly onboarded sites. Our teams are working to determine the cause and will provide updates as more information becomes available. The next update will be provided by 09:15 UTC.
[INC-1160] Degradation of Imperva Generated Certificate Issuance
The issue was identified as a degradation affecting a third-party service. The issue should now be resolved, and certificate issuance is operating as expected. We are closely monitoring the service to ensure continued stability. The next update will be no later than 17:00 UTC
identified
We have identified the issue affecting the onboarding of new WAF sites and the issuance of new certificates. Our teams are actively working to restore normal service. The next update will be before 15:00 UTC.
identified
We are investigating an issue affecting Imperva-generated certificate issuance. Customers may experience issues when onboarding new sites using an Imperva-generated certificate and renewing existing certificates. Customer assets and sites remain protected during this time. The next update will be before 14:00 UTC.
[INC-1158] Service Degradation of Dallas, TX (DAL) PoP
The Dallas, TX (DAL) PoP has been successfully activated and returned to service. Our technical teams will continue to closely monitor the PoP to ensure stability and performance.
identified
A fix has been applied to address the connectivity issue affecting the DAL (Dallas) PoP. Traffic continues to be routed through an alternate PoP while our teams monitor service stability.
The DAL PoP is scheduled to return to service during a low-traffic period, around 09:00 UTC on Saturday, 10 October.
We will provide a further update once the PoP is back in service.
identified
The issue affecting the DAL PoP has been identified, and our technical teams are actively working on a fix. Traffic remains rerouted through an alternate PoP in the region.
The next update will be provided no later than 00:20 UTC on Saturday, 10 October.
investigating
We are continuing to investigate this issue.
investigating
Investigation into the cause of the service degradation affecting the DAL PoP is still ongoing. Traffic remains rerouted through an alternate PoP in the region. Further updates will be provided as information becomes available.
investigating
Investigation into the cause of the service degradation affecting the DAL PoP is still ongoing. Traffic remains rerouted through an alternate PoP in the region. Further updates will be provided as information becomes available.
investigating
We have discovered a service degradation that is affecting the DAL POP, which may have resulted in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Traffic is currently being rerouted through an alternate PoP in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Investigation into the cause of the service degradation is currently ongoing. Further updates will be provided as information becomes available.
[INC-1152] IPv6 connectivity degradation across multiple PoPs
Atlanta, GA (ATL)Detroit, MI (DET)Singapore (XSP)Tokyo, Japan (NRT)Warsaw, Poland (WAR)
monitoring
The Warsaw (WAR) PoP has been successfully activated and is now operational.
Network traffic across all core Points of Presence—including Singapore (XSP), Atlanta (ATL), Detroit (DET), Tokyo (NRT), and Warsaw (WAR)—remains stable and fully operational following our remediation efforts.
Our engineering teams will continue to closely monitor system performance.
monitoring
Network traffic across all core points of presence—including Singapore (XSP), Atlanta (ATL), Detroit (DET), and Tokyo (NRT)—remains stable and fully operational following our earlier remediation efforts.
Our engineering teams are keeping a close watch on system performance, and we will share a follow-up update as soon as the Warsaw (WAR) PoP is successfully brought back online.
monitoring
Service for Singapore (XSP), Atlanta (ATL), Detroit (DET), and Tokyo (NRT) has been fully restored and is operating normally.
Traffic for Warsaw (WAR) remains bypassed while our engineering teams complete final validation and plan to bring the PoP back online during scheduled off-peak maintenance hours. . We are actively monitoring the system, and the next update will be provided by 13:00 UTC
investigating
We are observing IPv6 connectivity issues affecting Detroit, MI (DET).
Our teams are actively investigating the issue and working to implement remediation. The next update will be provided by 13:15 UTC.
investigating
Our investigation is ongoing, and our teams are actively working to identify the cause and implement the appropriate remediation.
The next update will be provided by 12:05 UTC.
investigating
We are observing a recurrence of IPv6 connectivity issues affecting Singapore (XSP) and Atlanta (ATL). Service in Tokyo (NRT) remains fully operational.
Additionally, IPv4 issues were observed for Warsaw (WAR). Traffic for WAR has been bypassed to restore service stability while our engineering teams actively investigate the root cause for XSP and the underlying issue at WAR.
The next update will be provided by 11:30am UTC
investigating
We are observing a recurrence of the IPv6 connectivity issues affecting Singapore (XSP). Service in Tokyo (NRT) and Atlanta (ATL) remains fully operational.
Our engineering team is actively investigating the cause of this regression and working to restore stability to XSP, as well as resolving the ongoing impact in Warsaw (WAR). The next update will be provided by 11:00 UTC
investigating
We are continuing to address the IPv6 connectivity issue across our network. Service for Singapore (XSP), Tokyo (NRT), and Atlanta (ATL) is operating normally.
Our teams are actively investigating the root cause and working to restore full connectivity for the remaining affected locations (WAR). The next update will be provided by 10:30 UTC.
investigating
We are continuing to address the IPv6 connectivity issue across our network. Service for Atlanta, GA (ATL) and Tokyo, Japan (NRT) is operating normally.
Our teams are actively investigating the root cause and working on a permanent resolution. The next update will be provided by 10:00 UTC.
investigating
Our investigation remains ongoing, and our teams are actively working to identify the cause and implement the appropriate remediation.
The next update will be provided no later than 09:40 UTC.
investigating
We are investigating an issue affecting network connectivity for customers using IPv6 addresses at multiple locations. Customers using IPv4 connectivity are not impacted.
Our teams are actively investigating the issue and working to identify the appropriate remediation. We will provide further updates as more information becomes available.
[INC-1149] Service degradation of Frankfurt, Germany (HHN) PoP
The connectivity issue has been identified and resolved by our technical teams, and the system will continue to be monitored for stability.
The Frankfurt, Germany (HHN) PoP will be returned to service during the low traffic period for this PoP. This is scheduled for around 02:00 UTC Friday 2nd October.
A further update will be posted once this process has been completed.
investigating
We continue to investigate the issue affecting the PoP. Traffic remains routed through alternate locations in the region.
The team is performing additional validation and testing before returning the PoP to service. We will continue to monitor the situation closely and provide further updates as more information becomes available.
investigating
We continue to investigate the connectivity issue affecting the Frankfurt, Germany (HHN) PoP. Traffic remains rerouted through alternate PoPs while the investigation continues.
Current monitoring indicates that services remain stable and traffic is being successfully handled through the alternate locations. The HHN PoP will be returned to service once the investigation and validation activities are complete.
investigating
We continue to investigate the connectivity issue affecting the Frankfurt, Germany (HHN) PoP. Traffic remains rerouted through alternate PoPs as a mitigation measure while investigations continue.
Current monitoring indicates network services remain stable and traffic is being successfully handled through alternate locations.
The HHN PoP will be returned to service once investigation and validation activities have been completed. We will continue to provide updates as more information becomes available.
investigating
We have identified a connectivity issue affecting the Frankfurt, Germany (HHN) PoP. As a mitigation measure, traffic is being rerouted through alternate locations to reduce customer impact while our teams investigate. Some customers may experience intermittent latency or connectivity degradation. We are actively working to resolve the issue and will provide updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
investigating
We have identified a service degradation affecting the Imperva API. As a result, some customers attempting to download SIEM logs via the API may receive HTTP 502 errors. Our teams are actively investigating the issue and working to restore normal service as quickly as possible.
All customer websites remain fully protected at this time. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
September 2026
[INC-1146] Service degradation of MAD (Madrid) PoP
The MAD (Madrid) PoP has been successfully activated and returned to service. Our technical teams will continue to closely monitor the PoP to ensure stability and performance.
identified
The team is preparing to begin the PoP activation shortly. We will closely monitor the PoP throughout the activation and provide further updates as the process progresses.
The next update on this incident will be provided no later than 01:00 UTC on 29 September 2026.
identified
The connectivity issue has been identified and resolved by our technical teams, and the system will continue to be monitored for stability.
The MAD (Madrid) PoP will be returned to service during the low traffic period for this PoP. This is scheduled for around 0001UTC Tuesday 29th September.
A further update will be posted once this process has been completed.
investigating
We continue to investigate the connectivity issue affecting the Madrid (MAD) PoP. Traffic remains rerouted through alternate PoPs as a mitigation measure while investigations continue.
Current monitoring indicates network services remain stable and traffic is being successfully handled through alternate locations.
The MAD PoP will be returned to service once investigation and validation activities have been completed. We will continue to provide updates as more information becomes available.
identified
We have identified a connectivity issue affecting the Madrid (MAD) PoP. As a mitigation measure, traffic is being rerouted through alternate locations to reduce customer impact while our teams investigate. Some customers may experience intermittent latency or connectivity degradation. We are actively working to resolve the issue and will provide updates as more information becomes available.
Amsterdam, Netherlands (RTM)Hong Kong (HHK)Dallas, TX (DAL)Denver, CO (DEN)Rio de Janeiro, Brazil (RIO)London 1, UK (LCY)San Jose, CA (SFO)Singapore (XSP)
monitoring
We continue to observe stable operations across the previously affected PoPs, with no further signs of impact at this time.
Engineering teams remain engaged and are closely monitoring the environment while the investigation into the underlying cause continues. We will provide a final update once monitoring activities have been completed.
identified
We have restored traffic flow across all previously affected PoPs, and GRE tunnel connectivity has been re-established. Traffic is currently routing as expected.
While service has stabilized, our engineering teams remain actively engaged in investigating the underlying cause of the issue and monitoring the environment closely. Customers may have experienced increased latency, Error 20 responses, or GRE tunnel connectivity issues during the period of impact.
We will continue to provide updates as our investigation progresses - the next update will be no later than 09:09 UTC
identified
We have identified an issue affecting multiple network locations (PoPs). Customers may experience increased latency, encounter Error 20 responses, and may be impacted by GRE tunnel connectivity issues.
Our engineering teams are actively investigating the issue to determine the full scope, impact, and underlying cause. We are working to restore normal service as quickly as possible and will provide updates as more information becomes available.
monitoring
We have implemented corrective actions and service has returned to normal operation. The affected GRE tunnels have been successfully re-established, and traffic is flowing as expected across the previously impacted locations.
Customers should no longer experience the increased latency or Error 20 responses previously observed. We are continuing to monitor the environment closely to ensure stability.
investigating
We have identified an issue affecting the XSP (Singapore) PoP. Customers may experience increased latency, Error 20 responses, and connectivity impacts related to GRE tunnels.
Our teams are actively investigating the issue and working to determine the scope, impact, and root cause. We will provide further updates as soon as additional information becomes available.
The next update will not be later than 08:10am UTC
Technical teams have performed remedial actions and the Advanced Bot Protection service has been restored. Technical teams will continue monitoring the system. Further updates to follow.
identified
We have identified the source of the issue affecting the Advanced Bot Protection service. Technical teams are working on a mitigation. Further updates to follow.
investigating
Our teams continue to work on implementing mitigation measures to address the issue. Technical teams are still engaged and actively investigating. Customer sites are still fully protected by Advanced Bot Protection at this time.
investigating
We are aware of an ABP issue affecting some users on Google Chrome 153 and above. Other browsers and versions are not currently affected. Customer sites are still fully protected by Advanced Bot Protection at this time. Our team is actively working on a fix. Technical teams are investigating. Further updates to follow.
[INC-1142] Network Connectivity Degradation Across Multiple PoPs Due to an Upstream Provider Issue
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)Seattle, WA (SEA)Toronto, Canada (TOR)Vancouver, Canada (VAN)
monitoring
To maintain service stability, the impacted upstream provider remains bypassed. Our teams continue to closely monitor the environment and are working with the upstream provider to gather further information. Additional updates will be provided as more details become available.
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
One of our upstream providers is currently experiencing a major outage.
We are contacting the provider to gather more information about the issue. As a mitigation, we have rerouted traffic away from the affected carrier at the impacted PoPs, which has mitigated customer impact.
We will continue to closely monitor the environment to ensure ongoing service stability. Further updates will be provided as more information becomes available.
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.
...
