Imperva Outage History

Imperva is up right now

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

Source: https://status.imperva.com

Minor February 13, 2026

[INC-975] Sydney, Australia (SYD) Data Center Issue

Detected by Pingoru
Feb 13, 2026, 09:58 AM UTC
Resolved
Feb 13, 2026, 08:53 PM UTC
Duration
10h 54m
Affected: Sydney, Australia (SYD)
Timeline · 7 updates
  1. monitoring Feb 13, 2026, 09:58 AM UTC

    Due to an issue with IPv6 traffic in our Sydney, Australia (SYD) Data Center, IPv6 traffic from SYD has been rerouted away, through an alternative data center in the region. Customers may encounter some latency on IPv6 traffic in the region while we resolve this issue. IPv4 traffic is unaffected and continues to be served by our SYD data center. 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 13, 2026, 10:18 AM UTC

    Due to an issue with IPv6 traffic in our Sydney, Australia (SYD) Data Center, IPv6 traffic from SYD has been rerouted away, through an alternative data center in the region. Customers may encounter some latency on IPv6 traffic in the region while we resolve this issue. IPv4 traffic is unaffected and continues to be served by our SYD data center. 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 13, 2026, 01:08 PM UTC

    Technical teams are continuing to working on a fix for the data center issue. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  4. investigating Feb 13, 2026, 03:56 PM UTC

    The technical teams are currently investigating a potential issue and have deactivated the Sydney (SYD) Data Center, Australia. Traffic has been rerouted to an alternate data center within the same region to maintain service continuity 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 Feb 13, 2026, 05:36 PM UTC

    The issue has been identified, and our technical teams are actively working on implementing a fix. The Sydney (SYD) Data Center remains temporarily deactivated while remediation activities are in progress. Traffic continues to be rerouted to an alternate data center within the same region to maintain service continuity. 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. monitoring Feb 13, 2026, 08:16 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.

  7. resolved Feb 13, 2026, 08:53 PM UTC

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

Read the full incident report →

Minor February 12, 2026

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

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

    We are investigating an issue in the Stockholm, Sweden (STO) data center. Traffic is being rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

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

    We are continuing to investigate this issue.

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

    Due to an issue in the data center traffic remains rerouted through an alternate data center in the region. Customers may encounter some latency for the duration of time that the reroute is in place. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

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

    A fix has been implemented and traffic has been restored to the data center. We are continuing to monitor in order to ensure that service has returned to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

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

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

Read the full incident report →

Major February 3, 2026

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

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

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

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

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

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

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

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

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

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

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

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

    We deactivated the problematic component and issue has been remediated. We are continuing to monitor in order to ensure that service has returned to normal. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

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

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

Read the full incident report →

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