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 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 Under Maintenance
Tokyo, Japan (NRT) - May 2026 Under Maintenance
Amsterdam, Netherlands  (RTM)  - May 2026 Under Maintenance
Frankfurt, Germany  (HHN) - April 2026 Under Maintenance
Singapore (XSP) - May 2026 Under Maintenance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

[ICM-4879] Essential Maintenance on the Imperva data center in Melbourne, Australia Apr 16, 2026 14:00-22:00 UTC

Maintenance on the Melbourne, Australia data center will be performed on Thursday, April 16th, 2026 at 14:00 UTC. We expect to complete the maintenance by Thursday, April 16th, 2026 at 22: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 Apr 09, 2026 - 13:56 UTC

[PPNG-3294] - Scheduled update to the Cloud Security Console – April 19, 2026 Apr 19, 2026 13:00-15:00 UTC

The Cloud Security Console will undergo a scheduled update on April 19, 2026, between 13:00 and 15:00 UTC (updated time). During this maintenance window, customers may experience temporary disruptions when logging in to the Cloud Management console.

No impact is expected to API and Terraform authentication or functionality.
Customer sites will remain online and protected at all times. We appreciate your understanding and apologize for any inconvenience.
Posted on Apr 12, 2026 - 18:55 UTC

[ICM-4875] Planned maintenance on the Imperva data center in New York 2, NY Apr 21, 2026 02:00-10:00 UTC

Maintenance on the New York 2, NY data center will be performed on Tuesday, April 21st, 2026 at 02:00 UTC. We expect to complete the maintenance by Tuesday, April 21st, 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 Apr 14, 2026 - 03:41 UTC

[ICM-4904] Planned maintenance on the Imperva data center in Houston, TX Apr 23, 2026 04:00-12:00 UTC

Maintenance on the Houston, TX data center will be performed on Thursday, April 23rd 2026 at 04:00 UTC. We expect to complete the maintenance by Thursday, April 23rd 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 Apr 14, 2026 - 17:16 UTC

[UM-13107] - Scheduled update to the Cloud Security Console – April 26, 2026 Apr 26, 2026 13:00-16:00 UTC

Update - We will be undergoing scheduled maintenance during this time.
Apr 12, 2026 - 18:42 UTC
Scheduled - The Cloud Security Console will undergo a scheduled update on April 26, 2026, between 13:00 and 16: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 09, 2026 - 08:19 UTC

[ICM-4906] Planned Maintenance on the Imperva data center in Paris 2, France Apr 28, 2026 23:00 - Apr 29, 2026 05:00 UTC

Maintenance on the Paris 2, France data center will be performed on Tuesday, April 28th, 2026 at 23:00 UTC. We expect to complete the maintenance by Wednesday, April 29th, 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
Posted on Apr 15, 2026 - 06:25 UTC
Apr 15, 2026

No incidents reported today.

Apr 14, 2026

No incidents reported.

Apr 13, 2026
[ICM-4795] Planned Maintenance on the Imperva data center in Houston, TX
Completed - The scheduled maintenance has been completed.
Apr 13, 12:59 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 13, 05:00 UTC
Scheduled - Maintenance on the Houston, TX data center will be performed on Monday, April 13rd, 2026 at 05:00 UTC. We expect to complete the maintenance by Monday, April 13rd, 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
Apr 5, 12:40 UTC
[INC-1011] Imperva API Issue
Resolved - The incident has been resolved and normal service levels have been restored for the Imperva's API service.
Apr 13, 05:31 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 13, 04:59 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 13, 04:53 UTC
Update - We are continuing to investigate the potential service disruption affecting Imperva's API. The next Status Update on this Incident will be provided no later than 5:17 UTC. Further updates to follow.
Apr 13, 04:47 UTC
Update - We are continuing to investigate the potential service disruption affecting Imperva's API. The next Status Update on this Incident will be provided no later than 04:47 UTC. Further updates to follow.
Apr 13, 04:18 UTC
Investigating - We have discovered a potential service disruption affecting Imperva's API. 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.
Apr 13, 03:47 UTC
Apr 12, 2026
[TR-11927] - Scheduled update to the Cloud Security Console – April 12, 2026
Completed - The scheduled maintenance has been completed.
Apr 12, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 12, 06:00 UTC
Scheduled - The Cloud Security Console will undergo a scheduled update on April 12, 2026, between 06:00 and 07:00 UTC. During this maintenance window, customers may experience temporary disruptions when making changes to domains and site settings (including onboarding ). In addition, the CAPTCHA fallback mechanism will be temporarily unavailable.
Apr 6, 14:30 UTC
Apr 11, 2026

No incidents reported.

Apr 10, 2026
[INC-1009] Imperva Management Portal Cloud WAF Dashboard Issue
Resolved - Final validation has been completed, data visibility on the Cloud WAF dashboard has been restored, and all systems are now functioning as expected.

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.
Apr 10, 10:05 UTC
Update - Data visibility has been restored on the Cloud WAF dashboard, and systems are operating as expected. However, a gap remains for the period from yesterday until now. The data is present, but may not be fully visible across all resolutions.
We are actively completing the remaining data processing and backfilling the missing data. New data is being reflected correctly on the dashboard. Full restoration is expected within approximately 10 hours.
Apr 9, 23:17 UTC
Update - The fix is currently being deployed by the technical teams.

The next status update for this incident will be provided no later than 23:25 UTC.
Apr 9, 22:57 UTC
Update - The fix is currently being deployed by the technical teams.

The next status update for this incident will be provided no later than 22:50 UTC.
Apr 9, 22:20 UTC
Update - The fix is currently being deployed by the technical teams.

The next status update for this incident will be provided no later than 22:20 UTC.
Apr 9, 21:50 UTC
Update - We have identified the source of the service degradation impacting the Cloud WAF dashboard, resulting in missing data in the Security Events section. A fix is currently being deployed by the technical teams.

The next status update for this incident will be provided no later than 21:50 UTC.
Apr 9, 21:20 UTC
Identified - We have identified the source of the service degradation impacting the Cloud WAF dashboard, resulting in missing data in the Security Events section. Technical teams are actively working on mitigation.

The next status update for this incident will be provided no later than 21:19 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.
Apr 9, 20:49 UTC
Update - We continue to investigate the service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected, and our engineering teams are actively working toward resolution.

The next Status Update on this Incident will be provided no later than 21:06 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.
Apr 9, 20:36 UTC
Update - We continue to investigate the service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected, and our engineering teams are actively working toward resolution.

The next Status Update on this Incident will be provided no later than 20: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.

In the event of a service disruption, the update will include potential impacts to any affected region.
Apr 9, 20:06 UTC
Investigating - We have identified a potential service degradation affecting the Imperva Management Portal. The Cloud WAF dashboard is not displaying data in the Security Events section. Customer domains remain fully protected at this time. Technical teams are actively investigating, and further updates will follow.

The next Status Update on this Incident will be provided no later than 20:08 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.
Apr 9, 19:39 UTC
[INC-1008] Advanced Bot Protection Issue
Resolved - The incident has been resolved and normal service levels have been restored for the Imperva Advanced Bot Protection service.
Apr 10, 01:16 UTC
Update - Services remain stable. Monitoring has been in progress and will continue for an extended period to ensure sustained stability and normal operation.
Apr 9, 21:37 UTC
Monitoring - The phased global rollout has been successfully completed. Systems are stable, and monitoring is ongoing to ensure continued normal operation.
Apr 9, 19:12 UTC
Update - The phased global rollout is currently underway, with continuous monitoring in place. The next status update will be provided no later than 19:50 UTC.
Apr 9, 18:50 UTC
Update - The phased global deployment is currently in progress. Monitoring is ongoing as we continue with the rollout. The next status update will be provided no later than 18:50 UTC.
Apr 9, 17:50 UTC
Update - We are deploying the fix globally in a phased approach to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 17:50 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.
Apr 9, 16:50 UTC
Update - We are deploying the fix globally in a phased approach to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 16:50 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.
Apr 9, 15:51 UTC
Update - We are rolling out the fix in a phased manner globally to minimize any potential impact on live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 15:50 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.
Apr 9, 14:50 UTC
Update - We are rolling out the fix in a phased manner globally to reduce the risk of additional impact to live customer traffic. This will take time and we will provide regular updates in a 60 minute cadence until it is completed. The next Status Update on this Incident will be provided no later than 14:50 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.
Apr 9, 13:51 UTC
Update - Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 13:50 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.
Apr 9, 13:20 UTC
Update - Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 13:20 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.
Apr 9, 12:50 UTC
Update - Technical teams are actively implementing a fix. The next status update on this incident will be provided no later than 12:50 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.
Apr 9, 12:20 UTC
Update - Technical teams are working on a FIX. The next status update on this incident will be provided no later than 12:20 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.
Apr 9, 11:50 UTC
Update - Technical teams are working on a FIX. The next status update on this incident will be provided no later than 11:50 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.
Apr 9, 11:19 UTC
Identified - We have identified an issue in key rotation which is affecting tokens for Advance Bot Protection customers. Technical teams are working on a mitigation. The next status update on this incident will be provided no later than 11:15 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.
Apr 9, 10:45 UTC
Update - We are actively investigating a potential service disruption impacting Advanced Bot Protection. Engineering teams are engaged and working to determine the cause and contributing factors. The next update will be provided by 11:55 UTC.
Apr 9, 10:26 UTC
Update - We are continuing to investigate a potential service disruption affecting Advanced Bot Protection. Our technical teams are actively working to identify the cause. The next status update on this incident will be provided no later than 10:25 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.
Apr 9, 09:56 UTC
Update - We are continuing to investigate the potential service disruption affecting Advanced Bot Protection. Our technical teams are actively investigating the set of contributing factors. The next Status Update on this Incident will be provided no later than 09: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.
Apr 9, 09:26 UTC
Update - We are continuing to investigate the potential service disruption affecting Advanced Bot Protection. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 09:25 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.
Apr 9, 08:55 UTC
Investigating - We have discovered a potential service degradation affecting Advance Bot Protection customers. Customer websites are returning browser errors to some end users. Customer sites are still fully protected by Advanced Bot Protection 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.
Apr 9, 07:49 UTC
Apr 9, 2026
Apr 8, 2026

No incidents reported.

Apr 7, 2026

No incidents reported.

Apr 6, 2026
[ICM-4857] Essential Maintenance on the Imperva data center in Chicago 1, IL
Completed - The scheduled maintenance has been completed.
Apr 6, 12:59 UTC
Update - Maintenance on the Chicago 1, IL data center has been extended to Monday, April 6th, 2026 at 13:00 UTC.
Apr 6, 11:47 UTC
Update - Maintenance on the Chicago 1, IL data center has been extended to Monday, April 6th, 2026 at 12:00 UTC.
Apr 6, 10:40 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 6, 05:00 UTC
Scheduled - Maintenance on the Chicago 1, IL data center will be performed on Monday, April 6th, 2026 at 05:00 UTC. We expect to complete the maintenance by Monday, April 6th, 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 2, 18:28 UTC
Apr 5, 2026
[INC-1004] Potential CWAF issue on multiple Data Center
Resolved - Service in the data centers have 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.
Apr 5, 14:55 UTC
Monitoring - The issue appears to be resolved at this time. 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.
Apr 5, 14:39 UTC
Investigating - Technical teams are investigating a potential CWAF issue in the (DFW, EWR, IAD, LCY, NYC, PAR) Data Center . Further updates to follow.
Apr 5, 14:02 UTC
[ICM-4809] Essential Maintenance on the Imperva data center in Ashburn, VA
Completed - The scheduled maintenance has been completed.
Apr 5, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 5, 06:00 UTC
Scheduled - Maintenance on the Ashburn, VA data center will be performed on Sunday, April 5th, 2026 at 06:00 UTC. We expect to complete the maintenance by Sunday, April 5th, 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
Mar 29, 06:42 UTC
Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026

No incidents reported.

Apr 1, 2026
[ICM-4767] Planned Maintenance on the Imperva data center in Chicago 2, IL
Completed - The scheduled maintenance has been completed.
Apr 1, 11:56 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 1, 04:00 UTC
Update - Maintenance on the Chicago 2, IL data center will be performed on Wednesday, April 1st, 2026 at 04:00 UTC. We expect to complete the maintenance by Wednesday, April 1st, 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
Mar 24, 09:22 UTC
Scheduled - Maintenance on the Chicago 2, IL data center will be performed on Tuesday, March 31st, 2026 at 04:00 UTC. We expect to complete the maintenance by Wednesday, April 1st, 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
Mar 24, 09:09 UTC
← Incident History Powered by Atlassian Statuspage