All Systems Operational

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 (XSP) 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 Operational
Cloud Security Management Platform Operational
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 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

[ICM-5078] Planned Maintenance on the Imperva data center in Mumbai, India Jun 11, 2026 20:00 - Jun 12, 2026 04:00 UTC

Maintenance on the Mumbai, India data center will be performed on Thursday, June 11th, 2026 at 20:00 UTC. We expect to complete the maintenance by Friday, June 12th, 2026 at 04: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 27, 2026 - 19:57 UTC

[ICM-5009 / ICM-5095] Planned Maintenance on the Imperva data center in Jakarta, Indonesia Jun 16, 2026 17:00 - Jun 17, 2026 03:00 UTC

Update - We will be undergoing scheduled maintenance during this time.
Jun 08, 2026 - 22:27 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jun 04, 2026 - 17:58 UTC
Scheduled - Maintenance on the Jakarta, Indonesia data center will be performed on Tuesday, June 16th, 2026 at 16:00 UTC. We expect to complete the maintenance by Wednesday, June 17th, 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

Jun 04, 2026 - 17:24 UTC

[ICM-5108] Planned Maintenance on the Imperva data center in Barcelona, Spain Jun 17, 2026 22:00 - Jun 18, 2026 08:00 UTC

Update - Maintenance on the Barcelona, Spain data center will be performed on Wednesday, June 17th, 2026 at 22:00 UTC. We expect to complete the maintenance by Thursday, June 18th, 2026 at 08: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

Jun 09, 2026 - 01:03 UTC
Scheduled - Maintenance on the Barcelona, Spain data center will be performed on Wednesday, June 17th, 2026 at 23:00 UTC. We expect to complete the maintenance by Thursday, June 18th, 2026 at 08: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

Jun 03, 2026 - 07:51 UTC
Jun 10, 2026
Completed - The scheduled maintenance has been completed.
Jun 10, 11:37 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 10, 02:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jun 4, 21:20 UTC
Scheduled - Maintenance on the Ashburn, VA data center will be performed on Wednesday, June 10th, 2026 at 02:00 UTC. We expect to complete the maintenance by Wednesday, June 10th, 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

Jun 2, 19:56 UTC
Completed - The scheduled maintenance has been completed.
Jun 10, 05:11 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 9, 23:00 UTC
Scheduled - Maintenance on the Dusseldorf, Germany data center will be performed on Tuesday, June 9th, 2026 at 23:00 UTC. We expect to complete the maintenance by Wednesday, June 10th, 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

May 28, 06:16 UTC
Jun 9, 2026
Completed - The scheduled maintenance has been completed.
Jun 9, 11:43 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 9, 06:00 UTC
Scheduled - Maintenance on the San Jose, CA data center will be performed on Tuesday, June 9th, 2026 at 06:00 UTC. We expect to complete the maintenance by Tuesday, June 9th, 2026 at 14: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 27, 13:05 UTC
Completed - The scheduled maintenance has been completed.
Jun 9, 09:19 UTC
Update - Maintenance on the London 2, UK data center has been extended to Tuesday, June 9th, 2026 at 10:00 UTC.
Jun 9, 08:16 UTC
Update - Maintenance on the London 2, UK data center has been extended to Tuesday, June 9th, 2026 at 09:00 UTC.
Jun 9, 06:17 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 8, 23:00 UTC
Scheduled - Maintenance on the London 2, UK data center will be performed on Monday, June 8th, 2026 at 23:00 UTC. We expect to complete the maintenance by Tuesday, June 9th, 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

Jun 2, 10:12 UTC
Completed - The scheduled maintenance has been completed.
Jun 9, 03:49 UTC
Update - Maintenance on the Hong Kong data center has been extended to Tuesday, June 9th, 2026 at 04:00 UTC.
Jun 9, 00:51 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 8, 16:00 UTC
Scheduled - Maintenance on the Hong Kong data center will be performed on Monday, June 8th, 2026 at 16:00 UTC. We expect to complete the maintenance by Tuesday, June 9th, 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

Jun 1, 14:28 UTC
Jun 8, 2026
Completed - The scheduled maintenance has been completed.
Jun 8, 09:45 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 8, 06:00 UTC
Scheduled - Maintenance on the Los Angeles, CA data center will be performed on Monday, June 8th, 2026 at 06:00 UTC. We expect to complete the maintenance by Monday, June 8th, 2026 at 14: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 27, 13:16 UTC
Jun 7, 2026
Completed - The scheduled maintenance has been completed.
Jun 7, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 7, 08:00 UTC
Scheduled - The Network Protection will undergo a scheduled update on June 7, 2026, between 08:00 and 09:00 UTC.
During this maintenance window, the Network DDoS dashboards may be temporarily unavailable.
Customer network ranges will remain online and protected at all times.
We appreciate your understanding and apologize for any inconvenience.

Jun 1, 16:34 UTC
Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026
Completed - The scheduled maintenance has been completed.
Jun 4, 20:53 UTC
Verifying - Verification is currently underway for the maintenance items.
Jun 4, 20:47 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 4, 17:00 UTC
Scheduled - Maintenance on the Taipei, Taiwan data center will be performed on Thursday, June 4th, 2026 at 17:00 UTC. We expect to complete the maintenance by Friday, June 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

May 27, 19:50 UTC
Resolved - The technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. The PoP is fully operational and ready for service.
We appreciate your patience and understanding throughout this incident.

Jun 4, 06:30 UTC
Update - The technical team identified and resolved an unexpected issue affecting range advertisements. Continuous monitoring is underway to validate service stability and will confirm full operational readiness of the PoP. The PoP is now active, and traffic has been restored to the EWR data center. The next Status Update on this Incident will be provided no later than 06:31 UTC.
Jun 4, 06:01 UTC
Monitoring - Technical team has successfully activated the PoP, and traffic has been restored to the EWR data center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. The next Status Update on this Incident will be provided no later than 06:01 UTC.
Jun 4, 05:00 UTC
Update - A fix has been implemented, and traffic has been restored to the data center. We are continuing to monitor to ensure that service has returned to normal.
The next update will be provided no later than 05:01 UTC.

Jun 4, 04:31 UTC
Update - The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.
Jun 3, 11:01 UTC
Update - The EWR PoP has remained stable during this monitoring period, and is currently scheduled for activation during the local off-peak period on 04-Jun-2026 04:00 UTC. Until that time, customer traffic will continue to be serviced by alternative PoPs.
May 30, 15:19 UTC
Update - Technical teams have identified and remediated the underlying issue. As a precautionary measure, the EWR PoP will remain bypassed while monitoring continues. An estimated timeline for reactivation will be provided shortly.
May 29, 23:41 UTC
Identified - The technical teams have localized the problem and addressed it. The EWR PoP will remain bypassed until a scheduled maintenance window of 0400 to 0800 UTC on 1 June 2026.
The next update will be provided following the reactivation of the EWR PoP.

May 29, 22:46 UTC
Update - Our Network Engineering teams remain actively engaged in investigating and mitigating the connectivity issues impacting the New York 2, NY (EWR) data center.

The next update will be provided no later than 22:34 UTC.

May 29, 21:34 UTC
Update - Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center.

The next update will be provided no later than 21:20 UTC.

May 29, 20:20 UTC
Update - We are still investigating an issue affecting one of our points of presence (EWR), which may cause intermittent connectivity or latency.
Traffic has been rerouted through alternate locations to maintain service continuity while our teams continue working toward resolution.

Next update will be shared no later then 20:07 UTC.

May 29, 19:37 UTC
Update - The investigation is still ongoing, with multiple technical teams actively reviewing available data and evaluating possible contributing factors. At this stage, there are no major developments to report, and troubleshooting activities continue.

Customer traffic remains routed through alternate regional PoPs to maintain service continuity while mitigation efforts and root cause analysis are in progress.

Next update will be shared no later then 19:26 UTC.

May 29, 18:26 UTC
Update - Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active.
Customer traffic continues to be served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed.
Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information becomes available.

The next update on the incident will be shared no later than 18:25 UTC.

May 29, 17:28 UTC
Update - Investigation remains ongoing, with multiple technical teams continuing to analyze the available data and assess potential contributing factors. At this time, there are no significant changes to report, and troubleshooting efforts remain active.
Customer traffic continues to be served through alternate PoPs in the region to help maintain service continuity while root cause and mitigation activities proceed.
Technical teams are actively working to identify the underlying cause of the issue. Further updates will be provided as additional information becomes available.

The next update on the incident will be shared no later than 18:25 UTC.

May 29, 17:25 UTC
Update - The investigation remains ongoing, with multiple technical teams continuing to analyze the available data and evaluate potential contributing factors. Customer traffic continues to be served through alternate PoPs in the region to maintain service continuity while troubleshooting efforts and root cause analysis proceed.
The next update on the incident will be shared no later than 17:25 UTC.

May 29, 16:25 UTC
Update - The investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting. Customer traffic continues to be served through an alternate PoP in the region to minimize impact while investigation and mitigation efforts continue.
The next update on the incident will be shared no later than 16:27 UTC.

May 29, 15:27 UTC
Update - Investigation remains ongoing, with multiple technical teams actively engaged in troubleshooting and analysis efforts. Teams are also investigating a recent increase in anomalous traffic to determine whether it is contributing to the observed behavior. Traffic continues to be rerouted through an alternate data center in the region to minimize customer impact while the root cause is being identified.
The next update on the incident will be shared no later than 15:28 UTC.

May 29, 14:29 UTC
Update - We continue to investigate the issue affecting the data center. Traffic remains rerouted through an alternate data center in the region while troubleshooting efforts are ongoing.
The next update on the incident will be shared no later than 14:25 UTC.

May 29, 13:56 UTC
Investigating - We are investigating an issue in the New York 2, NY (EWR) 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 next update on the incident will be shared no later than 13:55 UTC.

May 29, 13:24 UTC
Completed - The scheduled maintenance has been completed.
Jun 4, 03:18 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 22:00 UTC
Scheduled - Maintenance on the Paris, France data center will be performed on Wednesday, June 3rd, 2026 at 22:00 UTC. We expect to complete the maintenance by Thursday, June 4th, 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

May 26, 17:14 UTC
Jun 3, 2026
Completed - The scheduled maintenance has been completed.
Jun 3, 20:38 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 17:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
May 26, 03:12 UTC
Scheduled - As part of our commitment to building a future-facing network, Imperva recently launched our Next Generation Architecture in the XSP - Singapore PoP with improved capacity, connectivity, and services. This PoP is replacing our currently operational PoP in SIN – Singapore. Imperva will be migrating all services and customer traffic from our SIN PoP to our XSP PoP, and decommissioning our SIN PoP during a scheduled maintenance window which will begin at June 2nd, 2026 at 17:00 UTC, completing by June 3rd, 2026 at 21:00 UTC.

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 25, 01:42 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.

Jun 3, 14:55 UTC
Monitoring - A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. Next update will be shared no later than 14:56 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.

Jun 3, 14:25 UTC
Investigating - Technical teams are continuing to working on a fix for the data center issue. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Next update will be shared no later than 14:30 UTC.

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

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

Jun 3, 13:59 UTC
Identified - We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. Next update will be shared 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.

Jun 3, 13:29 UTC
Completed - This maintenance will be rescheduled.
Jun 3, 13:56 UTC
Scheduled - Maintenance on the Jakarta, Indonesia data center will be performed on Wednesday, June 3rd, 2026 at 17:00 UTC. We expect to complete the maintenance by Thursday, June 4th, 2026 at 03: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 26, 15:16 UTC
Completed - The scheduled maintenance has been completed.
Jun 3, 12:57 UTC
Update - Maintenance on the Sao Paulo, Brazil data center has been extended to Wednesday June 3rd, 2026 at 13:00 UTC.
Jun 3, 11:37 UTC
Update - Maintenance on the Sao Paulo, Brazil data center has been extended to Monday, April 6th, 2026 at 12:00 UTC.
Jun 3, 10:17 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 03:00 UTC
Scheduled - Maintenance on the Sao Paulo, Brazil data center will be performed on Wednesday, June 3rd, 2026 at 03:00 UTC. We expect to complete the maintenance by Wednesday, June 3rd, 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

May 26, 19:11 UTC
Resolved - The incident has been resolved and normal service levels have been restored for the 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.

Jun 3, 09:40 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. Next update will be shared no later than 09:42 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.

Jun 3, 09:11 UTC
Identified - We have identified the source of the service degradation causing slowness on the Management Platform and
customers accessing onboarded sites from the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Next update will be shared no later then 09: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.

Jun 3, 08:59 UTC
Investigating - We are currently investigating an issue causing slowness on the Management Platform and
Customers accessing onboarded sites from the APAC region may experience intermittent latency or delays when reaching their protected websites.
Our teams are actively investigating the cause and working to restore normal service performance. We will provide additional updates as more information becomes available.

Next update will be shared no later then 09:00 UTC.

Jun 3, 08:36 UTC
Completed - The scheduled maintenance has been completed.
Jun 3, 05:46 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 22:00 UTC
Scheduled - Maintenance on the Barcelona, Spain data center will be performed on Tuesday, June 2nd, 2026 at 22:00 UTC. We expect to complete the maintenance by Wednesday, June 3rd, 2026 at 08: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 19, 09:00 UTC
Jun 2, 2026
Jun 1, 2026

No incidents reported.

May 31, 2026
Completed - The scheduled maintenance has been completed.
May 31, 15:49 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 31, 13:00 UTC
Scheduled - The Cloud Security Console will undergo a scheduled update on May 31, 2026 (postponed from May 24, 2026) between 13:00 and 17: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.

May 25, 08:59 UTC
May 30, 2026
Completed - The scheduled maintenance has been completed.
May 30, 13:56 UTC
Update - Maintenance on the Lima, Peru data center has been extended to Saturday, May 30th, 2026 at 14:00 UTC.
May 30, 12:34 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 30, 03:00 UTC
Scheduled - Maintenance on the Lima, Peru data center will be performed on Saturday, May 30th, 2026 at 03:00 UTC. We expect to complete the maintenance by Saturday, May 30th, 2026 at 13: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 30, 01:06 UTC
May 29, 2026
Resolved - Service in the data center has been restored to normal.
May 29, 12:01 UTC
Monitoring - A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal.
The next update will be provided no later than 12:00 UTC.

May 29, 10:57 UTC
Identified - The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP.
The next update will be provided no later than 10:46 UTC.

May 29, 10:16 UTC
Update - Investigation is ongoing. Technical teams continue to analyze the issue and validate findings. Customer traffic continues to be served normally through an alternate PoP.
Next update will be shared no later then 10:18 UTC.

May 29, 09:48 UTC
Update - The investigation is ongoing, and technical teams continue to actively troubleshoot and analyze the issue to determine the underlying cause.
Next update will be shared no later then 09:42 UTC.

May 29, 09:12 UTC
Investigating - During monitoring, the team identified some abnormalities in the network. The engineering team is currently re-investigating the issue, and traffic is being re-routed to an alternate data center.

Next update will be shared no later then 09:11 UTC.

May 29, 08:41 UTC
Monitoring - A fix has been implemented, and customer traffic continues to be served normally through the New York 2, NY (EWR) PoP.

We will continue to monitor the situation to ensure that service remains 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 29, 07:25 UTC
Update - The technical teams have identified an issue affecting the New York 2, NY (EWR) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP.

Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

May 28, 21:54 UTC
Update - As a precautionary measure, the New York 2, NY (EWR) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time.

Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.

May 28, 20:17 UTC
Update - Our Network Engineers continue to work on resolving the connectivity issues affecting the New York 2, NY (EWR) data center.

The next update will be provided no later than 20:00 UTC.

May 28, 19:30 UTC
Update - We have identified intermittent connectivity issues affecting the New York 2, NY (EWR) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center.

The next update will be provided no later than 19:27 UTC.

May 28, 18:57 UTC
Update - We have identified connectivity issues affecting our New York 2, NY (EWR) data center. Traffic is currently being re-routed to an alternate data center to minimize customer impact.

The next update will be provided no later than 18:53 UTC.

May 28, 18:23 UTC
Identified - We have identified connectivity issues in our New York 2, NY (EWR). traffic is being re-routed to an alternate data-center.

Next update will be shared no later then 18:37.

May 28, 18:09 UTC
Resolved - Service in the data center has been restored to normal.
May 29, 11:05 UTC
Monitoring - A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal.
The next update will be provided no later than 11:18 UTC.

May 29, 10:18 UTC
Update - The technical teams have identified an issue affecting the Vancouver, Canada (VAN) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP.

Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

May 28, 21:55 UTC
Update - As a precautionary measure, the Vancouver, Canada (VAN) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time.

Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.

May 28, 20:44 UTC
Update - We have identified intermittent connectivity issues affecting the Vancouver, Canada (VAN) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center.

The next update will be provided no later than 20:24 UTC.

May 28, 19:54 UTC
Update - We have identified connectivity issues in our Vancouver, Canada (VAN) data center. Traffic is being re-routed to an alternate data center.

The next update will be provided no later than 19:54 UTC.

May 28, 19:24 UTC
Identified - We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center.

The next update will be provided no later than 19:38 UTC.

May 28, 19:08 UTC
Completed - The scheduled maintenance has been completed.
May 29, 09:27 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 29, 01:00 UTC
Scheduled - Maintenance on the Ashburn, VA data center will be performed on Friday, May 29th, 2026 at 01:00 UTC. We expect to complete the maintenance by Friday, May 29th, 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

May 22, 11:02 UTC
May 28, 2026
Completed - The scheduled maintenance has been completed.
May 28, 23:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 18: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, 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, 20:26 UTC
Completed - The scheduled maintenance has been completed.
May 28, 11:59 UTC
Update - Maintenance on the Atlanta, GA data center has been extended to Thursday, May 28th, 2026 at 12:00 UTC.
May 28, 10:53 UTC
Update - Maintenance on the Atlanta, GA data center has been extended to Thursday, May 28th, 2026 at 11:00 UTC.
May 28, 09:53 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 04:00 UTC
Scheduled - Maintenance on the Atlanta, GA data center will be performed on Thursday, May 28th, 2026 at 04:00 UTC. We expect to complete the maintenance by Thursday, May 28th, 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

May 26, 07:24 UTC
Completed - The scheduled maintenance has been completed.
May 28, 03:49 UTC
Update - Maintenance on the Bangkok, Thailand data center has been extended to Thursday, May 28th, 2026 at 04:00 UTC.
May 28, 02:54 UTC
Update - Maintenance on the Bangkok, Thailand data center has been extended to Thursday, May 28th, 2026 at 03:00 UTC.
May 28, 00:51 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 27, 17:00 UTC
Scheduled - 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

May 12, 20:27 UTC
May 27, 2026
Resolved - No abnormalities were observed during the monitoring period. The incident has been resolved, and normal service levels have been fully restored for the Imperva Advanced Bot Protection service.
May 27, 22:52 UTC
Update - The technical team remains in the monitoring phase to ensure service stability and confirm that the issue does not recur.

The next update will be shared no later then 22:53 UTC.

May 27, 22:23 UTC
Monitoring - Technical teams have implemented mitigation measures and the ABP dashboards are now operating normally. Teams will continue to closely monitor the environment, and further updates will be shared as they become available.
May 27, 20:47 UTC
Update - Investigation and remediation activities are currently in progress, with engineering teams actively working to identify the root cause and restore service stability.

Next update will be shared no later then 20:33 UTC.

May 27, 20:04 UTC
Investigating - We have discovered a potential service degradation, affecting some ABP dashboards. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. Further updates to follow.

Next update will be shared no later then 19:52 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 27, 19:22 UTC