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.
May 2026
[INC -1026] Issue in FP on browser classification
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results. The next Status Update on this Incident will be provided no later than 21:30 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include pot...
identified
The issue has been identified, and remediation efforts are currently underway. The next Status Update on this Incident will be provided no later than 20:45 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update...
identified
The issue has been identified and a fix is being implemented. The next Status Update on this Incident will be provided no later than 20:10 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include pot...
identified
We have discovered a potential issue affecting FP on browser classification. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected r...
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
The technical teams are still working on the recovery for the Imperva Management Portal dashboard issue. The next status update on this incident will be provided no later than 05:28 UTC.
investigating
Technical teams are continuing to work on a fix for the Imperva Management Portal dashboard issue. The next status update on this incident will be provided no later than 04:28 UTC.
investigating
We are continuing to investigate. The next Status Update on this Incident will be provided no later than 3:58 UTC.
investigating
We have discovered a potential service degradation, affecting Imperva Management Portal. The dashboards may not be not displaying the latest data. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 3:28 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect avai...
[INC-1022] Issue with Cloud WAF Protected Websites
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and services have returned to normal. We are continuing to monitor the situation closely to ensure stability.
The next Status Update on this Incident will be provided no later than 15:04 UTC.
investigating
We are actively investigating this issue and continuing our efforts to identify the cause of the issue.
The next Status Update on this Incident will be provided no later than 14:13 UTC.
investigating
We are continuing to actively investigate this issue.
The next Status Update on this Incident will be provided no later than 13:39 UTC.
investigating
Our investigation has determined that the previously suspected cause may be one contributing factor within a broader underlying root-cause pattern than initially identified. We are continuing to investigate and actively working to identify the underlying cause.
The next Status Update on this Incident will be provided no later than 13:11 UTC.
identified
We are continuing to actively work on implementing a fix.
The next Status Update on this Incident will be provided no later than 12:55 UTC.
identified
We have identified the issue, and a fix is currently being implemented.
The next Status Update on this Incident will be provided no later than 12:22 UTC.
investigating
We are investigating a potential issue impacting Cloud WAF Protected Websites. Some websites may fail to load or return errors. Customer domains remain fully protected at this time. Our technical teams are actively working to identify the root cause, and further updates will be shared as more information becomes available.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a...
The incident has been resolved, and all services have returned to normal operating levels. We will continue to monitor the situation closely.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affecte...
identified
The team has resolved the Security Events page issue on the Management Platform; however, Attack Analytics, threat alert emails, and SIEM integrations may still be impacted. The next Status Update on this Incident will be provided no later than 15:36 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availabili...
identified
Technical teams are continuing to work on a fix the issue. The next status update on this incident will be provided no later than 15:03 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected...
identified
Team are actively working to mitigate the issue. The next Status Update on this Incident will be provided no later than 14:33 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region
identified
The teams have identified a component potentially causing the issue. They are currently working to mitigate it. The next Status Update on this Incident will be provided no later than 14:00 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the...
identified
Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 13:30 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
identified
During the course of the investigation our teams found that the issue also affects ABP and Attack Analytics log delivery via SIEM solution in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 13:00 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and att...
identified
During the course of the investigation our teams found that the issue also affects the Attack Analytics and Security log delivery via SIEM solution in the APAC region. The next status update on this incident will be provided no later than 12:27 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of t...
investigating
Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 12:18 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include pot...
identified
We have identified the source of the service degradation affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 11:48 AM UTC. Further updates to follow.
...
investigating
We have discovered a potential service degradation, affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communica...
Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected eve...
investigating
We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 11:34UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected eve...
identified
We have identified the source of the service degradation that is causing delays in the propagation of recent configuration changes in the Imperva Management Portal. An additional 20% of configuration changes have been processed, reducing the overall delay.
The next update will be provided at 00:47 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detec...
investigating
The team is actively investigating the issue and processed approximately 30% of configuration change. The next update will be provided as soon as more information becomes available.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will ...
investigating
We are actively investigating a service degradation affecting the Imperva Management Portal. We will provide the next update as soon as more information becomes available.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include po...
investigating
We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 19:06 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the upda...
investigating
We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 18:05 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the upda...
investigating
The team is actively investigating the service degradation impacting the Imperva Management Portal, with the next update expected at 17:05 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affect...
investigating
The investigation into the service degradation affecting the Imperva Management Portal is ongoing, and the next update is scheduled for 16:30 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any aff...
investigating
We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 03:54UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
investigating
We have discovered a potential issue affecting My Publishing. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
[INC-1015] Santiago, Chile (STC) Data Center Issue
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been successfully implemented, and the issue has been remediated. All services are now operating as expected. We are continuing to closely monitor the environment to ensure stability and prevent any recurrence.
investigating
Technical teams are investigating a potential issue in the Santiago, Chile (STC) Data Center . Further updates to follow.
The next Status Update on this Incident will be provided no later than 23:50 UTC.
[INC-1011] Imperva API Issue
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate the potential service disruption affecting Imperva's API. The next Status Update on this Incident will be provided no later than 5:17 UTC. Further updates to follow.
investigating
We are continuing to investigate the potential service disruption affecting Imperva's API. The next Status Update on this Incident will be provided no later than 04:47 UTC. Further updates to follow.
investigating
We have discovered a potential service disruption affecting Imperva's API. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected reg...
Data visibility has been restored on the Cloud WAF dashboard, and systems are operating as expected. However, a gap remains for the period from yesterday until now. The data is present, but may not be fully visible across all resolutions.
We are actively completing the remaining data processing and backfilling the missing data. New data is being reflected correctly on the dashboard. Full restoration is expected within approximately 10 hours.
identified
The fix is currently being deployed by the technical teams.
The next status update for this incident will be provided no later than 23:25 UTC.
identified
The fix is currently being deployed by the technical teams.
The next status update for this incident will be provided no later than 22:50 UTC.
identified
The fix is currently being deployed by the technical teams.
The next status update for this incident will be provided no later than 22:20 UTC.
identified
We have identified the source of the service degradation impacting the Cloud WAF dashboard, resulting in missing data in the Security Events section. A fix is currently being deployed by the technical teams.
The next status update for this incident will be provided no later than 21:50 UTC.
identified
We have identified the source of the service degradation impacting the Cloud WAF dashboard, resulting in missing data in the Security Events section. Technical teams are actively working on mitigation.
The next status update for this incident will be provided no later than 21:19 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may...
investigating
We continue to investigate the service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected, and our engineering teams are actively working toward resolution.
The next Status Update on this Incident will be provided no later than 21:06 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. I...
investigating
We continue to investigate the service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected, and our engineering teams are actively working toward resolution.
The next Status Update on this Incident will be provided no later than 20:36 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. I...
investigating
We have identified a potential service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected at this time. Technical teams are actively investigating, and further updates will follow.
The next Status Update on this Incident will be provided no later than 20:08 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status ...
[INC-1008] Advanced Bot Protection Issue
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Services remain stable. Monitoring has been in progress and will continue for an extended period to ensure sustained stability and normal operation.
monitoring
The phased global rollout has been successfully completed. Systems are stable, and monitoring is ongoing to ensure continued normal operation.
identified
The phased global rollout is currently underway, with continuous monitoring in place. The next status update will be provided no later than 19:50 UTC.
identified
The phased global deployment is currently in progress. Monitoring is ongoing as we continue with the rollout. The next status update will be provided no later than 18:50 UTC.
identified
We are deploying the fix globally in a phased approach to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 17:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a...
identified
We are deploying the fix globally in a phased approach to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 16:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a...
identified
We are rolling out the fix in a phased manner globally to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 15:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a...
identified
We are rolling out the fix in a phased manner globally to reduce the risk of additional impact to live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 14:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attri...
identified
Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 13:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impact...
identified
Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 13:20 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impact...
identified
Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 12:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impact...
identified
Technical teams are working on a FIX. The next status update on this incident will be provided no later than 12:20 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any af...
identified
Technical teams are working on a FIX. The next status update on this incident will be provided no later than 11:50 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any af...
identified
We have identified an issue in key rotation which is affecting tokens for Advance Bot Protection customers. Technical teams are working on a mitigation. The next status update on this incident will be provided no later than 11:15 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect avai...
investigating
We are actively investigating a potential service disruption impacting Advanced Bot Protection. Engineering teams are engaged and working to determine the cause and contributing factors. The next update will be provided by 11:55 UTC.
investigating
We are continuing to investigate a potential service disruption affecting Advanced Bot Protection. Our technical teams are actively working to identify the cause. The next status update on this incident will be provided no later than 10:25 UTC.Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not aff...
investigating
We are continuing to investigate the potential service disruption affecting Advanced Bot Protection. Our technical teams are actively investigating the set of contributing factors. The next Status Update on this Incident will be provided no later than 09:55 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that...
investigating
We are continuing to investigate the potential service disruption affecting Advanced Bot Protection. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 09:25 UTC. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the se...
investigating
We have discovered a potential service degradation affecting Advance Bot Protection customers. Customer websites are returning browser errors to some end users. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detec...