Incapsula Outage History

Incapsula is up right now

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

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

Source: https://status.incapsula.com

Major May 6, 2026

[INC-1022] Issue with Cloud WAF Protected Websites

Detected by Pingoru
May 06, 2026, 11:36 AM UTC
Resolved
May 06, 2026, 03:04 PM UTC
Duration
3h 27m
Affected: Web Application Performance
Timeline · 8 updates
  1. investigating May 06, 2026, 11:36 AM UTC

    We are investigating a potential issue impacting Cloud WAF Protected Websites. Some websites may fail to load or return errors. Customer domains remain fully protected at this time. Our technical teams are actively working to identify the root cause, and further updates will be shared as more information becomes available. The status updates are an integral part of proactive monitoring and transparent communication about the status of our cloud services. Imperva investigates and attributes a status to all detected events that may or may not affect availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

  2. identified May 06, 2026, 11:53 AM UTC

    We have identified the issue, and a fix is currently being implemented. The next Status Update on this Incident will be provided no later than 12:22 UTC.

  3. identified May 06, 2026, 12:25 PM UTC

    We are continuing to actively work on implementing a fix. The next Status Update on this Incident will be provided no later than 12:55 UTC.

  4. investigating May 06, 2026, 12:41 PM UTC

    Our investigation has determined that the previously suspected cause may be one contributing factor within a broader underlying root-cause pattern than initially identified. We are continuing to investigate and actively working to identify the underlying cause. The next Status Update on this Incident will be provided no later than 13:11 UTC.

  5. investigating May 06, 2026, 01:10 PM UTC

    We are continuing to actively investigate this issue. The next Status Update on this Incident will be provided no later than 13:39 UTC.

  6. investigating May 06, 2026, 01:43 PM UTC

    We are actively investigating this issue and continuing our efforts to identify the cause of the issue. The next Status Update on this Incident will be provided no later than 14:13 UTC.

  7. monitoring May 06, 2026, 02:04 PM UTC

    A fix has been implemented, and services have returned to normal. We are continuing to monitor the situation closely to ensure stability. The next Status Update on this Incident will be provided no later than 15:04 UTC.

  8. resolved May 06, 2026, 03:04 PM UTC

    The issue has been resolved, and monitoring has confirmed service stability.

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 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 →

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 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 →

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 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 →