Incapsula Outage History

Incapsula is up right now

Incapsula had 80 outages in the last 2 years totaling 327h 4m of downtime — averaging 3.3 incidents per month.

There were 80 Incapsula outages since September 17, 2025 totaling 327h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.incapsula.com

Major February 17, 2026

[INC-976] SSL SAN validation issue

Detected by Pingoru
Feb 17, 2026, 12:10 PM UTC
Resolved
Feb 17, 2026, 01:51 PM UTC
Duration
1h 41m
Timeline · 3 updates
  1. investigating Feb 17, 2026, 12:10 PM UTC

    We have identified an issue impacting the adding of new SANs and the adding of existing SANs undergoing revalidation on Imperva Managed Certificates. At this time, affected scenarios are new SAN validations and SAN renewal where the old certificate has expired, and the SAN has not been revalidated in the current period. This incident does not affect protection for websites onboarded to Imperva. 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.

  2. monitoring Feb 17, 2026, 12:48 PM UTC

    Technical teams have performed remedial actions and SSL SAN validation issue is returning to normal operations. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  3. resolved Feb 17, 2026, 01:51 PM UTC

    This issue has been resolved. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Minor February 12, 2026

[INC-974] Stockholm, Sweden (STO) Data Center Issue

Detected by Pingoru
Feb 12, 2026, 10:59 PM UTC
Resolved
Feb 13, 2026, 02:33 AM UTC
Duration
3h 34m
Affected: Stockholm, Sweden (STO)
Timeline · 5 updates
  1. investigating Feb 12, 2026, 10:59 PM UTC

    We are investigating an issue in the Stockholm, Sweden (STO) 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.

  2. investigating Feb 12, 2026, 11:37 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 13, 2026, 01:54 AM UTC

    Due to an issue in the data center traffic remains 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.

  4. monitoring Feb 13, 2026, 02:15 AM UTC

    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.

  5. resolved Feb 13, 2026, 02:33 AM UTC

    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.

Read the full incident report →

Major February 3, 2026

[INC-969] Los Angeles, CA (SNA) PoP Data Center Issue

Detected by Pingoru
Feb 03, 2026, 06:07 PM UTC
Resolved
Feb 05, 2026, 03:46 PM UTC
Duration
1d 21h
Affected: Los Angeles, CA (SNA)
Timeline · 7 updates
  1. investigating Feb 03, 2026, 06:07 PM UTC

    Our technical teams are currently investigating an issue affecting the Los Angeles, CA (SNA) Point of Presence. Some customers may experience intermittent connectivity or timeouts when accessing CWAF-protected applications through this location.

  2. investigating Feb 03, 2026, 06:40 PM UTC

    Our technical teams continue to actively investigate the issue affecting the Los Angeles, CA (SNA) Point of Presence.

  3. investigating Feb 03, 2026, 07:26 PM UTC

    Our technical teams have isolated the affected components, and customer impact has been mitigated. Services are currently stable. We are continuing to investigate the issue to identify the root cause and ensure long-term stability.

  4. investigating Feb 03, 2026, 07:57 PM UTC

    Our teams continue to investigate the issue. Services are currently stable and there is no ongoing customer impact. We will provide further updates as more information becomes available.

  5. identified Feb 03, 2026, 10:19 PM UTC

    The issue has been identified and isolated. At this time, there is no current customer impact. We are continuing to closely monitor the environment to ensure service remains stable.

  6. monitoring Feb 04, 2026, 09:38 AM UTC

    We deactivated the problematic component and issue has been remediated. 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.

  7. resolved Feb 05, 2026, 03:46 PM UTC

    The incident has been resolved and 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.

Read the full incident report →

Minor February 1, 2026

[INC-966] Imperva Management Portal Network Protect Dashboards Issue

Detected by Pingoru
Feb 01, 2026, 12:12 PM UTC
Resolved
Feb 01, 2026, 03:00 PM UTC
Duration
2h 47m
Timeline · 6 updates
  1. identified Feb 01, 2026, 12:12 PM UTC

    We have identified a service degradation that is causing the dashboard on the network not to display historical data for Network Protect dashboards. Despite this issue, customers can continue to use the Imperva Management Portal for managing their accounts without interruption. Technical teams are working on a mitigation. 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.

  2. identified Feb 01, 2026, 12:46 PM UTC

    Technical teams are continuing to working on a fix for this issue.

  3. identified Feb 01, 2026, 01:20 PM UTC

    Our engineers are actively working on the fix to resolve this issue. We will provide another update in 2 hours or as soon as more information becomes available.

  4. monitoring Feb 01, 2026, 02:28 PM UTC

    Technical teams have performed remedial actions and the dashboard on the network display historical data for Network Protect dashboards. Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  5. monitoring Feb 01, 2026, 02:54 PM UTC

    This issue has been resolved.

  6. resolved Feb 01, 2026, 03:00 PM UTC

    This issue has been resolved.

Read the full incident report →

Minor January 22, 2026

[INC-964] Imperva Management Portal Configuration Changes Issue

Detected by Pingoru
Jan 22, 2026, 11:05 PM UTC
Resolved
Jan 23, 2026, 02:25 AM UTC
Duration
3h 20m
Timeline · 4 updates
  1. investigating Jan 22, 2026, 11:05 PM UTC

    We have discovered a potential service degradation, affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. Customer sites are still fully protected at this time. Technical teams are investigating. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  2. investigating Jan 22, 2026, 11:54 PM UTC

    We are continuing to investigate the service degradation affecting Imperva Management Portal. Recent configuration changes are being propagated with a delay. 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.

  3. monitoring Jan 23, 2026, 12:52 AM UTC

    Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. 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.

  4. resolved Jan 23, 2026, 02:25 AM UTC

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Notice January 17, 2026

[INC-961] Osaka, Japan (OSK), Seoul, South Korea (KOR), and Tokyo, Japan (TKO) Data Center Issue

Detected by Pingoru
Jan 17, 2026, 03:49 PM UTC
Resolved
Jan 18, 2026, 01:10 AM UTC
Duration
9h 21m
Affected: Osaka, Japan (OSK)Seoul, South Korea (KOR)Tokyo, Japan (TKO)
Timeline · 2 updates
  1. monitoring Jan 17, 2026, 03:49 PM UTC

    We experienced a brief issue impacting the Osaka, Japan (OSK), Seoul, South Korea (KOR), and Tokyo, Japan (TKO) Points of Presence. The issue has been resolved, and our technical teams are actively monitoring services at these locations. During the incident, customers using Cloud WAF–protected sites and GRE tunnels may have experienced higher-than-expected latency, intermittent connectivity, or a temporary loss of connectivity to services in the OSK, KOR, and TKO PoPs. 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.

  2. resolved Jan 18, 2026, 01:10 AM UTC

    Monitoring has confirmed that services are stable across the affected data centers, and no further issues have been identified. 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.

Read the full incident report →

Minor January 16, 2026

[INC-960] Network DDoS Issue Detected

Detected by Pingoru
Jan 16, 2026, 12:51 PM UTC
Resolved
Jan 16, 2026, 03:10 PM UTC
Duration
2h 18m
Timeline · 3 updates
  1. investigating Jan 16, 2026, 12:51 PM UTC

    We have identified a potential issue affecting On-Demand DDoS Protection, where traffic diversion may not function as expected. Our technical teams are actively investigating the issue. 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.

  2. monitoring Jan 16, 2026, 01:50 PM UTC

    On-Demand DDoS Protection is currently operational, and traffic diversion is functioning as expected. The technical teams continue to monitor the service closely. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  3. resolved Jan 16, 2026, 03:10 PM UTC

    Services are stable and operating normally. We identified an internal service issue that prevented customer traffic from being diverted to Imperva’s mitigation network during active attack conditions. The issue was caused by an internal authentication failure. The service was restored after the affected component was restarted, and traffic diversion is now functioning as expected. We are performing a detailed root cause analysis and enhancing monitoring and automated recovery mechanisms to ensure faster detection and prevent recurrence. Additional details will be shared once the investigation is complete.

Read the full incident report →

Major January 7, 2026

[ INC-951] Ashburn, VA (IAD) Data Center Issue

Detected by Pingoru
Jan 07, 2026, 04:08 PM UTC
Resolved
Jan 07, 2026, 05:46 PM UTC
Duration
1h 38m
Affected: Ashburn, VA (IAD)
Timeline · 4 updates
  1. investigating Jan 07, 2026, 04:08 PM UTC

    Technical teams are investigating a potential issue in the Ashburn, VA (IAD) Data Center . Further updates to follow.

  2. identified Jan 07, 2026, 04:35 PM UTC

    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.

  3. monitoring Jan 07, 2026, 04:55 PM UTC

    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.

  4. resolved Jan 07, 2026, 05:46 PM UTC

    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.

Read the full incident report →

Minor January 3, 2026

[ INC- 949 ] Hanoi, Vietnam (HAN) Data Center Issue

Detected by Pingoru
Jan 03, 2026, 04:10 PM UTC
Resolved
Jan 03, 2026, 07:20 PM UTC
Duration
3h 10m
Affected: Hanoi, Vietnam (HAN)
Timeline · 5 updates
  1. identified Jan 03, 2026, 04:10 PM UTC

    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.

  2. investigating Jan 03, 2026, 04:45 PM UTC

    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.

  3. identified Jan 03, 2026, 04:57 PM UTC

    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.

  4. monitoring Jan 03, 2026, 06:43 PM UTC

    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.

  5. resolved Jan 03, 2026, 07:20 PM UTC

    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.

Read the full incident report →

Minor December 29, 2025

[INC-947] Chicago (ORD and CHI) and Los Angeles, CA (SNA) Data Center Issue

Detected by Pingoru
Dec 29, 2025, 04:48 PM UTC
Resolved
Dec 30, 2025, 02:07 AM UTC
Duration
9h 18m
Affected: Chicago 1, IL (ORD)Chicago 2, IL (CHI)Los Angeles, CA (SNA)
Timeline · 4 updates
  1. investigating Dec 29, 2025, 04:48 PM UTC

    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.

  2. identified Dec 29, 2025, 08:15 PM UTC

    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.

  3. monitoring Dec 29, 2025, 10:25 PM UTC

    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.

  4. resolved Dec 30, 2025, 02:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 26, 2025

Documentation Portal Access Issue

Detected by Pingoru
Dec 26, 2025, 07:44 AM UTC
Resolved
Dec 26, 2025, 11:46 AM UTC
Duration
4h 1m
Timeline · 2 updates
  1. investigating Dec 26, 2025, 07:44 AM UTC

    We are currently investigating an issue impacting access to the Imperva documentation portal. Our teams are actively working to identify the root cause and restore access as quickly as possible. This issue is limited to the documentation portal only and does not impact Imperva products, customer traffic, or any other security services. Further updates will be provided as more information becomes available.

  2. resolved Dec 26, 2025, 11:46 AM UTC

    The issue impacting access to the Imperva documentation portal has been resolved, and normal access has been restored.

Read the full incident report →

Notice December 18, 2025

test incident

Detected by Pingoru
Dec 18, 2025, 01:39 PM UTC
Resolved
Dec 18, 2025, 01:39 PM UTC
Duration
21s
Timeline · 2 updates
  1. investigating Dec 18, 2025, 01:39 PM UTC

    this is a test

  2. resolved Dec 18, 2025, 01:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2025

[INC-941] Account Take Over Issue

Detected by Pingoru
Dec 10, 2025, 11:28 AM UTC
Resolved
Dec 10, 2025, 12:11 PM UTC
Duration
42m
Timeline · 4 updates
  1. investigating Dec 10, 2025, 11:28 AM UTC

    We have detected a potential service degradation affecting Account Takeover (ATO). Customers may encounter errors while onboarding new sites or endpoints. Our technical teams are investigating the issue, and we will provide additional 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.

  2. identified Dec 10, 2025, 11:49 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Dec 10, 2025, 11:57 AM UTC

    Technical teams have performed remedial actions and the Account Takeover service has returned to normal service levels. 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.

  4. resolved Dec 10, 2025, 12:11 PM UTC

    The incident has been resolved and normal service levels have been restored for the Account Takeover service. 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.

Read the full incident report →

Minor December 7, 2025

[INC-940] Imperva Management Portal Security Dashboard and API Security Dashboard Issue

Detected by Pingoru
Dec 07, 2025, 10:00 AM UTC
Resolved
Dec 07, 2025, 10:43 AM UTC
Duration
43m
Timeline · 3 updates
  1. investigating Dec 07, 2025, 10:00 AM UTC

    We have discovered a potential service degradation, affecting the Imperva Management Portal. Security Dashboard and API Security Dashboards are not responding or returning errors. Customer domains are still fully protected at this time. Technical teams are investigating. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  2. monitoring Dec 07, 2025, 10:16 AM UTC

    Technical teams have performed remedial actions and the Security Dashboard and API Security Dashboards are now correctly displaying data. Technical teams will continue monitoring the system. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  3. resolved Dec 07, 2025, 10:43 AM UTC

    The incident has been resolved and normal service levels have been restored for the Security Dashboard and API Security Dashboards on the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Minor November 24, 2025

[INC-936] Issue with Imperva Security Dashboard

Detected by Pingoru
Nov 24, 2025, 12:27 PM UTC
Resolved
Nov 24, 2025, 02:02 PM UTC
Duration
1h 34m
Timeline · 5 updates
  1. investigating Nov 24, 2025, 12:27 PM UTC

    We have discovered a potential issue affecting Imperva security Console Dashboard . 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.

  2. investigating Nov 24, 2025, 12:36 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 24, 2025, 12:52 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Nov 24, 2025, 01:00 PM UTC

    Technical teams have performed remedial actions and Imperva Security Dashboard is returning to normal operations. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  5. resolved Nov 24, 2025, 02:02 PM UTC

    This issue has been resolved. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Minor November 18, 2025

[INC-935] Imperva Management Portal UI Performance Degradation

Detected by Pingoru
Nov 18, 2025, 07:54 PM UTC
Resolved
Nov 19, 2025, 01:32 AM UTC
Duration
5h 38m
Timeline · 4 updates
  1. investigating Nov 18, 2025, 07:54 PM UTC

    We have discovered a potential service degradation, affecting Imperva Management Portal. The Management Portal website is slow to respond to user actions. All customer websites remain fully protected at this time. Technical teams are investigating. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  2. monitoring Nov 18, 2025, 08:29 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Nov 18, 2025, 08:42 PM UTC

    Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  4. resolved Nov 19, 2025, 01:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 17, 2025

[INC 934] Imperva Management Portal Configuration Changes Issue

Detected by Pingoru
Nov 17, 2025, 11:43 AM UTC
Resolved
Nov 17, 2025, 02:02 PM UTC
Duration
2h 18m
Timeline · 4 updates
  1. identified Nov 17, 2025, 11:43 AM UTC

    We have identified the source of the service degradation that is causing recent configuration changes made in the Imperva Management Portal not to be propagated. Technical teams are working on a mitigation. 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.

  2. monitoring Nov 17, 2025, 01:00 PM UTC

    Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. 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.

  3. monitoring Nov 17, 2025, 01:32 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 17, 2025, 02:02 PM UTC

    The incident has been resolved and normal service levels have been restored for propagation of changes in the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →

Minor November 16, 2025

[INC-933] Imperva Management Portal Configuration Changes Issue

Detected by Pingoru
Nov 16, 2025, 06:59 PM UTC
Resolved
Nov 16, 2025, 08:38 PM UTC
Duration
1h 39m
Timeline · 3 updates
  1. identified Nov 16, 2025, 06:59 PM UTC

    We have identified the source of the service degradation that is causing recent configuration changes made in the Imperva Management Portal to be propagated with a delay. Technical teams are working on a mitigation. 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.

  2. monitoring Nov 16, 2025, 08:08 PM UTC

    Technical teams have performed remedial actions and propagation of configuration changes in the Imperva Management Portal are returning to normal service levels. Technical teams will continue monitoring the system as it may take additional time for the backlog to clear. 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.

  3. resolved Nov 16, 2025, 08:38 PM UTC

    The incident has been resolved and normal service levels have been restored for the Imperva Management Portal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Read the full incident report →