Incapsula Outage History

Incapsula degraded · 1 active incident View live status →

Incapsula had 103 outages in the last 2 years totaling 709h 31m of downtime — averaging 4.2 incidents per month.

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

Source: https://status.incapsula.com

Minor September 17, 2026

[INC-1136] Service Degradation Affecting SIEM Log Ingestion

Detected by Pingoru
Sep 17, 2026, 11:52 PM UTC
Resolved
Sep 18, 2026, 01:30 AM UTC
Duration
1h 37m
Affected: SIEM Logs
Timeline · 5 updates
  1. investigating Sep 17, 2026, 11:11 PM UTC

    We are investigating an issue where some customers may receive SIEM logs from IP addresses that are no longer expected to be in use. Our teams are actively investigating the issue and working to identify the cause. We will provide further updates as more information becomes available.

  2. investigating Sep 17, 2026, 11:52 PM UTC

    We have identified the source of the issue affecting a subset of customers, resulting in SIEM logs being received from IP addresses that are no longer expected to be in use. Our teams are actively implementing mitigation measures to reduce customer impact and restore expected behavior. We will provide further updates as they become available.

  3. identified Sep 18, 2026, 12:25 AM UTC

    Our teams continue to work on implementing mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. Efforts remain focused on reducing customer impact and restoring expected behavior. We will provide additional updates as progress is made.

  4. monitoring Sep 18, 2026, 12:59 AM UTC

    Our teams have successfully implemented mitigation measures to address the issue causing some customers to receive SIEM logs from IP addresses that are no longer expected to be in use. The observed impact has been mitigated, and services are operating as expected at this time. We are continuing to closely monitor the environment to ensure ongoing stability and confirm the effectiveness of the mitigation. The next update on the issue will be shared no later than 01:30 UTC.

  5. resolved Sep 18, 2026, 01:30 AM UTC

    Mitigation measures have been successfully implemented, and after a period of monitoring, our teams have confirmed that services are operating as expected with no further impact observed. This incident is now resolved. We apologize for any inconvenience and thank you for your patience while we worked to address this issue.

Read the full incident report →

Minor September 17, 2026

[INC-1135] Service Degradation Causing Intermittent DNS Resolution Issues

Detected by Pingoru
Sep 17, 2026, 06:57 PM UTC
Resolved
Sep 18, 2026, 12:09 AM UTC
Duration
5h 11m
Affected: CDN and WAF Management
Timeline · 8 updates
  1. investigating Sep 17, 2026, 06:57 PM UTC

    We are currently investigating an issue that may cause intermittent DNS resolution failures for some customers. Our teams are actively investigating the issue and working to identify the cause and restore consistent DNS resolution. We will provide further updates as more information becomes available.

  2. investigating Sep 17, 2026, 07:39 PM UTC

    We continue to investigate intermittent DNS resolution issues that may affect a small number of requests. The issue is highly intermittent and remains limited in scope. Our teams are actively investigating the issue and working to identify the cause and ensure consistent DNS resolution. The next update on this issue will be shared no later than 20:10 UTC.

  3. identified Sep 17, 2026, 07:50 PM UTC

    The issue has been identified, and our teams have confirmed the cause of the intermittent DNS resolution failures. The team is currently applying the mitigation in a controlled manner across the affected services. The issue remains intermittent and limited in scope. The next update on the issue will be shared no later that 20:20 UTC.

  4. identified Sep 17, 2026, 08:24 PM UTC

    Mitigation efforts are continuing. We are seeing recovery as the targeted fix is progressively applied to the affected services. The next update on the issue will be shared no later than 20:55 UTC.

  5. identified Sep 17, 2026, 08:55 PM UTC

    Mitigation and validation efforts are continuing. The team is closely monitoring the service while applying the targeted fix across the remaining affected systems and validating recovery. The next update on the issue will be shared no later than 21:25 UTC.

  6. identified Sep 17, 2026, 09:34 PM UTC

    Mitigation and validation efforts remain ongoing. The team continues to apply the targeted fix to the remaining affected systems while closely monitoring the service and validating recovery. The next update on the issue will be shared no later than 22:05 UTC.

  7. monitoring Sep 17, 2026, 10:04 PM UTC

    The team has completed the mitigation, and the affected services have been validated to be operating as expected. We will continue to closely monitor the service to ensure the fix remains effective and services remains stable.

  8. resolved Sep 18, 2026, 12:09 AM UTC

    The services are now stable, and the issue has been fully mitigated. Post-mitigation validation has been completed, confirming that the services are operating as expected. The incident is now considered resolved.

Read the full incident report →

Minor September 17, 2026

[INC-1134] Degradation of performance in Imperva Management Console

Detected by Pingoru
Sep 17, 2026, 09:45 AM UTC
Resolved
Sep 17, 2026, 10:19 AM UTC
Duration
33m
Affected: Cloud Security Management Platform
Timeline · 3 updates
  1. investigating Sep 17, 2026, 09:45 AM UTC

    We are investigating an issue affecting the performance of the Imperva Management Console (MY). Customers may encounter elevated latency, login failures, or degraded console performance. Our engineering teams are engaged and investigating the issue with high priority. We will continue to provide updates as our investigation progresses. The next update will not be later than 10:15 UTC.

  2. monitoring Sep 17, 2026, 09:56 AM UTC

    The issue affecting the Imperva Management Console (MY) has been resolved, and service has been restored. Customers should now be able to access and use the console normally. Our team will continue to closely monitor the service to ensure stability. The next update will be no later than 10:30 UTC

  3. resolved Sep 17, 2026, 10:19 AM UTC

    The issue affecting the Imperva Management Console (MY) has been resolved. Service performance has returned to normal, and customers should no longer experience elevated latency, login issues, or general console degradation. We will continue to monitor the environment to ensure stability. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Minor September 8, 2026

Network connectivity degradation in MAD PoP

Detected by Pingoru
Sep 08, 2026, 05:03 AM UTC
Resolved
Sep 08, 2026, 05:37 AM UTC
Duration
34m
Affected: Madrid, Spain (MAD)
Timeline · 4 updates
  1. investigating Sep 08, 2026, 05:03 AM UTC

    We have identified an issue in the Madrid, Spain 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. _ _ Further updates will be shared as more information becomes available.

  2. identified Sep 08, 2026, 05:22 AM UTC

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

  3. monitoring Sep 08, 2026, 05:26 AM UTC

    Traffic has been restored to the Madrid, Spain (MAD) Data Center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.

  4. resolved Sep 08, 2026, 05:37 AM UTC

    Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service.

Read the full incident report →

Minor September 2, 2026

[INC-1120 ] Service Degradation affecting a subset of customers in North America region

Detected by Pingoru
Sep 02, 2026, 08:21 PM UTC
Resolved
Sep 03, 2026, 12:33 AM UTC
Duration
4h 12m
Affected: Chicago 2, IL (CHI)Detroit, MI (DET)Houston, TX (HOU)Los Angeles, CA (SNA)Montreal, Canada (YUL)New York 2, NY (EWR)Miami, FL (FLL)
Timeline · 3 updates
  1. investigating Sep 02, 2026, 08:21 PM UTC

    Imperva has been alerted to the fact that there have been two major fiber cuts in North America. These fiber cuts are within the network of a major upstream carrier. A subset of customer traffic coming to or going from the Imperva network may transit this infrastructure and as a result of this issue, customers may experience connectivity issues, increased latency, or service degradation. We will provide further updates as more information becomes available. The next update will be before 20:50 UTC

  2. monitoring Sep 02, 2026, 08:46 PM UTC

    We have rerouted traffic away from the affected carrier in the impacted PoPs, mitigating customer impact. We will continue to closely monitor the environment to ensure ongoing service stability.

  3. resolved Sep 03, 2026, 12:33 AM UTC

    Monitoring has shown stable performance following the mitigation measures implemented earlier. This incident is considered resolved at this time. We will continue to monitor the environment as part of our standard operational practices to ensure ongoing service stability.

Read the full incident report →

Major September 2, 2026

[INC-1118] Rio de Janeiro, Brazil (RIO) Data Center Issue

Detected by Pingoru
Sep 02, 2026, 04:56 AM UTC
Resolved
Sep 02, 2026, 07:16 AM UTC
Duration
2h 20m
Affected: Rio de Janeiro, Brazil (RIO)
Timeline · 7 updates
  1. investigating Sep 02, 2026, 04:56 AM UTC

    We have identified an issue in the Rio de Janeiro, Brazi 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. Further updates will be shared as more information becomes available.

  2. investigating Sep 02, 2026, 05:34 AM UTC

    The team is continuing to work on resolving the issue. To maintain service availability, traffic is being rerouted through an alternate data center in the region. During this time, customers may experience increased latency while the reroute remains in effect. Further updates will be shared as more information becomes available.

  3. investigating Sep 02, 2026, 06:18 AM UTC

    Our team is actively investigating and working to resolve the issue. To maintain service availability, traffic has been temporarily rerouted through an alternate data center in the region. During this time, customers may experience increased latency. Further updates will be shared as more information becomes available.

  4. investigating Sep 02, 2026, 06:59 AM UTC

    The issue has been identified, and technical teams are actively working on remediation. Customer traffic continues to be served normally through an alternate PoP. The next update will be provided no later than 07:30 UTC.

  5. identified Sep 02, 2026, 07:00 AM UTC

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

  6. monitoring Sep 02, 2026, 07:03 AM UTC

    Technical team has successfully activated the PoP, and traffic has been restored to the Janeiro, Brazil (RIO) Data Center. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service.

  7. resolved Sep 02, 2026, 07:16 AM UTC

    Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service.

Read the full incident report →

Major August 21, 2026

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

Detected by Pingoru
Aug 21, 2026, 07:28 PM UTC
Resolved
Aug 21, 2026, 10:42 PM UTC
Duration
3h 14m
Affected: Istanbul, Turkey (SAW)
Timeline · 5 updates
  1. investigating Aug 21, 2026, 07:28 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. Next update on the incident will be shared no later than 19:41 UTC

  2. identified Aug 21, 2026, 08:02 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.

  3. identified Aug 21, 2026, 08:56 PM UTC

    Our teams remain actively engaged in the investigation and remediation. Customers may experience increased latency while traffic remains rerouted. We will provide further updates as additional information becomes available.

  4. monitoring Aug 21, 2026, 09:41 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.

  5. resolved Aug 21, 2026, 10:42 PM UTC

    Monitoring has confirmed that the PoP is stable and operating normally. The incident has been resolved.

Read the full incident report →

Minor August 19, 2026

[INC-1109] Frankfurt (HHN) Data Center Issue

Detected by Pingoru
Aug 19, 2026, 03:04 AM UTC
Resolved
Aug 19, 2026, 03:55 AM UTC
Duration
50m
Affected: Frankfurt, Germany (HHN)
Timeline · 2 updates
  1. monitoring Aug 19, 2026, 03:04 AM UTC

    We have discovered a service degradation that affected the Frankfurt (HHN) Data Center Issue which may have resulted in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Service was restored in the PoP, mitigating the impact to customers.

  2. resolved Aug 19, 2026, 03:55 AM UTC

    Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident.

Read the full incident report →

Notice August 7, 2026

[INC-1102] Data Center Issues

Detected by Pingoru
Aug 07, 2026, 05:08 PM UTC
Resolved
Aug 07, 2026, 07:50 PM UTC
Duration
2h 41m
Affected: Denver, CO (DEN)New York 1, NY (NYC)New York 2, NY (EWR)San Jose, CA (SFO)Seattle, WA (SEA)
Timeline · 4 updates
  1. investigating Aug 07, 2026, 05:08 PM UTC

    We identified a brief issue impacting our Points of Presence (PoPs), which may have caused infrastructure tunnel disconnections and intermittent website timeouts for some customers. The issue has now recovered, and services are operating normally. Our teams are actively monitoring the platform to ensure continued stability.

  2. investigating Aug 07, 2026, 05:58 PM UTC

    Services remain stable across all previously affected Points of Presence (PoPs). Our teams continue to closely monitor the environment and analyze the event to confirm the underlying cause and ensure the continued stability of our services.

  3. monitoring Aug 07, 2026, 06:57 PM UTC

    A potential contributing factor has been identified. Services remain stable across all affected Points of Presence (PoPs), and no further issues have been observed since recovery. Our teams continue to closely monitor the environment to ensure ongoing service stability.

  4. resolved Aug 07, 2026, 07:50 PM UTC

    The incident has been resolved, and services have remained stable across all affected Points of Presence (PoPs).

Read the full incident report →

Minor August 5, 2026

[INC-1101] Real-Time WAF Alerting Service Degradation

Detected by Pingoru
Aug 05, 2026, 11:56 AM UTC
Resolved
Aug 05, 2026, 12:56 PM UTC
Duration
59m
Affected: CDN and WAF Management
Timeline · 4 updates
  1. investigating Aug 05, 2026, 11:56 AM UTC

    We are currently investigating reports of a potential issue affecting the generation and/or delivery of real-time WAF alerts. Some customers may experience delays in receiving WAF alerts or observe that expected real-time notifications are not being triggered. We are actively assessing the scope and impact of the issue and will provide further updates as more information becomes available. WAF protection remains fully operational. This issue affects real-time alerts only and does not impact traffic inspection or policy enforcement. Our next update will be provided as soon as we have additional information to share.

  2. identified Aug 05, 2026, 12:23 PM UTC

    We have identified the underlying cause of the issue affecting real-time WAF alerts. Our investigation indicates that the impact is limited to a subset of customers. WAF protection remains fully operational. This issue affects real-time alerting only and does not impact traffic inspection or policy enforcement. Our teams are working on mitigation and validation efforts. We will provide further updates as we make progress toward resolution. Our next update will be before 12:55 PM UTC

  3. monitoring Aug 05, 2026, 12:35 PM UTC

    A fix has been implemented to address the issue affecting real-time WAF alerts, and we are observing recovery across impacted services. WAF protection remained fully operational throughout the incident. The issue was limited to real-time alerting and did not impact traffic inspection or policy enforcement. We are currently monitoring the environment to ensure alert delivery has returned to normal operation and that no further issues are observed. We will continue to provide updates as warranted.

  4. resolved Aug 05, 2026, 12:56 PM UTC

    The issue affecting real-time WAF alerts has been resolved. Following the implementation of a fix and a period of monitoring, we have confirmed that real-time WAF alert delivery has returned to normal operation. WAF protection remained fully operational throughout the incident, and traffic inspection and policy enforcement were not impacted. We apologise for any inconvenience caused and appreciate your patience while we worked to resolve this issue.

Read the full incident report →

Minor July 27, 2026

[INC-1092] Support Ticketing System Issue

Detected by Pingoru
Jul 27, 2026, 06:09 AM UTC
Resolved
Jul 27, 2026, 08:32 AM UTC
Duration
2h 23m
Affected: Support Ticketing System
Timeline · 4 updates
  1. investigating Jul 27, 2026, 06:09 AM UTC

    We are investigating a potential issue affecting the Support Ticketing System. Customers may be experiencing issues logging into the Support Portal. Our technical teams are actively investigating the issue. The next update on the issue will be shared no later than 6:39 UTC.

  2. investigating Jul 27, 2026, 06:49 AM UTC

    Our teams are actively working to restore access to the Support Ticketing System. While this work is ongoing, customers experiencing issues accessing the Support Portal can reach our Support team for urgent assistance by calling +1 410 469 1651. Thank you for your patience as we work to resolve the issue.

  3. monitoring Jul 27, 2026, 07:45 AM UTC

    The issue preventing some customers from logging in to the Customer Support Portal has been resolved. Technical teams have completed remedial actions, and the portal has returned to normal operation. We are continuing to monitor the service to ensure stability and will provide a final update once monitoring is complete.

  4. resolved Jul 27, 2026, 08:32 AM UTC

    The issue that prevented some customers from logging in to the Customer Support Portal has been fully resolved. Technical teams implemented corrective actions and validated that normal login functionality has been restored. The Customer Support Portal is operating normally, and no further customer impact has been observed. We apologise for the inconvenience and appreciate your patience while we worked to resolve this issue. The incident is now closed.

Read the full incident report →

Major July 10, 2026

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

Detected by Pingoru
Jul 10, 2026, 03:38 PM UTC
Resolved
Jul 10, 2026, 11:38 PM UTC
Duration
8h
Affected: Johannesburg, South Africa (QRA)
Timeline · 5 updates
  1. investigating Jul 10, 2026, 03:38 PM UTC

    We have identified a potential issue in the Johannesburg, South Africa (QRA) 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 Jul 10, 2026, 04:04 PM UTC

    The team has identified the underlying issue and implemented a fix. To ensure business continuity and validate service stability, the Johannesburg, South Africa (QRA) PoP is scheduled to be reactivated at 23:00 UTC . In the meantime, traffic is being rerouted through an alternate data center in the region. Customers may experience increased latency and intermittent timeouts while the reroute remains in place. The team continues to closely monitor the environment . Next update on the issue will be shared no later than 23:00 UTC.

  3. identified Jul 10, 2026, 11:06 PM UTC

    Our team is currently working to reactivate the affected Point of Presence (PoP). We will provide another update once the PoP has been successfully restored. In the meantime, traffic is being rerouted through an alternate data center within the region to maintain service availability. During this period, customers may experience increased latency and intermittent timeouts. The team continues to closely monitor the environment and is actively working to restore normal service as quickly as possible. Next update on the issue will be shared no later than 23:36 UTC.

  4. monitoring Jul 10, 2026, 11:10 PM UTC

    Technical team has successfully activated the PoP, and traffic has been restored to the Johannesburg, South Africa (QRA) PoP. Verification testing and continuous monitoring are currently underway to validate stability and confirm the PoP is fully operational and ready for service. Next Status Update on this Incident will be provided no later than 23:40 UTC.

  5. resolved Jul 10, 2026, 11:38 PM UTC

    Technical team implemented the necessary fixes, completed validation activities, and confirmed service stability through continuous monitoring. All services are operating normally. PoP is fully operational and ready for service. We appreciate your patience and understanding throughout this incident.

Read the full incident report →

Minor June 11, 2026

[INC-1066] Increased Latency for a portion of Imperva Cloud WAF Protected Sites

Detected by Pingoru
Jun 11, 2026, 08:07 AM UTC
Resolved
Jun 11, 2026, 08:39 AM UTC
Duration
32m
Affected: Web Application Performance
Timeline · 3 updates
  1. investigating Jun 11, 2026, 08:07 AM UTC

    We are currently investigating increased latency affecting Imperva Cloud WAF protected sites. At this time, a portion of Imperva Cloud WAF customers may experience slower response times when accessing protected applications through Imperva. Our teams are actively investigating the cause and working to mitigate the impact. We will provide another update as more information becomes available. The next update will be at 08:36 UTC at the latest.

  2. monitoring Jun 11, 2026, 08:15 AM UTC

    The issue causing increased latency for Imperva Cloud WAF protected sites has been mitigated. Service performance has returned to normal, and our teams are continuing to monitor closely to ensure continued stability. We will provide a final update once monitoring is complete. Please note service impact continued for approximately 10 minutes.

  3. resolved Jun 11, 2026, 08:39 AM UTC

    This issue has been resolved. Our teams have confirmed that service performance for Imperva Cloud WAF protected sites has returned to normal and remained stable following mitigation. We will continue to monitor service health as part of our standard operational processes. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Minor June 10, 2026

[INC-1065 ] Imperva Management Portal Login Issue

Detected by Pingoru
Jun 10, 2026, 06:53 PM UTC
Resolved
Jun 11, 2026, 12:43 AM UTC
Duration
5h 49m
Affected: Cloud Security Management Platform
Timeline · 8 updates
  1. investigating Jun 10, 2026, 06:53 PM UTC

    We have discovered a potential service degradation, affecting customers ability to log in to the Imperva Management Portal. Technical teams are investigating. Further updates to follow. Next update on the issue will be provided no later than 19:23 UTC.

  2. investigating Jun 10, 2026, 07:24 PM UTC

    The team continues to actively investigate the issue and work toward resolution. At this time, the impact is limited to customer access to the Management Portal. Customer websites and protection services remain fully operational and continue to be protected as expected. Next update on the issue will be provided no later than 19:54 UTC.

  3. investigating Jun 10, 2026, 07:54 PM UTC

    Technical teams continue to actively investigate the issue. A potential contributing factor has been identified, and teams are currently working to validate and address it. Next update on the issue will be provided no later than 20:24 UTC.

  4. identified Jun 10, 2026, 08:19 PM UTC

    We have identified the underlying cause of the issue and have applied a fix. The issue affected access to the Management Portal and a subset of API requests. We are seeing signs of recovery following the implementation of the fix, and our teams are actively validating service restoration across the impacted components. Next update on the issue will be provided no later than 20:50 UTC.

  5. monitoring Jun 10, 2026, 08:42 PM UTC

    A fix has been successfully implemented, and services have been restored. Our teams have validated the recovery and are continuing to closely monitor the environment to ensure ongoing stability. Next update on the issue will be provided no later than 21:42 UTC.

  6. monitoring Jun 10, 2026, 09:43 PM UTC

    Services remain stable following the implementation of the fix, and no further issues have been observed. Our teams will continue to closely monitor the environment for an extended period to ensure stability. Next update on the issue will be provided no later than 23:43 UTC.

  7. monitoring Jun 10, 2026, 11:47 PM UTC

    Services remain stable, and no further issues have been observed. Our teams will continue to closely monitor the environment to ensure ongoing stability and verify that all services continue to operate as expected. Next update on the issue will be provided no later than 01:45 UTC on 11 June 2026.

  8. resolved Jun 11, 2026, 12:43 AM UTC

    Monitoring has confirmed that services remain stable following the implementation of the fix and the completion of validation activities. No further issues have been observed.

Read the full incident report →