Imperva Outage History

Started Mar 15, 2026, 05:37 AM UTC· resolved Mar 15, 2026, 04:28 PM UTC

1. investigating Mar 15, 2026, 05:37 AM UTC

   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. Further updates will be shared as more information becomes available.

2. identified Mar 15, 2026, 06:22 AM UTC

   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.

3. identified Mar 15, 2026, 08:05 AM UTC

   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.

4. identified Mar 15, 2026, 10:14 AM UTC

   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.

5. identified Mar 15, 2026, 01:08 PM UTC

   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.

6. monitoring Mar 15, 2026, 03:38 PM UTC

   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.

7. resolved Mar 15, 2026, 04:28 PM UTC

   The issue affecting certificate issuance has been resolved, and certificate ordering and issuance functionality have been fully restored.

Read the full incident report →

Started Mar 11, 2026, 05:46 PM UTC· resolved Mar 11, 2026, 08:29 PM UTC

1. identified Mar 11, 2026, 05:46 PM UTC

   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 service disruption, the update will include potential impacts to any affected region.

2. identified Mar 11, 2026, 05:50 PM UTC

   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 service disruption, the update will include potential impacts to any affected region.

3. identified Mar 11, 2026, 06:51 PM UTC

   As a precautionary measure, the Seoul (KOR) PoP 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.

4. monitoring Mar 11, 2026, 08:07 PM UTC

   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 impacts to any affected region.

5. resolved Mar 11, 2026, 08:29 PM UTC

   Service in the Seoul (KOR) data center has been restored to normal.

Read the full incident report →

Started Mar 06, 2026, 02:20 AM UTC· resolved Mar 06, 2026, 10:31 PM UTC

1. investigating Mar 06, 2026, 02:20 AM UTC

   Technical teams are investigating a potential issue in the Tokyo, Japan (TKO) 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.

2. investigating Mar 06, 2026, 02:32 AM UTC

   Technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to ensure service stability. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation. 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.

3. identified Mar 06, 2026, 09:47 AM UTC

   The technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to maintain service stability and is scheduled to be brought back online at 21:00 UTC. Customer traffic continues to be served normally through alternate PoP. 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.

4. monitoring Mar 06, 2026, 09:17 PM UTC

   A fix has been implemented and traffic has been restored to the Tokyo, Japan (TKO) 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 impacts to any affected region.

5. resolved Mar 06, 2026, 10:31 PM UTC

   Service in the Tokyo, Japan (TKO) data center has been restored 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.

Read the full incident report →

Started Mar 05, 2026, 10:30 PM UTC· resolved Mar 06, 2026, 05:58 AM UTC

1. investigating Mar 05, 2026, 10:30 PM UTC

   Technical teams are investigating a potential issue in the Chicago 2, IL (CHI) 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 service disruption, the update will include potential impacts to any affected region.

2. identified Mar 05, 2026, 10:49 PM UTC

   We have identified an issue in the data center. Traffic continues to be rerouted through an alternate data center in the region. Customers may experience some latency while the reroute remains 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 service disruption, the update will include potential impacts to any affected region.

3. identified Mar 05, 2026, 11:41 PM UTC

   To maintain service stability, the Chicago 2, IL (CHI) data center will remain in bypass mode until off-site hours. During this time, customer traffic will continue to be served by alternate data centers in the region. Further updates will be shared as the situation progresses. 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.

4. monitoring Mar 06, 2026, 05:45 AM UTC

   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 impacts to any affected region.

5. resolved Mar 06, 2026, 05:58 AM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Mar 05, 2026, 05:19 PM UTC· resolved Mar 05, 2026, 10:59 PM UTC

1. investigating Mar 05, 2026, 05:19 PM UTC

   We are currently investigating a potential issue where cache purge requests may not be working as expected. As a result, some customer websites may temporarily display outdated or cached content. Our engineering teams are actively investigating the issue and working towards resolution. Further updates will be shared as more information becomes available.

2. identified Mar 05, 2026, 05:57 PM UTC

   We have identified the issue affecting cache purge functionality. Our engineering teams are currently working on implementing a fix and restoring normal functionality. We will provide further updates as progress is made.

3. identified Mar 05, 2026, 06:48 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Mar 05, 2026, 07:52 PM UTC

   Our engineering teams have made progress in addressing the issue affecting cache purge functionality, and remediation efforts are ongoing.

5. identified Mar 05, 2026, 10:11 PM UTC

   We are continuing to work on a fix for this issue.

6. resolved Mar 05, 2026, 10:59 PM UTC

   Our engineering teams have completed the remediation. The issue affecting cache purge functionality has been resolved. 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.

Read the full incident report →

Started Mar 03, 2026, 01:04 PM UTC· resolved Mar 03, 2026, 08:26 PM UTC

1. investigating Mar 03, 2026, 01:04 PM UTC

   We have discovered a service degradation affecting Attack Analytics, the page is returning errors. 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.

2. identified Mar 03, 2026, 01:33 PM UTC

   We have identified the source of the issue affecting Attack Analytics. Technical teams are planning remedial action. Further updates to follow.

3. monitoring Mar 03, 2026, 02:32 PM UTC

   The fix has been successfully implemented, and the Attack Analytics page is now accessible. We are continuing to closely monitor the service to ensure stability and optimal performance. Further updates to follow.

4. resolved Mar 03, 2026, 08:26 PM UTC

   The incident has been resolved and normal service levels have been restored. 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.

Read the full incident report →

Started Mar 03, 2026, 11:57 AM UTC· resolved Mar 03, 2026, 02:35 PM UTC

1. investigating Mar 03, 2026, 11:57 AM UTC

   We are investigating an issue where some customers are unable to access the API Security "My APIs" Inventory and upload/manage OAS/Swagger files. Our technical teams are currently investigating the issue. Further updates will 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.

2. investigating Mar 03, 2026, 12:12 PM UTC

   We are continuing to investigate this issue.

3. identified Mar 03, 2026, 12:53 PM UTC

   We have identified the source of the issue affecting access to the API Security Page, "My APIs" Inventory and upload/manage OAS/Swagger files. Technical teams are planning remedial action. 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.

4. monitoring Mar 03, 2026, 01:35 PM UTC

   Technical teams have performed remedial actions and the API Security Page back to normal . Technical teams will continue monitoring the system. 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

5. resolved Mar 03, 2026, 02:35 PM UTC

   The incident has been resolved and normal service levels have been restored. 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.

Read the full incident report →

Started Feb 27, 2026, 12:10 PM UTC· resolved Feb 28, 2026, 12:26 AM UTC

1. investigating Feb 27, 2026, 12:10 PM UTC

   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. 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.

2. identified Feb 27, 2026, 12:44 PM UTC

   We have identified an issue impacting connectivity through a third-party transit ISP. The provider is actively working to resolve the problem. We are closely monitoring the situation and will share further updates as soon as additional 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 potential impacts to any affected region.

3. identified Feb 27, 2026, 02:19 PM UTC

   We are currently experiencing a connectivity issue related to a third-party transit ISP. Traffic has been rerouted through an alternate data center within the region to maintain service availability. During this time, some customers may experience increased latency until normal routing is fully restored. 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.

4. identified Feb 27, 2026, 05:54 PM UTC

   Traffic continues to remain rerouted through the alternate data center within the region to ensure service availability. We are actively following up with the third-party transit ISP(s) as they continue their investigation into the connectivity issue. During this time, some customers may experience increased latency until normal routing is fully restored. 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 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.

5. monitoring Feb 27, 2026, 11:36 PM UTC

   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 impacts to any affected region.

6. resolved Feb 28, 2026, 12:26 AM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Feb 25, 2026, 04:27 AM UTC· resolved Feb 25, 2026, 10:11 AM UTC

1. identified Feb 25, 2026, 04:27 AM UTC

   Technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to ensure service stability. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation. 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.

2. monitoring Feb 25, 2026, 09:12 AM UTC

   Technical teams have remove the bypass. There was no customer impact identified and we identified an internal issue with our monitoring systems. Customer traffic has resumed via Tokyo, Japan (TKO). 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.

3. resolved Feb 25, 2026, 10:11 AM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Feb 20, 2026, 07:55 AM UTC· resolved Feb 20, 2026, 08:16 AM UTC

1. investigating Feb 20, 2026, 07:55 AM UTC

   Technical teams are investigating a potential issue in the Vancouver, Canada (VAN) 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.

2. identified Feb 20, 2026, 08:06 AM UTC

   We have identified the source of the issue in the data center. Technical teams are working on a fix. 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.

3. monitoring Feb 20, 2026, 08:10 AM UTC

   A fix has been implemented and 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.

4. resolved Feb 20, 2026, 08:16 AM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Feb 19, 2026, 02:10 PM UTC· resolved Feb 19, 2026, 03:13 PM UTC

1. monitoring Feb 19, 2026, 02:10 PM UTC

   We experienced a brief issue impacting the Sydney Australia (SYD) and Melbourne, Australia (MEB) data center for 34 minutes (12:48–13:22 UTC). The issue has been resolved, and our technical teams are actively monitoring services at these location. During the incident, customers using Cloud WAF–protected sites and GRE tunnels may have experienced higher-than-expected latency, intermittent connectivity, or a temporary loss of connectivity to services in the SYD and MEB PoPs. 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.

2. resolved Feb 19, 2026, 03:13 PM UTC

   Monitoring has confirmed that services are stable across the affected data centers, and no further issues have been identified. 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.

Read the full incident report →

Started Feb 19, 2026, 08:15 AM UTC· resolved Feb 19, 2026, 10:32 AM UTC

1. investigating Feb 19, 2026, 08:15 AM UTC

   We have discovered a potential service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable. 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.

2. investigating Feb 19, 2026, 08:36 AM UTC

   We have discovered a potential service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable due to connectivity issues. Technical teams are currently investigating potential issues with a third-party provider. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our 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.

3. investigating Feb 19, 2026, 08:51 AM UTC

   We have discovered a potential service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable due to connectivity issues. This issue is also affecting our teams' ability to connect to our telephony system. We are treating this matter with the highest priority. Technical teams are currently investigating potential issues with a third-party provider. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

4. identified Feb 19, 2026, 09:53 AM UTC

   We have identified a potential cause for the service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable due to connectivity issues. This issue is also affecting our teams' ability to connect to our telephony system. We are treating this matter with the highest priority. Technical teams are currently investigating potential issues with our third-party provider. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

5. monitoring Feb 19, 2026, 10:06 AM UTC

   Technical teams have performed remedial actions and the Imperva Support Portal access is returning to normal operations. Technical teams will continue monitoring the system. 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.

6. resolved Feb 19, 2026, 10:32 AM UTC

   The incident has been resolved and normal service levels have been restored. We apologize for any inconvenience that this issue may have caused. 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.

Read the full incident report →

Started Feb 17, 2026, 12:10 PM UTC· resolved Feb 17, 2026, 01:51 PM UTC

1. investigating Feb 17, 2026, 12:10 PM UTC

   We have identified an issue impacting the adding of new SANs and the adding of existing SANs undergoing revalidation on Imperva Managed Certificates. At this time, affected scenarios are new SAN validations and SAN renewal where the old certificate has expired, and the SAN has not been revalidated in the current period. This incident does not affect protection for websites onboarded to Imperva. 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.

2. monitoring Feb 17, 2026, 12:48 PM UTC

   Technical teams have performed remedial actions and SSL SAN validation issue is returning to normal operations. 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.

3. resolved Feb 17, 2026, 01:51 PM UTC

   This issue has been resolved. 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.

Read the full incident report →

Started Feb 13, 2026, 09:58 AM UTC· resolved Feb 13, 2026, 08:53 PM UTC

1. monitoring Feb 13, 2026, 09:58 AM UTC

   Due to an issue with IPv6 traffic in our Sydney, Australia (SYD) Data Center, IPv6 traffic from SYD has been rerouted away, through an alternative data center in the region. Customers may encounter some latency on IPv6 traffic in the region while we resolve this issue. IPv4 traffic is unaffected and continues to be served by our SYD data center. 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.

2. identified Feb 13, 2026, 10:18 AM UTC

   Due to an issue with IPv6 traffic in our Sydney, Australia (SYD) Data Center, IPv6 traffic from SYD has been rerouted away, through an alternative data center in the region. Customers may encounter some latency on IPv6 traffic in the region while we resolve this issue. IPv4 traffic is unaffected and continues to be served by our SYD data center. 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.

3. identified Feb 13, 2026, 01:08 PM UTC

   Technical teams are continuing to working on a fix for the data center issue. 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.

4. investigating Feb 13, 2026, 03:56 PM UTC

   The technical teams are currently investigating a potential issue and have deactivated the Sydney (SYD) Data Center, Australia. Traffic has been rerouted to an alternate data center within the same region to maintain service continuity 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.

5. identified Feb 13, 2026, 05:36 PM UTC

   The issue has been identified, and our technical teams are actively working on implementing a fix. The Sydney (SYD) Data Center remains temporarily deactivated while remediation activities are in progress. Traffic continues to be rerouted to an alternate data center within the same region to maintain service continuity. 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.

6. monitoring Feb 13, 2026, 08:16 PM UTC

   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 impacts to any affected region.

7. resolved Feb 13, 2026, 08:53 PM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Feb 12, 2026, 10:59 PM UTC· resolved Feb 13, 2026, 02:33 AM UTC

1. investigating Feb 12, 2026, 10:59 PM UTC

   We are investigating an issue in the Stockholm, Sweden (STO) 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 service disruption, the update will include potential impacts to any affected region.

2. investigating Feb 12, 2026, 11:37 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 13, 2026, 01:54 AM UTC

   Due to an issue in the data center traffic remains 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 service disruption, the update will include potential impacts to any affected region.

4. monitoring Feb 13, 2026, 02:15 AM UTC

   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 impacts to any affected region.

5. resolved Feb 13, 2026, 02:33 AM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Feb 03, 2026, 06:07 PM UTC· resolved Feb 05, 2026, 03:46 PM UTC

1. investigating Feb 03, 2026, 06:07 PM UTC

   Our technical teams are currently investigating an issue affecting the Los Angeles, CA (SNA) Point of Presence. Some customers may experience intermittent connectivity or timeouts when accessing CWAF-protected applications through this location.

2. investigating Feb 03, 2026, 06:40 PM UTC

   Our technical teams continue to actively investigate the issue affecting the Los Angeles, CA (SNA) Point of Presence.

3. investigating Feb 03, 2026, 07:26 PM UTC

   Our technical teams have isolated the affected components, and customer impact has been mitigated. Services are currently stable. We are continuing to investigate the issue to identify the root cause and ensure long-term stability.

4. investigating Feb 03, 2026, 07:57 PM UTC

   Our teams continue to investigate the issue. Services are currently stable and there is no ongoing customer impact. We will provide further updates as more information becomes available.

5. identified Feb 03, 2026, 10:19 PM UTC

   The issue has been identified and isolated. At this time, there is no current customer impact. We are continuing to closely monitor the environment to ensure service remains stable.

6. monitoring Feb 04, 2026, 09:38 AM UTC

   We deactivated the problematic component and issue has been remediated. 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.

7. resolved Feb 05, 2026, 03:46 PM UTC

   The incident has been resolved and service in the data center has been restored 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.

Read the full incident report →

Started Feb 01, 2026, 12:12 PM UTC· resolved Feb 01, 2026, 03:00 PM UTC

1. identified Feb 01, 2026, 12:12 PM UTC

   We have identified a service degradation that is causing the dashboard on the network not to display historical data for Network Protect dashboards. Despite this issue, customers can continue to use the Imperva Management Portal for managing their accounts without interruption. Technical teams are working on a mitigation. 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.

2. identified Feb 01, 2026, 12:46 PM UTC

   Technical teams are continuing to working on a fix for this issue.

3. identified Feb 01, 2026, 01:20 PM UTC

   Our engineers are actively working on the fix to resolve this issue. We will provide another update in 2 hours or as soon as more information becomes available.

4. monitoring Feb 01, 2026, 02:28 PM UTC

   Technical teams have performed remedial actions and the dashboard on the network display historical data for Network Protect dashboards. Imperva Management Portal is returning to normal service levels. 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 service. In the event of a service disruption, the update will include potential impacts to any affected region.

5. monitoring Feb 01, 2026, 02:54 PM UTC

   This issue has been resolved.

6. resolved Feb 01, 2026, 03:00 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Jan 22, 2026, 11:05 PM UTC· resolved Jan 23, 2026, 02:25 AM UTC

1. investigating Jan 22, 2026, 11:05 PM UTC

   We have discovered a potential 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. 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.

2. investigating Jan 22, 2026, 11:54 PM UTC

   We are continuing to investigate the service degradation affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. 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.

3. monitoring Jan 23, 2026, 12:52 AM UTC

   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 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.

4. resolved Jan 23, 2026, 02:25 AM UTC

   The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. 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.

Read the full incident report →

Started Jan 20, 2026, 02:46 AM UTC· resolved Jan 20, 2026, 09:52 PM UTC

1. investigating Jan 20, 2026, 02:46 AM UTC

   Technical teams are investigating a potential issue in the Hanoi, Vietnam (HAN) 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.

2. identified Jan 20, 2026, 02:58 AM UTC

   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 service disruption, the update will include potential impacts to any affected region.

3. identified Jan 20, 2026, 03:05 AM UTC

   As a precautionary measure, the Hanoi (HAN) PoP 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 monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation. 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.

4. monitoring Jan 20, 2026, 08:43 PM UTC

   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 impacts to any affected region.

5. resolved Jan 20, 2026, 09:52 PM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Jan 18, 2026, 12:55 PM UTC· resolved Jan 19, 2026, 10:05 PM UTC

1. investigating Jan 18, 2026, 12:55 PM UTC

   Technical teams are investigating a potential issue in the Hanoi, Vietnam (HAN) 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.

2. identified Jan 18, 2026, 12:56 PM UTC

   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 service disruption, the update will include potential impacts to any affected region.

3. identified Jan 18, 2026, 01:28 PM UTC

   Technical teams are continuing to working on a fix for the data center issue.

4. identified Jan 18, 2026, 02:13 PM UTC

   Technical teams are currently investigating the issue and will provide updates 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 potential impacts to any affected region.

5. identified Jan 18, 2026, 02:43 PM UTC

   Our engineers are actively working on the fix to resolve the data center issue. We will provide another update in 2 hours or 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 potential impacts to any affected region.

6. identified Jan 18, 2026, 04:32 PM UTC

   As a precautionary measure, the Hanoi (HAN) PoP 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 monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation. 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.

7. monitoring Jan 19, 2026, 08:31 PM UTC

   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 impacts to any affected region.

8. resolved Jan 19, 2026, 10:05 PM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Jan 17, 2026, 03:49 PM UTC· resolved Jan 18, 2026, 01:10 AM UTC

1. monitoring Jan 17, 2026, 03:49 PM UTC

   We experienced a brief issue impacting the Osaka, Japan (OSK), Seoul, South Korea (KOR), and Tokyo, Japan (TKO) Points of Presence. The issue has been resolved, and our technical teams are actively monitoring services at these locations. During the incident, customers using Cloud WAF–protected sites and GRE tunnels may have experienced higher-than-expected latency, intermittent connectivity, or a temporary loss of connectivity to services in the OSK, KOR, and TKO PoPs. 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.

2. resolved Jan 18, 2026, 01:10 AM UTC

   Monitoring has confirmed that services are stable across the affected data centers, and no further issues have been identified. 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.

Read the full incident report →

Started Jan 16, 2026, 12:51 PM UTC· resolved Jan 16, 2026, 03:10 PM UTC

1. investigating Jan 16, 2026, 12:51 PM UTC

   We have identified a potential issue affecting On-Demand DDoS Protection, where traffic diversion may not function as expected. Our technical teams are actively investigating the issue. 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 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.

2. monitoring Jan 16, 2026, 01:50 PM UTC

   On-Demand DDoS Protection is currently operational, and traffic diversion is functioning as expected. The technical teams continue to monitor the service 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 affected region.

3. resolved Jan 16, 2026, 03:10 PM UTC

   Services are stable and operating normally. We identified an internal service issue that prevented customer traffic from being diverted to Imperva’s mitigation network during active attack conditions. The issue was caused by an internal authentication failure. The service was restored after the affected component was restarted, and traffic diversion is now functioning as expected. We are performing a detailed root cause analysis and enhancing monitoring and automated recovery mechanisms to ensure faster detection and prevent recurrence. Additional details will be shared once the investigation is complete.

Read the full incident report →

Started Jan 07, 2026, 04:08 PM UTC· resolved Jan 07, 2026, 05:46 PM UTC

1. investigating Jan 07, 2026, 04:08 PM UTC

   Technical teams are investigating a potential issue in the Ashburn, VA (IAD) Data Center . Further updates to follow.

2. identified Jan 07, 2026, 04:35 PM UTC

   We have identified the source of the issue in the data center. Technical teams are working on a fix. 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.

3. monitoring Jan 07, 2026, 04:55 PM UTC

   A fix has been implemented and 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.

4. resolved Jan 07, 2026, 05:46 PM UTC

   Services in the data center has been restored to normal. The IAD PoP was inadvertently deactivated, which caused customer CWAF traffic to be temporarily routed to alternate PoPs. Once identified, the PoP was reactivated, and engineers have confirmed that traffic has now shifted back to IAD and is being processed normally. During the incident, some traffic may have experienced a brief period of session resets and increased latency due to sub-optimal routing to alternate PoPs. Further research will be performed into how to prevent the triggering event which caused the PoP deactivation from recurring, and additional details will be provided following a completed root cause analysis.

Read the full incident report →

Started Jan 03, 2026, 04:10 PM UTC· resolved Jan 03, 2026, 07:20 PM UTC

1. identified Jan 03, 2026, 04:10 PM UTC

   We have identified an issue in the Hanoi, Vietnam (HAN) 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 service disruption, the update will include potential impacts to any affected region.

2. investigating Jan 03, 2026, 04:45 PM UTC

   Technical teams are continuing to working on a fix for the data center issue. 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.

3. identified Jan 03, 2026, 04:57 PM UTC

   Technical teams are continuing to working on a fix for the data center issue. 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.

4. monitoring Jan 03, 2026, 06:43 PM UTC

   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 impacts to any affected region.

5. resolved Jan 03, 2026, 07:20 PM UTC

   Service in the data center has been restored 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.

Read the full incident report →

Started Dec 30, 2025, 03:17 PM UTC· resolved Jan 05, 2026, 12:52 PM UTC

1. investigating Dec 30, 2025, 03:17 PM UTC

   Technical teams are currently investigating a potential issue impacting the Chicago 2, IL (CHI) data center. At this time our services are operational. However, some customers may experience intermittent connectivity issues when accessing websites. Customers encountering any issues are advised to contact Imperva Support for assistance. 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.

2. investigating Dec 30, 2025, 04:15 PM UTC

   We are continuing to investigate this issue.

3. investigating Dec 30, 2025, 05:09 PM UTC

   Technical teams are currently investigating and will provide updates as more information becomes available.

4. investigating Dec 30, 2025, 05:57 PM UTC

   Technical teams are actively investigating the issue.

5. investigating Dec 30, 2025, 06:30 PM UTC

   We are continuing to investigate this issue.

6. investigating Dec 30, 2025, 07:04 PM UTC

   Technical teams are currently investigating the issue and will provide updates 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 potential impacts to any affected region.

7. investigating Dec 30, 2025, 07:34 PM UTC

   We are investigating the issue and will share updates as available.

8. investigating Dec 30, 2025, 08:05 PM UTC

   Technical teams are actively investigating the issue.

9. investigating Dec 30, 2025, 08:35 PM UTC

   Technical teams are currently investigating the issue and will provide updates 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 potential impacts to any affected region.

10. investigating Dec 30, 2025, 09:05 PM UTC

    Technical teams are currently investigating and will provide updates as more information becomes available.

11. identified Dec 30, 2025, 09:36 PM UTC

    To ensure the best possible user experience and maintain business continuity, we have proactively implemented a temporary bypass of the Chicago (CHI) PoP. Customers who were previously served by the CHI PoP are being automatically rerouted to an alternative PoP. This process requires no action on your part, and services will continue to be delivered as usual. As a result of this rerouting, some customers may experience slightly increased latency. This behavior is expected during the bypass and does not indicate a service outage. If you experience any issues beyond normal latency, please contact our Technical Support team so we can assist promptly. We will continue to monitor the situation closely and provide updates as needed. 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.

12. identified Dec 31, 2025, 03:34 PM UTC

    As a precautionary measure, the Chicago (CHI) PoP will remain bypassed through the upcoming holiday period to ensure service stability. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation. 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.

13. monitoring Jan 05, 2026, 11:56 AM UTC

    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 impacts to any affected region.

14. resolved Jan 05, 2026, 12:52 PM UTC

    Service in the data center has been restored 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.

Read the full incident report →