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.
April 2026
[INC-1004] Potential CWAF issue on multiple Data Center
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue appears to be resolved at this time. We are continuing to monitor in order to ensure that service has returned to normal.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
investigating
Technical teams are investigating a potential CWAF issue in the (DFW, EWR, IAD, LCY, NYC, PAR) Data Center . Further updates to follow.
March 2026
[INC-1002] Johannesburg, South Africa (QRA) Data Center Issue
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and the issue has been mitigated. We are continuing to monitor in order to ensure that service has returned to normal.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any af...
investigating
Technical teams are investigating a potential issue in the Johannesburg, South Africa (QRA) data center. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
[INC-1001] Imperva GRE Performance Dashboard Issue across Multiple Data Center
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Technical teams have performed remedial actions and the Imperva GRE Performance Dashboard are now correctly displaying data. No data has been lost during this event. Technical teams will continue monitoring the system. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the s...
identified
We have identified the source of the degradation affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center. Customer domains are still fully protected at this time.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the up...
investigating
Technical teams are continuing to investigate the degradation affecting the Imperva GRE Performance Dashboard across multiple data centers.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected ...
investigating
We are continuing to investigate the degradation affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center.
Customer domains are still fully protected at this time. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of ...
investigating
We have discovered a degradation in our statistics affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center . Customer domains are still fully protected at this time. Technical teams are investigating. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availabilit...
[INC-997] New York 2, NY (EWR) 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.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential im...
identified
As a precautionary measure, the New York 2, NY (EWR) Data Center data center will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.
identified
We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a serv...
investigating
Technical teams are investigating a potential issue in the New York 2, NY (EWR) Data Center . Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
[INC-996] DUS traffic degradation
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 status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential im...
identified
As a precautionary measure, the Dusseldorf, Germany (DUS) data center will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.
identified
We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a serv...
investigating
Technical teams are investigating a potential issue in the Dusseldorf, Germany (DUS) data center. Further updates to follow.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.
In the event of a service disruption, the update will include potential impacts to any affected region.
[INC-994] Issue with Imperva Managed Certificates
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are observing signs of recovery, and certificate issuance is beginning to function again. Our teams are currently validating system stability and monitoring the process closely.
identified
We are continuing to work with our certificate authority provider to restore certificate issuance functionality. Existing certificates and active services remain unaffected.
Further updates will be shared as more information becomes available.
identified
We are continuing to work closely with our certificate authority provider to resolve the issue affecting certificate issuance. Efforts are ongoing to restore normal functionality as quickly as possible.
We will provide further updates as additional information becomes available.
identified
We are continuing to work with our certificate authority provider to resolve the issue affecting the ability to order or issue new certificates. Remediation efforts are currently in progress.
Existing certificates and active services remain unaffected. Further updates will be provided as more information becomes available.
identified
Our engineering team is actively working with the third-party certificate authority provider to resolve the issue affecting the issuance of new certificates.
We will continue to provide updates as progress is made toward restoring normal certificate ordering and issuance functionality.
investigating
We are currently experiencing an issue with the certificate issuance process with our upstream certificate authority provider. As a result, ordering or issuing new certificates is temporarily unavailable at this time.
This issue impacts all certificates managed through Imperva that require new issuance. Existing certificates and active services remain unaffected.
Our engineering team is actively working with the relevant provider to investigate and resolve the issue as quickly as possible. Fu...
