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.
August 2026
[INC-1111] Istanbul, Turkey (SAW ) Data Center Issue
majorSource not attested
Last archived state: resolved
View archived record details
Istanbul, Turkey (SAW)
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.
identified
Our teams remain actively engaged in the investigation and remediation. Customers may experience increased latency while traffic remains rerouted. We will provide further updates as additional information becomes available.
identified
We have identified an issue in the Istanbul, Turkey (SAW ) 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.
investigating
We have identified an issue in the Istanbul, Turkey (SAW ) 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 on the incident will be shared no later than 19:41 UTC
[INC-1109] Frankfurt (HHN) Data Center Issue
minorSource not attested
Last archived state: resolved
View archived record details
Frankfurt, Germany (HHN)
monitoring
We have discovered a service degradation that affected the Frankfurt (HHN) Data Center Issue which may have resulted in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Service was restored in the PoP, mitigating the impact to customers.
[INC-1105] YUL PoP Service Degradation
majorSource not attested
Last archived state: resolved
View archived record details
Montreal, Canada (YUL)
monitoring
Remediation activities have been completed, and the YUL (Montreal, Canada) PoP has been successfully restored and returned to service. Traffic is once again being served through the YUL PoP as normal.
We are continuing to closely monitor the environment to ensure stability and verify that all services remain fully operational. At this time, no customer impact is expected.
We will provide a final update once the incident has been fully resolved.
monitoring
Remediation is nearing completion, with the majority of the required work now finished. Only a few final activities remain before the YUL PoP can be safely reactivated. In the meantime, service remains stable as traffic continues to be routed through alternate Points of Presence.
Our current target is to complete the remaining activities and restore the YUL PoP to normal operation by Monday. We will continue to closely monitor the service and provide further updates as the work progresses.
monitoring
We have identified the source of the issue affecting the YUL (Montreal, Canada) PoP and continue to work on remediation. Service remains stable as traffic is being served through alternate Points of Presence (PoPs).
Our updated expected ETA for restoring the YUL PoP to normal operation is Monday. We will continue to closely monitor the service and provide further updates as more information becomes available.
monitoring
We have identified the source of the issue affecting the YUL (Montreal, Canada) PoP and are working on remediation. While completing the remediation may take an extended period of time, service has been stabilised by rerouting traffic through alternate Points of Presence (PoPs).
Traffic continues to be served through alternate locations, and we are not currently observing customer impact. We will continue to work towards restoring the YUL PoP to normal operation and will provide further upda...
monitoring
Traffic is now being served by other PoPs, and service has stabilised. Our teams continue to investigate the underlying cause of the issue affecting the YUL infrastructure and are working towards restoring the PoP to normal operation.
We will continue to monitor the environment closely and provide further updates as they become available. The next update will be no later than 09:18 UTC.
monitoring
We have mitigated the issue affecting the YUL (Montreal, Canada) PoP by removing the affected PoP from service and redirecting traffic to alternate locations.
Traffic is now being served by other PoPs, and service has stabilised. Our teams continue to investigate the underlying cause of the issue affecting the YUL infrastructure and are working towards restoring the PoP to normal operation.
We will continue to monitor the environment closely and provide further updates as they become availa...
investigating
We are investigating an issue affecting traffic reaching our YUL (Montreal, Canada) PoP. Customers may experience connectivity issues, increased latency, or service disruptions when traffic is routed through this location.
Our teams are actively investigating the issue and working to identify the root cause. We will provide further updates as more information becomes available.
The next update will be before 08:51 UTC
Technical teams have completed the necessary remediation, and configuration propagation through the Imperva Management Portal has returned to normal operating levels. The teams will continue to closely monitor the system to ensure ongoing stability. Further updates will be provided as they become available.
identified
Our technical teams continue to actively investigate the configuration publishing issue. Remediation and validation activities are ongoing, and the team is working to restore normal publishing operations while closely monitoring the service.
Customer sites remain protected. We will continue to provide updates as more information becomes available.
identified
Our technical teams continue to actively work on the configuration publishing issue. Remediation is progressing in a controlled manner, with the team working to restore the processing of affected configurations.
We are closely monitoring the service and validating the recovery as remediation activities continue. Customer sites remain protected. We will provide further updates as more information becomes available.
identified
Our technical teams remain actively engaged in addressing the configuration publishing issue. Remediation activities are ongoing, and we continue to closely monitor the service to ensure a stable and sustained recovery.
Customer sites remain protected. We will continue to provide updates as further information becomes available.
identified
Our technical teams continue to actively work on the issue affecting configuration publishing. Remediation efforts are underway, and we are closely monitoring the service to ensure a stable recovery.
Customer sites remain protected. We will provide further updates as more information becomes available.
identified
Our technical teams are actively engaged and working to remediate the issue. We are continuing to monitor the affected services closely and will provide further updates as more information becomes available. Customer sites remain protected.
identified
During our ongoing monitoring, we observed another instance of delayed configuration publishing. The technical team is actively investigating and working on remediation. Customer sites remain protected, and we continue to closely monitor the service.
monitoring
The technical team has applied a fix to address the issue, and the Publisher has returned to normal operation. Configuration changes are now being processed as expected, and the service has returned to a stable state. The team continues to monitor the system to ensure ongoing stability.
identified
Technical teams have identified the underlying issue and are actively working on a fix to restore normal configuration publishing.
The next update will be provided no later than 21:00 UTC.
investigating
We have discovered a service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. Customer sites are still fully protected at this time. Technical teams are investigating. Further updates to follow.
[INC-1102] Data Center Issues
Source not attested
Last archived state: resolved
View archived record details
monitoring
A potential contributing factor has been identified. Services remain stable across all affected Points of Presence (PoPs), and no further issues have been observed since recovery. Our teams continue to closely monitor the environment to ensure ongoing service stability.
investigating
Services remain stable across all previously affected Points of Presence (PoPs). Our teams continue to closely monitor the environment and analyze the event to confirm the underlying cause and ensure the continued stability of our services.
investigating
We identified a brief issue impacting our Points of Presence (PoPs), which may have caused infrastructure tunnel disconnections and intermittent website timeouts for some customers. The issue has now recovered, and services are operating normally.
Our teams are actively monitoring the platform to ensure continued stability.
[INC-1101] Real-Time WAF Alerting Service Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented to address the issue affecting real-time WAF alerts, and we are observing recovery across impacted services.
WAF protection remained fully operational throughout the incident. The issue was limited to real-time alerting and did not impact traffic inspection or policy enforcement.
We are currently monitoring the environment to ensure alert delivery has returned to normal operation and that no further issues are observed. We will continue to provide updates as warra...
identified
We have identified the underlying cause of the issue affecting real-time WAF alerts. Our investigation indicates that the impact is limited to a subset of customers.
WAF protection remains fully operational. This issue affects real-time alerting only and does not impact traffic inspection or policy enforcement.
Our teams are working on mitigation and validation efforts. We will provide further updates as we make progress toward resolution. Our next update will be before 12:55 PM UTC
investigating
We are currently investigating reports of a potential issue affecting the generation and/or delivery of real-time WAF alerts.
Some customers may experience delays in receiving WAF alerts or observe that expected real-time notifications are not being triggered. We are actively assessing the scope and impact of the issue and will provide further updates as more information becomes available.
WAF protection remains fully operational. This issue affects real-time alerts only and does not impact...
July 2026
[INC-1096] Global Support Phone System Disruption
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our team continues to monitor the service to ensure stability and ongoing availability.
Support phone numbers are operating normally, and users can contact Support by phone. Customers may continue to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance.
The next status update for this incident will be provided no later than 11:00 UTC.
The status updates are an integral part of proactive monitoring and transparent communication ab...
monitoring
Our team continues to monitor the service to ensure stability and ongoing availability.
Support phone numbers are operating normally, and users can contact Support by phone. Customers may continue to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance.
The next status update for this incident will be provided no later than 07:00 UTC.
The status updates are an integral part of proactive monitoring and transparent communication ab...
monitoring
Our team is actively monitoring the service to ensure stability and continued availability.
Support phone numbers are operating normally, and users should be able to contact Support by phone. Customers can continue to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance.
The next Status Update on this Incident will be provided no later than 06:00 UTC
The status updates are an integral part of proactive monitoring and transparent c...
identified
The issue has been identified, and our team is actively implementing corrective actions while monitoring the recovery progress.
Support phone numbers are currently operating normally, and users should be able to contact Support by phone. Customers are encouraged to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance while our team continues to monitor service stability.
Further updates will be provided as more information becomes...
investigating
We are currently investigating reports of a global issue impacting access to our support phone system. At this time, support phone numbers are operating normally, and users should be able to contact Support by phone.
Customers are encouraged to use the Customer Portal to submit support requests with the appropriate severity level for the fastest assistance while our team continues to monitor service stability.
The next Status Update on this Incident will be provided no later than 04:00 UTC
...
investigating
We are currently aware of a global issue impacting our support phone system. As a result, users may be unable to contact Support by phone. Our team is actively investigating the issue and working to restore service as quickly as possible. We apologize for any inconvenience this may cause.
The next update on this incident will be provided no later than 02:40 UTC
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services...
investigating
We are aware of an issue affecting our support phone system globally. Users may be unable to reach support by phone. Our team is actively investigating the issue and working to restore service as quickly as possible. We apologize for the inconvenience .
The next Status Update on this Incident will be provided no later than 02: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 at...
[INC-1092] Support Ticketing System Issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue preventing some customers from logging in to the Customer Support Portal has been resolved. Technical teams have completed remedial actions, and the portal has returned to normal operation. We are continuing to monitor the service to ensure stability and will provide a final update once monitoring is complete.
investigating
Our teams are actively working to restore access to the Support Ticketing System. While this work is ongoing, customers experiencing issues accessing the Support Portal can reach our Support team for urgent assistance by calling +1 410 469 1651. Thank you for your patience as we work to resolve the issue.
investigating
We are investigating a potential issue affecting the Support Ticketing System. Customers may be experiencing issues logging into the Support Portal. Our technical teams are actively investigating the issue.
The next update on the issue will be shared no later than 6:39 UTC.
[INC -1084] Rio de Janeiro, Brazil (RIO) 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 Rio de Janeiro, Brazil (RIO) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.
Next Status Update on this Incident will be provided no later than 6:03 UTC.
The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imper...
identified
We have worked with the hardware vendor to address the underlying issue. Based on the current assessment and successful health checks, the team has scheduled the affected PoP to be reactivated at 03:00 UTC on 18 July 2026.
To maintain service availability, traffic continues to be rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect.
The next update on this incident will be provided no later t...
identified
We are actively working with Hardware vendor to resolve the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect.
The next update can be expected around 16: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...
identified
Our team has identified a hardware issue within the routing infrastructure and is actively working with the vendor to troubleshoot and resolve the issue. To maintain service availability, traffic continues to be temporarily rerouted through an alternate data center in the region. Customers may continue to experience increased latency while this temporary routing remains in place.
Next update on the issue will be shared no later than 8:15 UTC.
The status updates are an integral part of proac...
identified
Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency.
We will provide the next update no later than 7:45 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 de...
identified
Our team is actively working to resolve the issue. To maintain service availability, traffic has been rerouted through an alternate data center in the region. Customers may experience increased latency while this temporary routing remains in place.
Next update on the issue will be shared no later than 7:10 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 ...
identified
The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect.
Next update on the issue will be shared no later than 6:35 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 ...
identified
We have identified an issue in the Rio de Janeiro, Brazi data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.
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.
...
[INC-1081] Johannesburg, South Africa (QRA) 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 Johannesburg, South Africa (QRA) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.
Next Status Update on this Incident will be provided no later than 23:40 UTC.
identified
Our team is currently working to reactivate the affected Point of Presence (PoP). We will provide another update once the PoP has been successfully restored.
In the meantime, traffic is being rerouted through an alternate data center within the region to maintain service availability. During this period, customers may experience increased latency and intermittent timeouts. The team continues to closely monitor the environment and is actively working to restore normal service as quickly as po...
identified
The team has identified the underlying issue and implemented a fix. To ensure business continuity and validate service stability, the Johannesburg, South Africa (QRA) PoP is scheduled to be reactivated at 23:00 UTC .
In the meantime, traffic is being rerouted through an alternate data center in the region. Customers may experience increased latency and intermittent timeouts while the reroute remains in place. The team continues to closely monitor the environment .
Next update on the issue w...
investigating
We have identified a potential issue in the Johannesburg, South Africa (QRA) 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 availabili...
