Imperva Status

Service Under Maintenance

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 (AMS) 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 (FRA) 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 (TKO) Operational

Imperva for Google Cloud (IGC) Regions - new category (starting Feb 22,2026) Operational

us-east1 region Operational

us-east4 region Operational

us-east5 region Operational

us-central1 region Operational

europe-west1 region Operational

Services - this category will be deprecated on March 22, 2026 Operational

Imperva Management Portal UI - (service will be deprecated on March 22, 2026) Operational

Imperva Management Portal API - (service will be deprecated on March 22, 2026) Operational

Imperva Management Portal- Configuration Changes - (service will be deprecated on March 22, 2026) Operational

Cloud WAF Network - (service will be deprecated on March 22, 2026) Operational

IP Protection - (service will be deprecated on March 22, 2026) Operational

Advanced Bot Protection - (service will be deprecated on March 22, 2026) Operational

Account Take Over - (service will be deprecated on March 22, 2026) Operational

DNS Protection - (service will be deprecated on March 22, 2026) Operational

JSONAR - (service will be deprecated on March 22, 2026) Operational

Client-Side Protection - (service will be deprecated on March 22, 2026) Operational

Cloud WAF GDPR - (service will be deprecated on March 22, 2026) Operational

Cloud WAF SIEM - (service will be deprecated on March 22, 2026) Operational

Cloud WAF Events & Statistics - (service will be deprecated on March 22, 2026) Operational

Attack Analytics - (service will be deprecated on March 22, 2026) Operational

Cloud Data Security - (service will be deprecated on March 22, 2026) Operational

Runtime Application Self Protection - (service will be deprecated on March 22, 2026) Operational

API Security - (service will be deprecated on March 22, 2026) Operational

Imperva Support - Ticketing and Phone Systems Operational

Weblogs - (service will be deprecated on March 22, 2026) Operational

Network DDoS - (service will be deprecated on March 22, 2026) Operational

Protection Services - new category (starting Feb 22,2026) Operational

Cloud WAF Protection Operational

Web Application Performance Operational

IGC WAF Protection Operational

Cloud L7 DDoS Protection 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 - new category (starting Feb 22,2026) 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 - new category (starting Feb 22,2026) Operational

Support Ticketing System Operational

Support Phone Systems Operational

Documentation Portal Operational

Third Party Services Operational

Coming Soon Under Maintenance

Tokyo, Japan (NRT) - April 2026 Under Maintenance

Amsterdam, Netherlands (RTM) - April 2026 Under Maintenance

Frankfurt, Germany (HHN) - May 2026 Under Maintenance

Singapore (XSP) - May 2026 Under Maintenance

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

[ICM-4686] Planned Maintenance on the Imperva data center in Sao Paulo, Brazil Mar `9`, `2026` `04:00`-`10:00` UTC

Maintenance on the Sao Paulo, Brazil data center will be performed on Monday, March 9th, 2026 at 04:00 UTC. We expect to complete the maintenance by Monday, March 9th, 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 Feb 26, 2026 - 17:07 UTC

[ICM-4688] Planned Maintenance on the Imperva data center in Hong Kong Mar `9`, `2026` `17:00` - Mar `10`, `2026` `01:00` UTC

Maintenance on the Hong Kong data center will be performed on Monday, March 9th, 2026 at 17:00 UTC. We expect to complete the maintenance by Tuesday, March 10th, 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 Feb 26, 2026 - 21:02 UTC

[ICM-4687] Planned Maintenance on the Imperva data center in New York, NY Mar `11`, `2026` `03:00`-`09:00` UTC

Maintenance on the New York, NY data center will be performed on Wednesday, March 11th, 2026 at 03:00 UTC. We expect to complete the maintenance by Wednesday, March 11th, 2026 at 09: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 Feb 26, 2026 - 17:06 UTC

[ICM-4694] Planned Maintenance on the Imperva data center in Miami, FL Mar `12`, `2026` `07:00`-`11:00` UTC

Maintenance on the Miami, FL data center will be performed on Thursday, March 12th, 2026 at 07:00 UTC. We expect to complete the maintenance by Thursday, March 12th, 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 Mar 02, 2026 - 14:56 UTC

[ICM-4717] Planned Maintenance on the Imperva data center in Chicago 2, IL Mar `16`, `2026` `04:00`-`12:00` UTC

Maintenance on the Chicago 2, IL data center will be performed on Monday, March 16th, 2026 at 04:00 UTC. We expect to complete the maintenance by Monday, March 16th, 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 Mar 05, 2026 - 17:51 UTC

[ICM-4718] Planned Maintenance on the Imperva data center in Lima, Peru Mar `18`, `2026` `04:00`-`12:00` UTC

Maintenance on the Lima, Peru data center will be performed on Wednesday, March 18th, 2026 at 04:00 UTC. We expect to complete the maintenance by Wednesday, March 18th, 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 Mar 05, 2026 - 17:49 UTC

[ICM-4706] Planned Maintenance on the Imperva data center in Taipei, Taiwan Mar `18`, `2026` `17:00` - Mar `19`, `2026` `01:00` UTC

Maintenance on the Taipei, Taiwan data center will be performed on Wednesday, March 18th, 2026 at 17:00 UTC. We expect to complete the maintenance by Thursday, March 19th, 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 Mar 06, 2026 - 23:22 UTC

[CWMS-6834] - Scheduled update to the Imperva waiting room – March 22, 2026 Mar `22`, `2026` `08:00`-`09:30` UTC

Update - We will be undergoing scheduled maintenance during this time.
Feb 22, 2026 - 21:07 UTC

Scheduled - The Imperva waiting room will undergo a scheduled update on March 22, 2026, between 08:00 and 9:30 UTC (rescheduled from March 1, 2026)
During this maintenance window, the Imperva waiting room will not function. Configuration changes to the waiting room settings should not be made at this time.

Customer domains will remain available and protected during this time.
We apologize for any inconvenience this may cause.
Feb 22, 2026 - 20:42 UTC

[UM-13046 ]- Scheduled update to the Cloud Security Console – March 22, 2026 Mar `22`, `2026` `14:00`-`17:00` UTC

The Cloud Security Console will undergo a scheduled update on March 22, 2025, between 14: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.
Posted on Feb 24, 2026 - 15:25 UTC

[ICM-4735] Planned Maintenance on the Imperva data center in Hanoi, Vietnam Mar `23`, `2026` `18:00` - Mar `24`, `2026` `02:00` UTC

Maintenance on the Hanoi, Vietnam data center will be performed on Monday, March 23rd, 2026 at 18:00 UTC. We expect to complete the maintenance by Tuesday, March 24th, 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
Posted on Mar 06, 2026 - 23:21 UTC

Past Incidents

Mar 7, 2026

No incidents reported today.

Mar 6, 2026

[INC-989] Tokyo, Japan (TKO) Data Center Issue

Resolved - Service in the Tokyo, Japan (TKO) data center has been restored to normal.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 6, 22:31 UTC

Monitoring - A fix has been implemented and traffic has been restored to the Tokyo, Japan (TKO) data center. We are continuing to monitor in order to ensure that service has returned to normal.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 6, 21:17 UTC

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

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 6, 09:47 UTC

Update - Technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to ensure service stability. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time.

Engineering teams will continue monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 6, 02:32 UTC

Investigating - Technical teams are investigating a potential issue in the Tokyo, Japan (TKO) data center. Further updates to follow.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 6, 02:20 UTC

[INC-988] Chicago 2, IL (CHI) Data Center Issue

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.
Mar 6, 05:58 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 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.
Mar 6, 05:45 UTC

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

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 5, 23:41 UTC

Identified - We have identified an issue in the data center. Traffic continues to be rerouted through an alternate data center in the region. Customers may experience some latency while the reroute remains in place.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 5, 22:49 UTC

Investigating - Technical teams are investigating a potential issue in the Chicago 2, IL (CHI) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 5, 22:30 UTC

Mar 5, 2026

[INC-987] Issue with Cache Purge

Resolved - Our engineering teams have completed the remediation. The issue affecting cache purge functionality has been resolved.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 5, 22:59 UTC

Update - We are continuing to work on a fix for this issue.
Mar 5, 22:11 UTC

Update - Our engineering teams have made progress in addressing the issue affecting cache purge functionality, and remediation efforts are ongoing.
Mar 5, 19:52 UTC

Update - We are continuing to work on a fix for this issue.
Mar 5, 18:48 UTC

Identified - We have identified the issue affecting cache purge functionality.
Our engineering teams are currently working on implementing a fix and restoring normal functionality. We will provide further updates as progress is made.
Mar 5, 17:57 UTC

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

[ICM-4633] Planned Maintenance on the Imperva data center in Tokyo, Japan

Completed - The scheduled maintenance has been completed.
Mar 5, 21:16 UTC

Verifying - Verification is currently underway for the maintenance items.
Mar 5, 20:50 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 5, 15:00 UTC

Update - We will be undergoing scheduled maintenance during this time.
Feb 26, 16:55 UTC

Scheduled - Maintenance on the Tokyo, Japan data center will be performed on Thursday, March 5th, 2026 at 15:00 UTC. We expect to complete the maintenance by Thursday, March 5th, 2026 at 23: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
Feb 26, 16:36 UTC

Mar 4, 2026

No incidents reported.

Mar 3, 2026

[INC-984] Attack Analytic Issue

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.
Mar 3, 20:26 UTC

Monitoring - The fix has been successfully implemented, and the Attack Analytics page is now accessible.
We are continuing to closely monitor the service to ensure stability and optimal performance. Further updates to follow.
Mar 3, 14:32 UTC

Identified - We have identified the source of the issue affecting Attack Analytics. Technical teams are planning remedial action. Further updates to follow.
Mar 3, 13:33 UTC

Investigating - We have discovered a service degradation affecting Attack Analytics, the page is returning errors. Technical teams are investigating. Further updates to follow.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 3, 13:04 UTC

[INC-983] API Security Issue

Monitoring - Technical teams have performed remedial actions and the API Security Page back to normal . Technical teams will continue monitoring the system.

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

In the event of a service disruption, the update will include potential impacts to any affected region
Mar 3, 13:35 UTC

Identified - We have identified the source of the issue affecting access to the API Security Page, "My APIs" Inventory and upload/manage OAS/Swagger files. Technical teams are planning remedial action. Further updates to follow.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 3, 12:53 UTC

Update - We are continuing to investigate this issue.
Mar 3, 12:12 UTC

Investigating - We are investigating an issue where some customers are unable to access the API Security "My APIs" Inventory and upload/manage OAS/Swagger files. Our technical teams are currently investigating the issue. Further updates will follow.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Mar 3, 11:57 UTC

[ICM-4641] Planned Maintenance on the Imperva data center in Barcelona, Spain

Completed - The scheduled maintenance has been completed.
Mar 3, 06:24 UTC

Update - Maintenance on the Barcelona, Spain data center has been extended to Tuesday, March 3rd, 2026 at 08:00 UTC.
Mar 3, 05:28 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 3, 00:00 UTC

Scheduled - Maintenance on the Barcelona, Spain data center will be performed on Tuesday, March 3rd, 2026 at 00:00 UTC. We expect to complete the maintenance by Tuesday, March 3rd, 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
Feb 19, 16:26 UTC

Mar 2, 2026

No incidents reported.

Mar 1, 2026

[TR-21344] - Scheduled update to the Imperva DNS protection – March 1, 2026

Completed - The scheduled maintenance has been completed.
Mar 1, 08:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 1, 06:30 UTC

Update - We will be undergoing scheduled maintenance during this time.
Feb 22, 13:56 UTC

Scheduled - The Imperva network DNS protection will undergo a scheduled update on March 1, 2026, between 06:30 and 8:00 UTC.
During this maintenance window, DNS Imperva management portal UI and API will not be available, and no configuration changes to the DNS protection can be made.

Customer domains will remain available and protected during this time.
We apologize for any inconvenience this may cause.
Feb 22, 13:53 UTC

Feb 28, 2026

[INC-982] Istanbul Turkey (SAW) Data Center Issue

Update - Traffic continues to remain rerouted through the alternate data center within the region to ensure service availability. We are actively following up with the third-party transit ISP(s) as they continue their investigation into the connectivity issue.
During this time, some customers may experience increased latency until normal routing is fully restored. Further updates will be shared as more information becomes available.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Feb 27, 17:54 UTC

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

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Feb 27, 14:19 UTC

Identified - We have identified an issue impacting connectivity through a third-party transit ISP. The provider is actively working to resolve the problem.
We are closely monitoring the situation and will share further updates as soon as additional information becomes available.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Feb 27, 12:44 UTC

Investigating - We have identified an issue in the Istanbul Turkey (SAW) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.

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.
Feb 27, 12:10 UTC

Feb 27, 2026

[ICM-4639] Essential Maintenance on the Imperva data center in Mumbai 2, India

Completed - The scheduled maintenance has been completed.
Feb 27, 00:52 UTC

Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Feb 27, 00:50 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 26, 20:00 UTC

Scheduled - Maintenance on the Mumbai 2, India data center will be performed on Thursday, February 26th, 2026 at 20:00 UTC. We expect to complete the maintenance by Friday, February 27th, 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
Feb 19, 16:23 UTC

Feb 26, 2026

Feb 25, 2026

[INC-980] Tokyo, Japan (TKO) Data Center Issue

Monitoring - Technical teams have remove the bypass. There was no customer impact identified and we identified an internal issue with our monitoring systems. Customer traffic has resumed via Tokyo, Japan (TKO).
We are continuing to monitor in order to ensure that service has returned to normal.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Feb 25, 09:12 UTC

Identified - Technical teams have identified an issue in the Tokyo, Japan (TKO) data center. As a precautionary measure, the TKO PoP will remain bypassed to ensure service stability. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time.

Engineering teams will continue monitoring the environment, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Feb 25, 04:27 UTC

Feb 24, 2026

No incidents reported.

Feb 23, 2026

Status page service changes and upcoming deprecations

Completed - The scheduled maintenance has been completed.
Feb 23, 12:30 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 23, 12:00 UTC

Scheduled - We are updating the Imperva Status page to improve clarity and consistency across services. As part of this update, existing services are renamed and reorganized, and some current service entries begin the deprecation process.
What’s changing on February 22, 2026:
The Status page uses an updated list of services, with revised naming and clear descriptions.
The single Services category is replaced with three categories:
o Protection services
o Management and analytics services
o Additional services
Existing services are marked as “Will be deprecated on March 22, 2026.”
What’s changing on March 22, 2026:
Services marked as deprecated are fully removed from the Status page.
What you need to do:
To continue receiving Status page updates for the relevant services, update your subscriptions to the new services before March 22, 2026.
1. Go to https://status.imperva.com/.
2. Click Subscribe to Updates.
3. Choose your preferred delivery method for notifications.
4. Under Components, select the new services you want to subscribe to.
If you do not subscribe to the new services, you will stop receiving updates when the deprecated services are removed.
Feb 23, 11:31 UTC

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Service Under Maintenance

Scheduled Maintenance

[ICM-4686] Planned Maintenance on the Imperva data center in Sao Paulo, Brazil Mar 9, 2026 04:00-10:00 UTC

[ICM-4688] Planned Maintenance on the Imperva data center in Hong Kong Mar 9, 2026 17:00 - Mar 10, 2026 01:00 UTC

[ICM-4687] Planned Maintenance on the Imperva data center in New York, NY Mar 11, 2026 03:00-09:00 UTC

[ICM-4694] Planned Maintenance on the Imperva data center in Miami, FL Mar 12, 2026 07:00-11:00 UTC

[ICM-4717] Planned Maintenance on the Imperva data center in Chicago 2, IL Mar 16, 2026 04:00-12:00 UTC

[ICM-4718] Planned Maintenance on the Imperva data center in Lima, Peru Mar 18, 2026 04:00-12:00 UTC

[ICM-4706] Planned Maintenance on the Imperva data center in Taipei, Taiwan Mar 18, 2026 17:00 - Mar 19, 2026 01:00 UTC

[CWMS-6834] - Scheduled update to the Imperva waiting room – March 22, 2026 Mar 22, 2026 08:00-09:30 UTC

[UM-13046 ]- Scheduled update to the Cloud Security Console – March 22, 2026 Mar 22, 2026 14:00-17:00 UTC

[ICM-4735] Planned Maintenance on the Imperva data center in Hanoi, Vietnam Mar 23, 2026 18:00 - Mar 24, 2026 02:00 UTC

Past Incidents

[ICM-4686] Planned Maintenance on the Imperva data center in Sao Paulo, Brazil Mar `9`, `2026` `04:00`-`10:00` UTC

[ICM-4688] Planned Maintenance on the Imperva data center in Hong Kong Mar `9`, `2026` `17:00` - Mar `10`, `2026` `01:00` UTC

[ICM-4687] Planned Maintenance on the Imperva data center in New York, NY Mar `11`, `2026` `03:00`-`09:00` UTC

[ICM-4694] Planned Maintenance on the Imperva data center in Miami, FL Mar `12`, `2026` `07:00`-`11:00` UTC

[ICM-4717] Planned Maintenance on the Imperva data center in Chicago 2, IL Mar `16`, `2026` `04:00`-`12:00` UTC

[ICM-4718] Planned Maintenance on the Imperva data center in Lima, Peru Mar `18`, `2026` `04:00`-`12:00` UTC

[ICM-4706] Planned Maintenance on the Imperva data center in Taipei, Taiwan Mar `18`, `2026` `17:00` - Mar `19`, `2026` `01:00` UTC

[CWMS-6834] - Scheduled update to the Imperva waiting room – March 22, 2026 Mar `22`, `2026` `08:00`-`09:30` UTC

[UM-13046 ]- Scheduled update to the Cloud Security Console – March 22, 2026 Mar `22`, `2026` `14:00`-`17:00` UTC

[ICM-4735] Planned Maintenance on the Imperva data center in Hanoi, Vietnam Mar `23`, `2026` `18:00` - Mar `24`, `2026` `02:00` UTC