Imperva Outage History

Imperva is up right now

There were 28 Imperva outages since February 3, 2026 totaling 147h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.imperva.com

Minor May 3, 2026

[INC-1021] Imperva Security Event Delay Issue

Detected by Pingoru
May 03, 2026, 10:48 AM UTC
Resolved
May 03, 2026, 04:28 PM UTC
Duration
5h 39m
Affected: Cloud Security Management PlatformSIEM LogsEvents PageAttack Analytic
Timeline · 12 updates
  1. investigating May 03, 2026, 10:48 AM UTC

    We have discovered a potential service degradation, affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. 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. identified May 03, 2026, 11:18 AM UTC

    We have identified the source of the service degradation affecting the Imperva Management Portal. This issue affects the Security Events page of the management portal and email notification alerts for security events. This issue is isolated to customers with data centers in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 11:48 AM 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.

  3. investigating May 03, 2026, 11:49 AM UTC

    Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 12:18 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.

  4. identified May 03, 2026, 11:57 AM UTC

    During the course of the investigation our teams found that the issue also affects the Attack Analytics and Security log delivery via SIEM solution in the APAC region. The next status update on this incident will be provided no later than 12:27 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.

  5. identified May 03, 2026, 12:31 PM UTC

    During the course of the investigation our teams found that the issue also affects ABP and Attack Analytics log delivery via SIEM solution in the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 13:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  6. identified May 03, 2026, 01:02 PM UTC

    Technical teams are continuing to work on a fix for the Imperva Management Portal issue. The next status update on this incident will be provided no later than 13:30 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

  7. identified May 03, 2026, 01:30 PM UTC

    The teams have identified a component potentially causing the issue. They are currently working to mitigate it. The next Status Update on this Incident will be provided no later than 14:00 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  8. identified May 03, 2026, 02:03 PM UTC

    Team are actively working to mitigate the issue. The next Status Update on this Incident will be provided no later than 14:33 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

  9. identified May 03, 2026, 02:33 PM UTC

    Technical teams are continuing to work on a fix the issue. The next status update on this incident will be provided no later than 15:03 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.

  10. identified May 03, 2026, 03:06 PM UTC

    The team has resolved the Security Events page issue on the Management Platform; however, Attack Analytics, threat alert emails, and SIEM integrations may still be impacted. The next Status Update on this Incident will be provided no later than 15: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.

  11. monitoring May 03, 2026, 03:28 PM UTC

    The incident has been resolved, and all services have returned to normal operating levels. We will continue to monitor the situation 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.

  12. resolved May 03, 2026, 04:28 PM UTC

    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.

Read the full incident report →

Minor April 27, 2026

[INC-1019] Imperva Management Portal Configuration Changes Issue

Detected by Pingoru
Apr 27, 2026, 11:04 AM UTC
Resolved
Apr 27, 2026, 11:31 AM UTC
Duration
26m
Affected: Cloud Security Management Configuration Changes
Timeline · 3 updates
  1. investigating Apr 27, 2026, 11:04 AM UTC

    We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 11:34UTC. 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 Apr 27, 2026, 11:14 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.

  3. resolved Apr 27, 2026, 11:31 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 →

Major April 24, 2026

[INC-1018] Imperva Management Portal Configuration Changes Issue

Detected by Pingoru
Apr 24, 2026, 02:43 PM UTC
Resolved
Apr 25, 2026, 01:14 AM UTC
Duration
10h 31m
Affected: Cloud Security Management Configuration Changes
Timeline · 11 updates
  1. investigating Apr 24, 2026, 02:43 PM UTC

    We have discovered a potential issue affecting My Publishing. 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 Apr 24, 2026, 03:24 PM UTC

    We are continuing to investigate the service degradation affecting Imperva Management Portal. Next update will be shared at 03:54UTC. 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. investigating Apr 24, 2026, 04:00 PM UTC

    The investigation into the service degradation affecting the Imperva Management Portal is ongoing, and the next update is scheduled for 16:30 UTC. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  4. investigating Apr 24, 2026, 04:35 PM UTC

    The team is actively investigating the service degradation impacting the Imperva Management Portal, with the next update expected at 17:05 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.

  5. investigating Apr 24, 2026, 05:05 PM UTC

    We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 18:05 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.

  6. investigating Apr 24, 2026, 06:06 PM UTC

    We are continuing to investigate the potential service disruption affecting the Imperva Management Portal. The next Status Update on this Incident will be provided no later than 19: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.

  7. investigating Apr 24, 2026, 07:07 PM UTC

    We are actively investigating a service degradation affecting the Imperva Management Portal. We will provide the next update as soon 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.

  8. investigating Apr 24, 2026, 10:30 PM UTC

    The team is actively investigating the issue and processed approximately 30% of configuration change. The next update will be provided as soon 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.

  9. identified Apr 24, 2026, 11:47 PM UTC

    We have identified the source of the service degradation that is causing delays in the propagation of recent configuration changes in the Imperva Management Portal. An additional 20% of configuration changes have been processed, reducing the overall delay. The next update will be provided at 00:47 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.

  10. monitoring Apr 25, 2026, 12:02 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.

  11. resolved Apr 25, 2026, 01:14 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 →

Major April 21, 2026

[INC-1015] Santiago, Chile (STC) Data Center Issue

Detected by Pingoru
Apr 21, 2026, 11:21 PM UTC
Resolved
Apr 22, 2026, 12:08 AM UTC
Duration
47m
Affected: Santiago, Chile (STC)
Timeline · 3 updates
  1. investigating Apr 21, 2026, 11:21 PM UTC

    Technical teams are investigating a potential issue in the Santiago, Chile (STC) Data Center . Further updates to follow. The next Status Update on this Incident will be provided no later than 23:50 UTC.

  2. monitoring Apr 21, 2026, 11:34 PM UTC

    A fix has been successfully implemented, and the issue has been remediated. All services are now operating as expected. We are continuing to closely monitor the environment to ensure stability and prevent any recurrence.

  3. resolved Apr 22, 2026, 12:08 AM UTC

    The incident has been resolved, and all services have been restored to normal operation.

Read the full incident report →

Major April 13, 2026

[INC-1011] Imperva API Issue

Detected by Pingoru
Apr 13, 2026, 03:47 AM UTC
Resolved
Apr 13, 2026, 05:31 AM UTC
Duration
1h 43m
Affected: CDN and WAF Management
Timeline · 6 updates
  1. investigating Apr 13, 2026, 03:47 AM UTC

    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.

  2. investigating Apr 13, 2026, 04:18 AM UTC

    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.

  3. investigating Apr 13, 2026, 04:47 AM UTC

    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.

  4. identified Apr 13, 2026, 04:53 AM UTC

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

  5. monitoring Apr 13, 2026, 04:59 AM UTC

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

  6. resolved Apr 13, 2026, 05:31 AM UTC

    The incident has been resolved and normal service levels have been restored for the Imperva's API service.

Read the full incident report →

Major April 9, 2026

[INC-1009] Imperva Management Portal Cloud WAF Dashboard Issue

Detected by Pingoru
Apr 09, 2026, 07:39 PM UTC
Resolved
Apr 10, 2026, 10:05 AM UTC
Duration
14h 26m
Affected: CDN and WAF Management
Timeline · 10 updates
  1. investigating Apr 09, 2026, 07:39 PM UTC

    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.

  2. investigating Apr 09, 2026, 08:06 PM UTC

    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.

  3. investigating Apr 09, 2026, 08:36 PM UTC

    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.

  4. identified Apr 09, 2026, 08:49 PM UTC

    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.

  5. identified Apr 09, 2026, 09:20 PM UTC

    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.

  6. identified Apr 09, 2026, 09:50 PM UTC

    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.

  7. identified Apr 09, 2026, 10:20 PM UTC

    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.

  8. identified Apr 09, 2026, 10:57 PM UTC

    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.

  9. identified Apr 09, 2026, 11:17 PM UTC

    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.

  10. resolved Apr 10, 2026, 10:05 AM UTC

    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.

Read the full incident report →

Major April 9, 2026

[INC-1008] Advanced Bot Protection Issue

Detected by Pingoru
Apr 09, 2026, 07:49 AM UTC
Resolved
Apr 10, 2026, 01:16 AM UTC
Duration
17h 27m
Affected: Advanced BOT Protection
Timeline · 20 updates
  1. investigating Apr 09, 2026, 07:49 AM UTC

    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.

  2. investigating Apr 09, 2026, 08:55 AM UTC

    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.

  3. investigating Apr 09, 2026, 09:26 AM UTC

    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.

  4. investigating Apr 09, 2026, 09:56 AM UTC

    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.

  5. investigating Apr 09, 2026, 10:26 AM UTC

    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.

  6. identified Apr 09, 2026, 10:45 AM UTC

    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.

  7. identified Apr 09, 2026, 11:19 AM UTC

    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.

  8. identified Apr 09, 2026, 11:50 AM UTC

    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.

  9. identified Apr 09, 2026, 12:20 PM UTC

    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.

  10. identified Apr 09, 2026, 12:50 PM UTC

    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.

  11. identified Apr 09, 2026, 01:20 PM UTC

    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.

  12. identified Apr 09, 2026, 01:51 PM UTC

    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.

  13. identified Apr 09, 2026, 02:50 PM UTC

    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.

  14. identified Apr 09, 2026, 03:51 PM UTC

    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.

  15. identified Apr 09, 2026, 04:50 PM UTC

    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.

  16. identified Apr 09, 2026, 05:50 PM UTC

    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.

  17. identified Apr 09, 2026, 06:50 PM UTC

    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.

  18. monitoring Apr 09, 2026, 07:12 PM UTC

    The phased global rollout has been successfully completed. Systems are stable, and monitoring is ongoing to ensure continued normal operation.

  19. monitoring Apr 09, 2026, 09:37 PM UTC

    Services remain stable. Monitoring has been in progress and will continue for an extended period to ensure sustained stability and normal operation.

  20. resolved Apr 10, 2026, 01:16 AM UTC

    The incident has been resolved and normal service levels have been restored for the Imperva Advanced Bot Protection service.

Read the full incident report →

Minor April 5, 2026

[INC-1004] Potential CWAF issue on multiple Data Center

Detected by Pingoru
Apr 05, 2026, 02:02 PM UTC
Resolved
Apr 05, 2026, 02:55 PM UTC
Duration
53m
Affected: Ashburn, VA (IAD)Dallas, TX (DFW)London, UK (LCY)New York 1, NY (NYC)New York 2, NY (EWR)Paris, France (PAR)
Timeline · 3 updates
  1. investigating Apr 05, 2026, 02:02 PM UTC

    Technical teams are investigating a potential CWAF issue in the (DFW, EWR, IAD, LCY, NYC, PAR) Data Center . Further updates to follow.

  2. monitoring Apr 05, 2026, 02:39 PM UTC

    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.

  3. resolved Apr 05, 2026, 02:55 PM UTC

    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.

Read the full incident report →

Major March 27, 2026

[INC-1002] Johannesburg, South Africa (QRA) Data Center Issue

Detected by Pingoru
Mar 27, 2026, 12:23 PM UTC
Resolved
Mar 27, 2026, 01:32 PM UTC
Duration
1h 9m
Affected: Johannesburg, South Africa (QRA)
Timeline · 3 updates
  1. investigating Mar 27, 2026, 12:23 PM UTC

    Technical teams are investigating a potential issue in the Johannesburg, South Africa (QRA) 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.

  2. monitoring Mar 27, 2026, 12:32 PM UTC

    A fix has been implemented, and the issue has been mitigated. 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.

  3. resolved Mar 27, 2026, 01:32 PM UTC

    Some customer traffic being processed in Johannesburg, South Africa (QRA) PoP may have experienced higher than expected latency and packet loss due to an upstream provider issue, outside of the Thales Imperva Network. Engineers bypassed two impacted circuits in order to remove them from production, resulting in stabilized traffic. Services are now stable. Additional details will be provided following a completed root cause analysis.

Read the full incident report →

Major March 27, 2026

[INC-1001] Imperva GRE Performance Dashboard Issue across Multiple Data Center

Detected by Pingoru
Mar 27, 2026, 11:17 AM UTC
Resolved
Mar 27, 2026, 02:57 PM UTC
Duration
3h 39m
Affected: Network DDoS Management
Timeline · 6 updates
  1. investigating Mar 27, 2026, 11:17 AM UTC

    We have discovered a degradation in our statistics affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center . 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. investigating Mar 27, 2026, 12:28 PM UTC

    We are continuing to investigate the degradation affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center. 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.

  3. investigating Mar 27, 2026, 01:06 PM UTC

    Technical teams are continuing to investigate the degradation affecting the Imperva GRE Performance Dashboard across multiple data centers. 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. identified Mar 27, 2026, 01:56 PM UTC

    We have identified the source of the degradation affecting the Imperva GRE Performance Dashboard Issue across Multiple Data Center. Customer domains are still fully protected at this time. 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 Mar 27, 2026, 02:02 PM UTC

    Technical teams have performed remedial actions and the Imperva GRE Performance Dashboard are now correctly displaying data. No data has been lost during this event. 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.

  6. resolved Mar 27, 2026, 02:57 PM UTC

    The incident has been resolved and normal service levels have been restored for the Imperva GRE Performance Dashboard. 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 March 21, 2026

[INC-997] New York 2, NY (EWR) Data Center Issue

Detected by Pingoru
Mar 21, 2026, 06:00 AM UTC
Resolved
Mar 21, 2026, 09:33 AM UTC
Duration
3h 32m
Affected: New York 2, NY (EWR)
Timeline · 5 updates
  1. investigating Mar 21, 2026, 06:00 AM UTC

    Technical teams are investigating a potential issue in the New York 2, NY (EWR) 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.

  2. identified Mar 21, 2026, 06:07 AM UTC

    We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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 Mar 21, 2026, 06:44 AM UTC

    As a precautionary measure, the New York 2, NY (EWR) Data Center data center will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

  4. monitoring Mar 21, 2026, 09:01 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 Mar 21, 2026, 09: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 →

Minor March 20, 2026

[INC-996] DUS traffic degradation

Detected by Pingoru
Mar 20, 2026, 08:38 PM UTC
Resolved
Mar 21, 2026, 03:45 AM UTC
Duration
7h 7m
Affected: Dusseldorf, Germany (DUS)
Timeline · 5 updates
  1. investigating Mar 20, 2026, 08:38 PM UTC

    Technical teams are investigating a potential issue in the Dusseldorf, Germany (DUS) 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.

  2. identified Mar 20, 2026, 09:00 PM UTC

    We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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 Mar 20, 2026, 09:16 PM UTC

    As a precautionary measure, the Dusseldorf, Germany (DUS) data center will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

  4. monitoring Mar 21, 2026, 02:35 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 Mar 21, 2026, 03:45 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 March 15, 2026

[INC-994] Issue with Imperva Managed Certificates

Detected by Pingoru
Mar 15, 2026, 05:37 AM UTC
Resolved
Mar 15, 2026, 04:28 PM UTC
Duration
10h 50m
Affected: Third Party Services
Timeline · 7 updates
  1. investigating Mar 15, 2026, 05:37 AM UTC

    We are currently experiencing an issue with the certificate issuance process with our upstream certificate authority provider. As a result, ordering or issuing new certificates is temporarily unavailable at this time. This issue impacts all certificates managed through Imperva that require new issuance. Existing certificates and active services remain unaffected. Our engineering team is actively working with the relevant provider to investigate and resolve the issue as quickly as possible. Further updates will be shared as more information becomes available.

  2. identified Mar 15, 2026, 06:22 AM UTC

    Our engineering team is actively working with the third-party certificate authority provider to resolve the issue affecting the issuance of new certificates. We will continue to provide updates as progress is made toward restoring normal certificate ordering and issuance functionality.

  3. identified Mar 15, 2026, 08:05 AM UTC

    We are continuing to work with our certificate authority provider to resolve the issue affecting the ability to order or issue new certificates. Remediation efforts are currently in progress. Existing certificates and active services remain unaffected. Further updates will be provided as more information becomes available.

  4. identified Mar 15, 2026, 10:14 AM UTC

    We are continuing to work closely with our certificate authority provider to resolve the issue affecting certificate issuance. Efforts are ongoing to restore normal functionality as quickly as possible. We will provide further updates as additional information becomes available.

  5. identified Mar 15, 2026, 01:08 PM UTC

    We are continuing to work with our certificate authority provider to restore certificate issuance functionality. Existing certificates and active services remain unaffected. Further updates will be shared as more information becomes available.

  6. monitoring Mar 15, 2026, 03:38 PM UTC

    We are observing signs of recovery, and certificate issuance is beginning to function again. Our teams are currently validating system stability and monitoring the process closely.

  7. resolved Mar 15, 2026, 04:28 PM UTC

    The issue affecting certificate issuance has been resolved, and certificate ordering and issuance functionality have been fully restored.

Read the full incident report →

Minor March 11, 2026

[INC-992] Seoul (KOR) Data Center Issue

Detected by Pingoru
Mar 11, 2026, 05:46 PM UTC
Resolved
Mar 11, 2026, 08:29 PM UTC
Duration
2h 43m
Affected: Seoul, South Korea (KOR)Tokyo, Japan (TKO)
Timeline · 5 updates
  1. identified Mar 11, 2026, 05:46 PM UTC

    We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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 Mar 11, 2026, 05:50 PM UTC

    We have identified an issue in the data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. 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 Mar 11, 2026, 06:51 PM UTC

    As a precautionary measure, the Seoul (KOR) PoP will remain bypassed. Customer traffic continues to be served normally via alternate PoP, and no customer action is required at this time. Engineering teams will continue to investigate the issue, and further updates will be shared as changes are made or once the PoP is restored to normal operation.

  4. monitoring Mar 11, 2026, 08:07 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 Mar 11, 2026, 08:29 PM UTC

    Service in the Seoul (KOR) data center has been restored to normal.

Read the full incident report →

Minor March 6, 2026

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

Detected by Pingoru
Mar 06, 2026, 02:20 AM UTC
Resolved
Mar 06, 2026, 10:31 PM UTC
Duration
20h 10m
Affected: Tokyo, Japan (TKO)
Timeline · 5 updates
  1. investigating Mar 06, 2026, 02:20 AM UTC

    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.

  2. investigating Mar 06, 2026, 02:32 AM UTC

    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.

  3. identified Mar 06, 2026, 09:47 AM UTC

    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.

  4. monitoring Mar 06, 2026, 09:17 PM UTC

    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.

  5. resolved Mar 06, 2026, 10:31 PM UTC

    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.

Read the full incident report →

Minor March 5, 2026

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

Detected by Pingoru
Mar 05, 2026, 10:30 PM UTC
Resolved
Mar 06, 2026, 05:58 AM UTC
Duration
7h 27m
Affected: Chicago 2, IL (CHI)
Timeline · 5 updates
  1. investigating Mar 05, 2026, 10:30 PM UTC

    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.

  2. identified Mar 05, 2026, 10:49 PM UTC

    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.

  3. identified Mar 05, 2026, 11:41 PM UTC

    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.

  4. monitoring Mar 06, 2026, 05:45 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 Mar 06, 2026, 05:58 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 March 5, 2026

[INC-987] Issue with Cache Purge

Detected by Pingoru
Mar 05, 2026, 05:19 PM UTC
Resolved
Mar 05, 2026, 10:59 PM UTC
Duration
5h 39m
Affected: Web Application Performance
Timeline · 6 updates
  1. investigating Mar 05, 2026, 05:19 PM UTC

    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.

  2. identified Mar 05, 2026, 05:57 PM UTC

    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.

  3. identified Mar 05, 2026, 06:48 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Mar 05, 2026, 07:52 PM UTC

    Our engineering teams have made progress in addressing the issue affecting cache purge functionality, and remediation efforts are ongoing.

  5. identified Mar 05, 2026, 10:11 PM UTC

    We are continuing to work on a fix for this issue.

  6. resolved Mar 05, 2026, 10:59 PM UTC

    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.

Read the full incident report →

Major March 3, 2026

[INC-984] Attack Analytic Issue

Detected by Pingoru
Mar 03, 2026, 01:04 PM UTC
Resolved
Mar 03, 2026, 08:26 PM UTC
Duration
7h 21m
Affected: Attack Analytic
Timeline · 4 updates
  1. investigating Mar 03, 2026, 01:04 PM UTC

    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.

  2. identified Mar 03, 2026, 01:33 PM UTC

    We have identified the source of the issue affecting Attack Analytics. Technical teams are planning remedial action. Further updates to follow.

  3. monitoring Mar 03, 2026, 02:32 PM UTC

    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.

  4. resolved Mar 03, 2026, 08:26 PM UTC

    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.

Read the full incident report →

Major March 3, 2026

[INC-983] API Security Issue

Detected by Pingoru
Mar 03, 2026, 11:57 AM UTC
Resolved
Mar 03, 2026, 02:35 PM UTC
Duration
2h 37m
Affected: API Security Management
Timeline · 5 updates
  1. investigating Mar 03, 2026, 11:57 AM UTC

    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.

  2. investigating Mar 03, 2026, 12:12 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 03, 2026, 12:53 PM UTC

    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.

  4. monitoring Mar 03, 2026, 01:35 PM UTC

    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

  5. resolved Mar 03, 2026, 02:35 PM UTC

    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.

Read the full incident report →

Minor February 27, 2026

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

Detected by Pingoru
Feb 27, 2026, 12:10 PM UTC
Resolved
Feb 28, 2026, 12:26 AM UTC
Duration
12h 16m
Affected: Istanbul, Turkey (SAW)
Timeline · 6 updates
  1. investigating Feb 27, 2026, 12:10 PM UTC

    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.

  2. identified Feb 27, 2026, 12:44 PM UTC

    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.

  3. identified Feb 27, 2026, 02:19 PM UTC

    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.

  4. identified Feb 27, 2026, 05:54 PM UTC

    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.

  5. monitoring Feb 27, 2026, 11:36 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.

  6. resolved Feb 28, 2026, 12:26 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 →

Minor February 25, 2026

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

Detected by Pingoru
Feb 25, 2026, 04:27 AM UTC
Resolved
Feb 25, 2026, 10:11 AM UTC
Duration
5h 44m
Affected: Tokyo, Japan (TKO)
Timeline · 3 updates
  1. identified Feb 25, 2026, 04:27 AM UTC

    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.

  2. monitoring Feb 25, 2026, 09:12 AM UTC

    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.

  3. resolved Feb 25, 2026, 10:11 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 →

Minor February 20, 2026

[INC-979] Vancouver, Canada (VAN) Data Center Issue

Detected by Pingoru
Feb 20, 2026, 07:55 AM UTC
Resolved
Feb 20, 2026, 08:16 AM UTC
Duration
20m
Affected: Vancouver, Canada (VAN)
Timeline · 4 updates
  1. investigating Feb 20, 2026, 07:55 AM UTC

    Technical teams are investigating a potential issue in the Vancouver, Canada (VAN) 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.

  2. identified Feb 20, 2026, 08:06 AM 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 Feb 20, 2026, 08:10 AM 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 Feb 20, 2026, 08:16 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 →

Notice February 19, 2026

[INC-978] Sydney, Australia , Melbourne, Australia (MEB) Data Center Issue

Detected by Pingoru
Feb 19, 2026, 02:10 PM UTC
Resolved
Feb 19, 2026, 03:13 PM UTC
Duration
1h 3m
Affected: Melbourne, Australia (MEB)Sydney, Australia (SYD)
Timeline · 2 updates
  1. monitoring Feb 19, 2026, 02:10 PM UTC

    We experienced a brief issue impacting the Sydney Australia (SYD) and Melbourne, Australia (MEB) data center for 34 minutes (12:48–13:22 UTC). The issue has been resolved, and our technical teams are actively monitoring services at these location. 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 SYD and MEB 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 Feb 19, 2026, 03:13 PM 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 →

Critical February 19, 2026

[INC-977] Imperva Support Portal Access Issue

Detected by Pingoru
Feb 19, 2026, 08:15 AM UTC
Resolved
Feb 19, 2026, 10:32 AM UTC
Duration
2h 17m
Timeline · 6 updates
  1. investigating Feb 19, 2026, 08:15 AM UTC

    We have discovered a potential service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable. 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 Feb 19, 2026, 08:36 AM UTC

    We have discovered a potential service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable due to connectivity issues. Technical teams are currently investigating potential issues with a third-party provider. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our 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. investigating Feb 19, 2026, 08:51 AM UTC

    We have discovered a potential service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable due to connectivity issues. This issue is also affecting our teams' ability to connect to our telephony system. We are treating this matter with the highest priority. Technical teams are currently investigating potential issues with a third-party provider. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

  4. identified Feb 19, 2026, 09:53 AM UTC

    We have identified a potential cause for the service degradation, affecting customers ability to access the Imperva Support Portal as the portal is temporarily unavailable due to connectivity issues. This issue is also affecting our teams' ability to connect to our telephony system. We are treating this matter with the highest priority. Technical teams are currently investigating potential issues with our third-party provider. Further updates to follow. The status updates are an integral part of proactive monitoring and transparent communication about the status of our services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service.

  5. monitoring Feb 19, 2026, 10:06 AM UTC

    Technical teams have performed remedial actions and the Imperva Support Portal access is returning to normal operations. 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.

  6. resolved Feb 19, 2026, 10:32 AM UTC

    The incident has been resolved and normal service levels have been restored. We apologize for any inconvenience that this issue may have caused. 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 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 →

Looking to track Imperva downtime and outages?

Pingoru polls Imperva's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Imperva reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Imperva alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Imperva for free

5 free monitors · No credit card required