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 (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
Services Operational
Imperva Management Portal UI Operational
Imperva Management Portal API Operational
Imperva Management Portal- Configuration Changes Operational
Cloud WAF Network Operational
IP Protection Operational
Advanced Bot Protection Operational
Account Take Over Operational
DNS Protection Operational
JSONAR Operational
Client-Side Protection Operational
Cloud WAF GDPR Operational
Cloud WAF SIEM Operational
Cloud WAF Events & Statistics Operational
Attack Analytics Operational
Cloud Data Security Operational
Runtime Application Self Protection Operational
API Security Operational
Imperva Support - Ticketing and Phone Systems Operational
Weblogs Operational
Network DDoS Operational
Third Party Services Operational
Third Party Services Operational
Coming Soon Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

[TR-21145] Scheduled update to the Imperva Network protection – January 11, 2026 Jan 11, 2026 14:00-17:00 UTC

The Imperva network protection will undergo a scheduled update on January 11, 2026, between 14:00 and 17:00 UTC. During this maintenance window, customers may experience delays when applying configuration changes to the Network DDOS settings (L3).
Posted on Dec 30, 2025 - 16:13 UTC

[ICM-4367] Planned Maintenance on the Imperva data center in Amsterdam, Netherlands Jan 13, 2026 23:00 - Jan 14, 2026 05:00 UTC

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

[ICM-4509] Essential Maintenance on the Imperva data center in Jakarta, Indonesia Jan 15, 2026 17:00 - Jan 16, 2026 01:00 UTC

Maintenance on the Jakarta, Indonesia data center will be performed on Thursday, January 15th, 2026 at 17:00 UTC. We expect to complete the maintenance by Friday, January 16th, 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 Jan 08, 2026 - 14:59 UTC
Jan 10, 2026

No incidents reported today.

Jan 9, 2026

No incidents reported.

Jan 8, 2026
[ICM-4426] Planned Maintenance on the Imperva data center in London 2, UK
Completed - The scheduled maintenance has been completed.
Jan 8, 05:17 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 7, 23:00 UTC
Scheduled - Maintenance on the London 2, UK data center will be performed on Wednesday, January 7th, 2026 at 23:00 UTC. We expect to complete the maintenance by Thursday, January 8th, 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
Dec 9, 05:36 UTC
Jan 7, 2026
[ INC-951] Ashburn, VA (IAD) Data Center Issue
Resolved - Services in the data center has been restored to normal.

The IAD PoP was inadvertently deactivated, which caused customer CWAF traffic to be temporarily routed to alternate PoPs. Once identified, the PoP was reactivated, and engineers have confirmed that traffic has now shifted back to IAD and is being processed normally.
During the incident, some traffic may have experienced a brief period of session resets and increased latency due to sub-optimal routing to alternate PoPs.
Further research will be performed into how to prevent the triggering event which caused the PoP deactivation from recurring, and additional details will be provided following a completed root cause analysis.
Jan 7, 17:46 UTC
Monitoring - A fix has been implemented and we are continuing to monitor in order to ensure that service has returned to normal.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Jan 7, 16:55 UTC
Identified - We have identified the source of the issue in the data center. Technical teams are working on a fix.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Jan 7, 16:35 UTC
Investigating - Technical teams are investigating a potential issue in the Ashburn, VA (IAD) Data Center . Further updates to follow.
Jan 7, 16:08 UTC
Jan 6, 2026

No incidents reported.

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

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 31, 15:34 UTC
Identified - To ensure the best possible user experience and maintain business continuity, we have proactively implemented a temporary bypass of the Chicago (CHI) PoP.

Customers who were previously served by the CHI PoP are being automatically rerouted to an alternative PoP. This process requires no action on your part, and services will continue to be delivered as usual.

As a result of this rerouting, some customers may experience slightly increased latency. This behavior is expected during the bypass and does not indicate a service outage. If you experience any issues beyond normal latency, please contact our Technical Support team so we can assist promptly.

We will continue to monitor the situation closely and provide updates as needed.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 30, 21:36 UTC
Update - Technical teams are currently investigating and will provide updates as more information becomes available.
Dec 30, 21:05 UTC
Update - Technical teams are currently investigating the issue and will provide updates as more information becomes available.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 30, 20:35 UTC
Update - Technical teams are actively investigating the issue.
Dec 30, 20:05 UTC
Update - We are investigating the issue and will share updates as available.
Dec 30, 19:34 UTC
Update - Technical teams are currently investigating the issue and will provide updates as more information becomes available.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 30, 19:04 UTC
Update - We are continuing to investigate this issue.
Dec 30, 18:30 UTC
Update - Technical teams are actively investigating the issue.
Dec 30, 17:57 UTC
Update - Technical teams are currently investigating and will provide updates as more information becomes available.
Dec 30, 17:09 UTC
Update - We are continuing to investigate this issue.
Dec 30, 16:15 UTC
Investigating - Technical teams are currently investigating a potential issue impacting the Chicago 2, IL (CHI) data center.
At this time our services are operational. However, some customers may experience intermittent connectivity issues when accessing websites.
Customers encountering any issues are advised to contact Imperva Support for assistance.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 30, 15:17 UTC
Jan 4, 2026
[ICM-4478] Planned Maintenance on the Imperva data center in Bogota, Colombia
Completed - The scheduled maintenance has been completed.
Jan 4, 13:57 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 4, 05:00 UTC
Scheduled - Maintenance on the Bogota, Colombia data center will be performed on Sunday, January 4th, 2026 at 05:00 UTC. We expect to complete the maintenance by Sunday, January 4th, 2026 at 15: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
Dec 22, 15:41 UTC
[TR-21145] Scheduled update to the Imperva Network protection – January 4, 2026
Completed - The scheduled maintenance has been completed.
Jan 4, 08:30 UTC
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Jan 4, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 4, 07:00 UTC
Scheduled - The Imperva network protection will undergo a scheduled update on January 4, 2026, between 07:00 and 8:30 UTC. During this maintenance window, customers may experience delays when applying configuration changes to the Network DDOS settings (L3).
Dec 30, 16:11 UTC
Jan 3, 2026
[ INC- 949 ] Hanoi, Vietnam (HAN) 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.
Jan 3, 19:20 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.
Jan 3, 18:43 UTC
Identified - Technical teams are continuing to working on a fix for the data center issue.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Jan 3, 16:57 UTC
Investigating - Technical teams are continuing to working on a fix for the data center issue.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Jan 3, 16:45 UTC
Identified - We have identified an issue in the Hanoi, Vietnam (HAN) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Jan 3, 16:10 UTC
Jan 2, 2026

No incidents reported.

Jan 1, 2026

No incidents reported.

Dec 31, 2025
Dec 30, 2025
[INC-947] Chicago (ORD and CHI) and Los Angeles, CA (SNA) Data Center Issue
Resolved - This incident has been resolved.
Dec 30, 02:07 UTC
Monitoring - A fix has been implemented and we are continuing to monitor in order to ensure that service has returned to normal.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 29, 22:25 UTC
Identified - We have identified the source of the issue in the data center. Technical teams are working on a fix.

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

In the event of a service disruption, the update will include potential impacts to any affected region.
Dec 29, 20:15 UTC
Investigating - Technical teams are investigating a potential issue in the Chicago, IL (ORD and CHI) and Los Angeles, CA (SNA) data centers. 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.
Dec 29, 16:48 UTC
Dec 29, 2025
Dec 28, 2025

No incidents reported.

Dec 27, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage