Update - Investigations are currently in progress, and the team is actively working on the issue.
Next update on this incident will be shared no later than 20:51 UTC.

May 15, 2026 - 20:21 UTC
Update - Our technical teams are actively investigating the issue and working on remediation.
Next update on this incident will be shared no later than 20:21 UTC.

May 15, 2026 - 19:51 UTC
Investigating - We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow.

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.

May 15, 2026 - 19:22 UTC
North American PoPs Operational
Ashburn, VA (IAD) Operational
Atlanta, GA (ATL) Operational
Chicago 1, IL (ORD) Operational
Chicago 2, IL (CHI) Operational
Dallas, TX (DFW) Operational
Denver, CO (DEN) Operational
Detroit, MI (DET) Operational
Houston, TX (HOU) Operational
Los Angeles, CA (SNA) Operational
Miami, FL (MIA) Operational
Montreal, Canada (YUL) Operational
New York 1, NY (NYC) Operational
New York 2, NY (EWR) Operational
San Jose, CA (SFO) Operational
Seattle, WA (SEA) Operational
Toronto, Canada (TOR) Operational
Vancouver, Canada (VAN) Operational
EMEA PoPs Operational
Amsterdam, Netherlands (RTM) Operational
Barcelona, Spain (BCN) Operational
Cape Town, South Africa (CPT) Operational
Copenhagen, Denmark (CPH) Operational
Dubai, UAE (DWC) Operational
Dublin, Ireland (DUB) Operational
Dusseldorf, Germany (DUS) Operational
Frankfurt, Germany (HHN) Operational
Istanbul, Turkey (SAW) Operational
Johannesburg, South Africa (QRA) Operational
London, UK (LCY) Operational
London 2, UK (LHR) Operational
Madrid, Spain (MAD) Operational
Milan, Italy (MXP) Operational
Paris, France (PAR) Operational
Stockholm, Sweden (STO) Operational
Tel Aviv, Israel (MED) Operational
Vienna, Austria (GRZ) Operational
Warsaw, Poland (WAR) Operational
Zurich, Switzerland (GVA) Operational
LATAM PoPs Operational
Bogota, Colombia (BOG) Operational
Buenos Aires, Argentina (EZE) Operational
Lima, Peru (LIM) Operational
Queretaro, Mexico (QRO) Operational
Rio de Janeiro, Brazil (RIO) Operational
Santiago, Chile (STC) Operational
Sao Paulo, Brazil (SAO) Operational
APAC PoPs Operational
Auckland, New Zealand (AKL) Operational
Bangkok, Thailand (DMK) Operational
Hanoi, Vietnam (HAN) Operational
Hong Kong (HHK) Operational
Jakarta, Indonesia (JKT) Operational
Kuala Lumpur, Malaysia (KUL) Operational
Melbourne, Australia (MEB) Operational
Manila, Philippines (MNL) Operational
Mumbai 1, India (BOM) Operational
Mumbai 2, India (NAG) Operational
New Delhi, India (NDL) Operational
Osaka, Japan (OSK) Operational
Seoul, South Korea (KOR) Operational
Singapore (SIN) Operational
Sydney, Australia (SYD) Operational
Taipei, Taiwan (TSA) Operational
Tokyo, Japan (NRT) Operational
Imperva for Google Cloud (IGC) Regions Operational
us-east1 region Operational
us-east4 region Operational
us-east5 region Operational
us-central1 region Operational
europe-west1 region Operational
Protection Services Operational
Cloud WAF Protection Operational
Web Application Performance Operational
IGC WAF Protection Operational
Cloud L7 DDoS Protection Operational
Login Protect Operational
File Upload Scan and Protect Operational
Protected DNS Operational
Managed DNS Operational
L3/4 IP Protection Operational
L3/4 Network DDoS Protection Operational
Advanced BOT Protection Operational
API Security Operational
Account Takeover Protection Operational
Client-Side Protection Operational
Waiting Room Operational
Management and Analytics Services Partial Outage
Cloud Security Management Platform Partial Outage
Cloud Security Management Configuration Changes Operational
Account and User Management Operational
CDN and WAF Management Operational
API Security Management Operational
Network DDoS Management Operational
DNS protection Managment Operational
ABP Management Operational
Account Takeover Protection Management Operational
Client-Side Protection Management Operational
Waiting Room Management Operational
Runtime Protection Deployment Operational
SIEM Logs Operational
Events Page Operational
Attack Analytic Operational
IP Reputation Operational
Additional services Operational
Support Ticketing System Operational
Support Phone Systems Operational
Documentation Portal Operational
Third Party Services Operational
Third Party Services Operational
Coming Soon Under Maintenance
Singapore (XSP) - May 2026 Under Maintenance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

[ICM-5016] Essential Maintenance on the Imperva data center in Ashburn, VA May 18, 2026 03:00-11:00 UTC

Maintenance on the Ashburn, VA data center will be performed on Monday, May 18th, 2026 at 03:00 UTC. We expect to complete the maintenance by Monday, May 18th, 2026 at 11:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 14, 2026 - 18:01 UTC

[ICM-5025] Essential Maintenance on the Imperva data center in Buenos Aires, Argentina May 18, 2026 04:00-10:00 UTC

Maintenance on the Buenos Aires, Argentina data center will be performed on Monday, May 18th, 2026 at 04:00 UTC. We expect to complete the maintenance by Monday, May 18th, 2026 at 10:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 14, 2026 - 18:03 UTC

[ICM-4969] Planned Maintenance on the Imperva data center in London 2, UK May 19, 2026 00:00-07:00 UTC

Maintenance on the London 2, UK data center will be performed on Tuesday, May 19th, 2026 at 00:00 UTC. We expect to complete the maintenance by Tuesday, May 19th, 2026 at 07:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 06, 2026 - 04:50 UTC

[ICM-5017] Essential Maintenance on the Imperva data center in Barcelona, Spain May 19, 2026 23:00 - May 20, 2026 07:00 UTC

Maintenance on the Barcelona, Spain data center will be performed on Tuesday, May 19th, 2026 at 23:00 UTC. We expect to complete the maintenance by Wednesday, May 20th, 2026 at 07:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 12, 2026 - 20:42 UTC

[ICM-5015] Essential Maintenance on the Imperva data center in Dallas, TX May 21, 2026 06:00-12:00 UTC

Maintenance on the Dallas, TX data center will be performed on Thursday, May 21st, 2026 at 06:00 UTC. We expect to complete the maintenance by Thursday, May 21st, 2026 at 12:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 14, 2026 - 18:00 UTC

[UM-12996] - Scheduled update to the Cloud Security Console – May 24, 2026 May 24, 2026 13:00-16:00 UTC

The Cloud Security Console will undergo a scheduled update on May 24, 2026, between 13:00 and 16:00 UTC. During this maintenance window, customers may experience intermittent disruptions with the login service to the Management Console or sending API calls.


Customer sites will remain online and protected at all times. We appreciate your understanding and apologize for any inconvenience.

Posted on May 12, 2026 - 12:23 UTC

[ICM-5011] Planned Maintenance on the Imperva data center in Detroit, MI May 25, 2026 04:00-12:00 UTC

Maintenance on the Detroit, MI data center will be performed on Monday, May 25th, 2026 at 04:00 UTC. We expect to complete the maintenance by Monday, May 25th, 2026 at 12:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 11, 2026 - 12:02 UTC

[ICM-5018] Planned Maintenance on the Imperva data center in Johannesburg, South Africa May 25, 2026 23:00 - May 26, 2026 06:00 UTC

Maintenance on the Johannesburg, South Africa data center will be performed on Monday, May 25th, 2026 at 23:00 UTC. We expect to complete the maintenance by Tuesday, May 26th, 2026 at 06:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 13, 2026 - 14:11 UTC

[ICM-5005] Planned Maintenance on the Imperva data center in Bangkok, Thailand May 27, 2026 17:00 - May 28, 2026 01:00 UTC

Maintenance on the Bangkok, Thailand data center will be performed on Wednesday, May 27th, 2026 at 17:00 UTC. We expect to complete the maintenance by Thursday, May 28th, 2026 at 01:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Posted on May 12, 2026 - 20:27 UTC

[ICM-5007] Planned Maintenance on the Imperva data center in Hanoi, Vietnam May 28, 2026 18:00 - May 29, 2026 02:00 UTC

Update - Maintenance on the Hanoi, Vietnam data center will be performed on Thursday, May 28th, 2026 at 18:00 UTC. We expect to complete the maintenance by Friday, May 29th, 2026 at 02:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

May 15, 2026 - 04:44 UTC
Scheduled - Maintenance on the Hanoi, Vietnam data center will be performed on Monday, May 25th, 2026 at 18:00 UTC. We expect to complete the maintenance by Tuesday, May 26th, 2026 at 02:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

May 12, 2026 - 20:26 UTC
May 15, 2026
Resolved - The incident has been resolved and normal service levels have been restored for the Imperva Management Portal.
May 15, 11:42 UTC
Monitoring - The issue has been identified as ISP-related. Technical teams have taken mitigation actions, and we are observing improvements in service performance. Monitoring will continue to ensure stability.
May 15, 09:52 UTC
Update - Technical teams are continuing to actively troubleshoot the issue and are working to restore normal service levels.
The next update on the incident will be shared no later that 09:50 UTC

May 15, 09:21 UTC
Update - The impact has been identified as isolated to the India region. Technical teams are actively investigating the issue and working towards mitigation.
The next update on the incident will be shared no later that 09:22 UTC

May 15, 08:53 UTC
Investigating - We have discovered a potential service degradation, affecting Imperva Management Portal. The Management Portal website is slow to respond to user actions and in some cases user login attempts may also fail. 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.

May 15, 08:17 UTC
Completed - The scheduled maintenance has been completed.
May 15, 03:46 UTC
Update - Maintenance on the Jakarta, Indonesia data center has been extended to Friday, May 15th, 2026 at 04:00 UTC.
May 15, 01:27 UTC
Update - Maintenance on the Jakarta, Indonesia data center has been extended to Friday, May 15th, 2026 at 02:00 UTC.
May 14, 23:32 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 17:00 UTC
Scheduled - Maintenance on the Jakarta, Indonesia data center will be performed on Thursday, May 14th, 2026 at 17:00 UTC. We expect to complete the maintenance by Friday, May 15th, 2026 at 01:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

May 7, 17:18 UTC
Resolved - 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.

May 15, 00:32 UTC
Monitoring - 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.

May 14, 23:55 UTC
Update - Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 23:55 UTC. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that 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.

May 14, 22:55 UTC
Update - Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 22:55 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 14, 21:55 UTC
Update - Our engineers are actively working on the fix to resolve the data center issue. The next Status Update on this Incident will be provided no later than 21:55 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 14, 21:25 UTC
Update - Technical teams are currently investigating the issue and will provide updates as more information becomes available. The next Status Update on this Incident will be provided no later than 21:25 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 14, 20:55 UTC
Identified - We have identified the source of the issue in the data center. Technical teams are working on a fix. The next Status Update on this Incident will be provided no later than 20:51 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 14, 20:21 UTC
Investigating - Technical teams are investigating a potential issue in the New Delhi (NDL), Mumbai (NAG) Data Center. The next Status Update on this Incident will be provided no later than 20:19 UTC. Further updates to follow.
May 14, 19:49 UTC
May 14, 2026
Resolved - The incident has been resolved and normal service levels have been restored for 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.

May 14, 18:28 UTC
Monitoring - Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. 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.

May 14, 17:58 UTC
Investigating - We have discovered a potential service degradation, affecting customers ability to use the Imperva Management Portal. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 17:56 UTC. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 14, 17:26 UTC
Completed - The scheduled maintenance has been completed.
May 14, 07:52 UTC
Update - Maintenance on the Paris, France data center has been extended to Thursday, May 14th, 2026 at 08:00 UTC.
May 14, 05:46 UTC
Update - Maintenance on the Paris, France data center has been extended to Thursday, May 14th, 2026 at 07:00 UTC.
May 14, 04:26 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 23:00 UTC
Scheduled - Maintenance on the Paris, France data center will be performed on Wednesday, May 13rd, 2026 at 23:00 UTC. We expect to complete the maintenance by Thursday, May 14th, 2026 at 05:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

May 7, 03:08 UTC
May 13, 2026
Completed - The scheduled maintenance has been completed.
May 13, 19:51 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 12, 15:00 UTC
Update - Maintenance on the Tokyo, Japan data center will be performed on Tuesday, May 12th, 2026 at 15:00 UTC. We expect to complete the maintenance by Wednesday, May 13rd, 2026 at 19:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

May 7, 03:50 UTC
Scheduled - As part of our commitment to building a future-facing network, Imperva recently launched our Next Generation Architecture in the NRT - Tokyo, Japan PoP with improved capacity, connectivity, and services. This PoP is replacing our currently operational PoP in TKO - Tokyo, Japan. Imperva will be migrating all services and customer traffic from our TKO PoP to our NRT PoP, and decommissioning our TKO PoP during a scheduled maintenance window which will begin at 12-May-2026 15:00, completing by 13-May-2026 19:00.


For Cloud WAF customers, Imperva will reroute traffic to an unaffected PoP in the region for the duration of the maintenance, with no expected interruption to Cloud WAF services. At the end of the maintenance, traffic will be serviced by the new PoP. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via an alternate connection such as GRE tunnels or Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. At the end of the maintenance, DDoS Protection traffic will be serviced by the new PoP. If Performance Monitoring is enabled on the connections, you will notice a change in the IP address of the PM servers that are sending ICMP echo messages. This might require you to modify ACL/firewall configurations to allow ICMP traffic from the new IPs. To learn more, see https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/performance-monitoring.htm

May 4, 18:03 UTC
Completed - The scheduled maintenance has been completed.
May 13, 07:36 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 13, 03:00 UTC
Scheduled - Maintenance on the Sao Paulo, Brazil data center will be performed on Wednesday, May 13rd, 2026 at 03:00 UTC. We expect to complete the maintenance by Wednesday, May 13rd, 2026 at 11:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Apr 29, 09:11 UTC
Resolved - We have discovered a service degradation that affected the EZE PoP which may have resulted in customers experiencing impact for Imperva Cloud WAF and DDoS for Networks traffic routed through the EZE PoP. Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts. Services has been restored for EZE PoP.
May 13, 01:57 UTC
May 12, 2026
Resolved - The incident has been resolved and normal service levels have been restored for 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.

May 12, 12:15 UTC
Monitoring - Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. 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.

May 12, 11:23 UTC
Investigating - We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow.

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.

May 12, 10:56 UTC
Resolved - We have identified ISP-related connectivity issues in the Vancouver region which affected traffic at 07:03 UTC - 07:21 UTC that may have impacted Imperva Cloud WAF and DDoS for Networks traffic routed through the VAN PoP.

Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts.

May 12, 07:49 UTC
May 11, 2026
Resolved - Monitoring has confirmed that the issue has been resolved, and all services are operating normally.
May 11, 14:22 UTC
Update - The Ashburn, VA (IAD) PoP is now online. Teams will continue to monitor closely to ensure service stability.
May 11, 12:39 UTC
Update - Pre-checks have been completed, and the PoP is expected to be brought back online within the next 15 minutes.
The next update will be shared once the PoP is fully online.

May 11, 12:29 UTC
Update - The issue has been mitigated. We are currently in the process of activating the Ashburn, VA (IAD) PoP. Pre-checks are being completed as part of the restoration, and traffic will be gradually restored.
The next update will be provided once the PoP is ready to be brought online.

May 11, 12:03 UTC
Update - The PoP remains deactivated , with traffic continuing to be routed through alternate data centers in the region to ensure service continuity. We are closely monitoring the environment. Further updates to follow.
May 11, 10:44 UTC
Update - The PoP is still deactivated and traffic is being rerouted through an alternate data center in the region. We are continuing to monitor the PoP before bringing it up again.
May 11, 07:51 UTC
Update - Technical teams have performed remedial actions and still monitoring the results.
May 11, 06:47 UTC
Update - We are continuing to monitor for any further issues.
May 11, 05:46 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 11, 04:43 UTC
Update - The PoP remains deactivated while the team is working in restoring connectivity within the PoP. 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.
May 11, 03:47 UTC
Identified - We have identified an issue in the data center and the PoP has been deactivated for now. 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.
May 11, 02:48 UTC
Update - Technical teams are still working on restoring connectivity within the PoP. The next Status Update on this Incident will be provided no later than 03:17 UTC.
May 11, 02:15 UTC
Update - Technical teams are continuing to investigate. The next Status Update on this Incident will be provided no later than 02:17 UTC.
May 11, 01:43 UTC
Update - We are continuing to investigate. The next Status Update on this Incident will be provided no later than 01:47 UTC.
May 11, 01:25 UTC
Investigating - Technical teams are investigating a potential issue in the Ashburn, VA (IAD) 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.

May 11, 00:47 UTC
Resolved - The issue affecting the Cloud WAF Dashboards component has been resolved. All systems are operating normally.
May 11, 08:33 UTC
Monitoring - A fix has been implemented for the issue impacting the Cloud WAF Dashboards component. The issue has been mitigated, and the team is actively monitoring to ensure continued stability.
May 11, 07:26 UTC
Update - Our technical teams are actively working to resolve the issue and will share updates as progress is made.
The next Status Update on this Incident will be provided no later than 07:52 UTC.

May 11, 07:22 UTC
Update - We have narrowed the issue down to the “WAF Sessions by Country” component in the Security dashboard, which is not functioning as expected. The technical teams are actively working on a fix.

The next Status Update on this Incident will be provided no later than 07:26 UTC.

May 11, 06:56 UTC
Investigating - We have discovered a potential service degradation, affecting the Imperva Management Portal. One or more Cloud WAF Dashboards are not responding or returning errors. Customer domains are still fully protected at this time. Technical teams are investigating. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 11, 06:32 UTC
May 10, 2026
Completed - The scheduled maintenance has been completed.
May 10, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 10, 13:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Apr 12, 18:42 UTC
Scheduled - The Cloud Security Console will undergo a scheduled update on May 10, 2026, between 13:00 and 17:00 UTC. During this maintenance window, customers may experience delays when applying configuration changes.

Please note that no changes will be lost - all updates will be applied as soon as possible.

Customer sites will remain online and protected at all times. We appreciate your understanding and apologize for any inconvenience.

Apr 9, 08:19 UTC
Resolved - Monitoring has confirmed that services are stable, and the 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.

May 10, 16:21 UTC
Update - We are continuing to monitor for any further issues.
May 10, 15:02 UTC
Monitoring - Technical teams have performed remedial actions and services are 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.

May 10, 14:54 UTC
Investigating - A third-party internet service provider is currently experiencing an issue resulting in degradation of CWAF and Network DDoS services. Customers may experience elevated latency or, in some cases, temporary loss of availability for CWAF-protected sites. This impact includes CloudWAF customers using Origin POP and Network DDoS customers utilizing Mesh. Customer websites remain fully protected during this time.

The next Status Update on this Incident will be provided no later than 14:05 UTC.

May 10, 13:35 UTC
Resolved - The incident has been resolved and normal service levels have been restored for 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.

May 10, 13:28 UTC
Monitoring - Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Further updates to follow.The next Status Update on this Incident will be provided no later than 14:02 UTC.
May 10, 13:01 UTC
Identified - We have identified the issue causing intermittent issues with loading various pages on the Imperva Management Console, as well as impacting Imperva APIs. The team is actively working on remediation
The next Status Update on this Incident will be provided no later than 13:06 UTC.

May 10, 12:36 UTC
Update - Investigations indicate that the scope of the impact also includes Imperva APIs, in addition to intermittent issues loading various pages on the Management Console. Technical teams continue to investigate.
The next Status Update on this Incident will be provided no later than 12:54 UTC.

May 10, 12:24 UTC
Investigating - We have discovered a potential service degradation, affecting intermittent issues loading various pages on the Management Console. 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.

May 10, 12:10 UTC
May 9, 2026

No incidents reported.

May 8, 2026
Resolved - The incident has been successfully resolved, and all services are operating normally.

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.

May 8, 21:13 UTC
Monitoring - A fix has been implemented and we are monitoring the results. The next Status Update on this Incident will be provided no later than 21:30 UTC. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 8, 21:01 UTC
Update - The issue has been identified, and remediation efforts are currently underway. The next Status Update on this Incident will be provided no later than 20:45 UTC. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 8, 20:16 UTC
Update - The issue has been identified and a fix is being implemented. The next Status Update on this Incident will be provided no later than 20:10 UTC. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 8, 19:42 UTC
Identified - We have discovered a potential issue affecting FP on browser classification. Technical teams are investigating. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 8, 19:37 UTC
Completed - The scheduled maintenance has been completed.
May 8, 08:32 UTC
Update - Maintenance on the Istanbul, Turkey data center has been extended to Friday, May 8th, 2026 at 09:00 UTC.
May 8, 05:33 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 7, 22:00 UTC
Scheduled - Maintenance on the Istanbul, Turkey data center will be performed on Thursday, May 7th, 2026 at 22:00 UTC. We expect to complete the maintenance by Friday, May 8th, 2026 at 06:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Apr 28, 13:34 UTC
Resolved - The incident has been resolved and normal service levels have been restored for the Cloud WAF Dashboards on the Imperva Management Portal.
May 8, 05:45 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 8, 05:37 UTC
Identified - The issue has been identified and a fix is being implemented.
May 8, 05:19 UTC
Update - The technical teams are still working on the recovery for the Imperva Management Portal dashboard issue. The next status update on this incident will be provided no later than 05:28 UTC.
May 8, 04:26 UTC
Update - Technical teams are continuing to work on a fix for the Imperva Management Portal dashboard issue. The next status update on this incident will be provided no later than 04:28 UTC.
May 8, 03:57 UTC
Update - We are continuing to investigate. The next Status Update on this Incident will be provided no later than 3:58 UTC.
May 8, 03:36 UTC
Investigating - We have discovered a potential service degradation, affecting Imperva Management Portal. The dashboards may not be not displaying the latest data. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 3:28 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 8, 02:57 UTC
May 7, 2026
Completed - The scheduled maintenance has been completed.
May 7, 03:57 UTC
Update - Maintenance on the Amsterdam, Netherlands data center has been extended to Thursday, May 7th, 2026 at 04:00 UTC.
May 7, 01:07 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 22:00 UTC
Scheduled - As part of our commitment to building a future-facing network, Imperva recently launched our Next Generation Architecture in the RTM - Amsterdam, Netherlands PoP with improved capacity, connectivity, and services. This PoP is replacing our currently operational PoP in AMS - Amsterdam, Netherlands. Imperva will be migrating all services and customer traffic from our AMS PoP to our RTM PoP, and decommissioning our AMS PoP during a scheduled maintenance window which will begin at 05-May-2026 22:00, completing by 07-May-2026 02:00.

For Cloud WAF customers, Imperva will reroute traffic to an unaffected PoP in the region for the duration of the maintenance, with no expected interruption to Cloud WAF services. At the end of the maintenance, traffic will be serviced by the new PoP. DDoS Protection for Networks customers must ensure that the advertisement of their ranges via an alternate connection such as GRE tunnels or Cross-Connects is in place prior to the start of maintenance to avoid interruption of service. At the end of the maintenance, DDoS Protection traffic will be serviced by the new PoP. If Performance Monitoring is enabled on the connections, you will notice a change in the IP address of the PM servers that are sending ICMP echo messages. This might require you to modify ACL/firewall configurations to allow ICMP traffic from the new IPs. To learn more, see https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/performance-monitoring.htm

Apr 30, 08:10 UTC
May 6, 2026
Resolved - The issue has been resolved, and monitoring has confirmed service stability.
May 6, 15:04 UTC
Monitoring - A fix has been implemented, and services have returned to normal. We are continuing to monitor the situation closely to ensure stability.
The next Status Update on this Incident will be provided no later than 15:04 UTC.

May 6, 14:04 UTC
Update - We are actively investigating this issue and continuing our efforts to identify the cause of the issue.
The next Status Update on this Incident will be provided no later than 14:13 UTC.

May 6, 13:43 UTC
Update - We are continuing to actively investigate this issue.
The next Status Update on this Incident will be provided no later than 13:39 UTC.

May 6, 13:10 UTC
Investigating - Our investigation has determined that the previously suspected cause may be one contributing factor within a broader underlying root-cause pattern than initially identified. We are continuing to investigate and actively working to identify the underlying cause.

The next Status Update on this Incident will be provided no later than 13:11 UTC.

May 6, 12:41 UTC
Update - We are continuing to actively work on implementing a fix.
The next Status Update on this Incident will be provided no later than 12:55 UTC.

May 6, 12:25 UTC
Identified - We have identified the issue, and a fix is currently being implemented.

The next Status Update on this Incident will be provided no later than 12:22 UTC.

May 6, 11:53 UTC
Investigating - We are investigating a potential issue impacting Cloud WAF Protected Websites. Some websites may fail to load or return errors. Customer domains remain fully protected at this time. Our technical teams are actively working to identify the root cause, and further updates will be shared as more information becomes available.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a 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.

May 6, 11:36 UTC
May 5, 2026
Completed - The scheduled maintenance has been completed.
May 5, 05:57 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 00:00 UTC
Scheduled - Maintenance on the Paris, France data center will be performed on Tuesday, May 5th, 2026 at 00:00 UTC. We expect to complete the maintenance by Tuesday, May 5th, 2026 at 06:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Apr 27, 06:34 UTC
Completed - The scheduled maintenance has been completed.
May 5, 00:37 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 4, 17:00 UTC
Scheduled - Maintenance on the Jakarta, Indonesia data center will be performed on Monday, May 4th, 2026 at 17:00 UTC. We expect to complete the maintenance by Tuesday, May 5th, 2026 at 01:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Apr 27, 17:17 UTC
May 4, 2026
May 3, 2026
Resolved - 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.

May 3, 16:28 UTC
Monitoring - The incident has been resolved, and all services have returned to normal operating levels. We will continue to monitor the situation closely.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 3, 15:28 UTC
Update - The team has resolved the Security Events page issue on the Management Platform; however, Attack Analytics, threat alert emails, and SIEM integrations may still be impacted. The next Status Update on this Incident will be provided no later than 15:36 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

May 3, 15:06 UTC
Update - Technical teams are continuing to work on a fix the issue. The next status update on this incident will be provided no later than 15:03 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 3, 14:33 UTC
Update - Team are actively working to mitigate the issue. The next Status Update on this Incident will be provided no later than 14:33 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region

May 3, 14:03 UTC
Update - The teams have identified a component potentially causing the issue. They are currently working to mitigate it. The next Status Update on this Incident will be provided no later than 14:00 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 3, 13:30 UTC
Update - Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 13:30 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

May 3, 13:02 UTC
Update - During the course of the investigation our teams found that the issue also affects ABP and Attack Analytics log delivery via SIEM solution in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 13:00 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and 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.

May 3, 12:31 UTC
Identified - During the course of the investigation our teams found that the issue also affects the Attack Analytics and Security log delivery via SIEM solution in the APAC region. The next status update on this incident will be provided no later than 12:27 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 3, 11:57 UTC
Investigating - Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 12:18 UTC.

The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

In the event of a service disruption, the update will include potential impacts to any affected region.

May 3, 11:49 UTC
Identified - We have identified the source of the service degradation affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 11:48 AM UTC. Further updates to follow.

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.

May 3, 11:18 UTC
Investigating - We have discovered a potential service degradation, affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Further updates to follow.

The status updates are an integral part of proactive monitoring and transparent 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.

May 3, 10:48 UTC
May 2, 2026

No incidents reported.

May 1, 2026
Completed - The scheduled maintenance has been completed.
May 1, 23:54 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 1, 17:00 UTC
Scheduled - Maintenance on the Singapore data center will be performed on Friday, May 1st, 2026 at 17:00 UTC. We expect to complete the maintenance by Saturday, May 2nd, 2026 at 01:00 UTC.
For Cloud WAF customers, Imperva will reroute traffic to the closest data center for the duration of the maintenance, with no expected interruption of Cloud WAF services.
DDoS Protection for Networks customers must ensure that the advertisement of their ranges via alternate connection such as GRE tunnels and Cross-Connects is in place prior to the start of maintenance to avoid interruption of service.
The link to Imperva's documentation can be found here: https://docs.imperva.com/bundle/cloud-application-security/page/network-ddos/maintenance-prep.htm

Apr 30, 13:25 UTC