Time: March 13, 2024, 3:03 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: March 13, 2024, 1:43 p.m.

Status: Monitoring

Update: We are currently processing all security events from the time of the incident, which might result in delays for customers accessing them in the Imperva Cloud Security console. Our estimated completion time is 6 hours. 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.

Time: March 13, 2024, 9:29 a.m.

Status: Monitoring

Update: Technical teams have performed remedial actions, and service is returning to normal operations. Although we are still processing all the data, customers may experience a delay in receiving the events. 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.

Time: March 13, 2024, 8:44 a.m.

Status: Identified

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

Time: March 13, 2024, 7 a.m.

Status: Identified

Update: We have identified the source of the issue affecting security events in the US region, which may result in delays in receiving security events in the US region in the next few hours. 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.

Time: March 13, 2024, 3:49 a.m.

Status: Investigating

Update: We have discovered a potential service degradation affecting the Security events dashboard in the US region. No data has been lost during this event. However, customers may experience some delays in receiving the Security events in the next hours. 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 status to all detected events that may or may not affect the availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Time: March 13, 2024, 3:03 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: March 13, 2024, 1:43 p.m.

Status: Monitoring

Update: We are currently processing all security events from the time of the incident, which might result in delays for customers accessing them in the Imperva Cloud Security console. Our estimated completion time is 6 hours. 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.

Time: March 13, 2024, 9:29 a.m.

Status: Monitoring

Update: Technical teams have performed remedial actions, and service is returning to normal operations. Although we are still processing all the data, customers may experience a delay in receiving the events. 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.

Time: March 13, 2024, 8:44 a.m.

Status: Identified

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

Time: March 13, 2024, 7 a.m.

Status: Identified

Update: We have identified the source of the issue affecting security events in the US region, which may result in delays in receiving security events in the US region in the next few hours. 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.

Time: March 13, 2024, 3:49 a.m.

Status: Investigating

Update: We have discovered a potential service degradation affecting the Security events dashboard in the US region. No data has been lost during this event. However, customers may experience some delays in receiving the Security events in the next hours. 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 status to all detected events that may or may not affect the availability of the service. In the event of a service disruption, the update will include potential impacts to any affected region.

Time: March 4, 2024, 9:32 p.m.

Status: Resolved

Update: Service for the Istanbul (IST) PoP has remained stable and functioning normally. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.

Time: March 4, 2024, 9:32 p.m.

Status: Resolved

Update: Service for the Istanbul (IST) PoP has remained stable and functioning normally. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.

Time: March 4, 2024, 9:12 p.m.

Status: Monitoring

Update: A fix has been implemented and service has been restored to the Istanbul (IST) PoP. We are monitoring to ensure continued stability. Further updates will be provided as information becomes available.

Time: March 4, 2024, 9:12 p.m.

Status: Monitoring

Update: A fix has been implemented and service has been restored to the Istanbul (IST) PoP. We are monitoring to ensure continued stability. Further updates will be provided as information becomes available.

Time: March 4, 2024, 9 p.m.

Status: Identified

Update: We have identified the source of the service disruption affecting the Istanbul (IST) PoP to be a device in the PoP experienced a service fault. We are working on remedial actions to mitigate the impact to customers at this time. Further updates will be provided as information becomes available.

Time: March 4, 2024, 9 p.m.

Status: Identified

Update: We have identified the source of the service disruption affecting the Istanbul (IST) PoP to be a device in the PoP experienced a service fault. We are working on remedial actions to mitigate the impact to customers at this time. Further updates will be provided as information becomes available.

Time: March 4, 2024, 8:40 p.m.

Status: Investigating

Update: We have discovered a service disruption that is affecting the Istanbul (IST) PoP, which may result in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Investigation into the cause of the service disruption is currently ongoing. Further updates will be provided as information becomes available.

Time: March 4, 2024, 8:40 p.m.

Status: Investigating

Update: We have discovered a service disruption that is affecting the Istanbul (IST) PoP, which may result in customers experiencing a loss of connectivity, intermittent packet loss and/or higher than expected latency to services. Investigation into the cause of the service disruption is currently ongoing. Further updates will be provided as information becomes available.

Time: March 4, 2024, 6:10 p.m.

Status: Resolved

Update: The Advanced Bot Protection dashboard has remained stable and functioning normally. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.

Time: March 4, 2024, 5:34 p.m.

Status: Monitoring

Update: We have completed completed the implementation of remedial measures, and Advanced Bot Protection dashboard has returned to normal service levels. We are continuing to monitor in order to ensure the continued stability of the service. Further updates will be provided as information becomes available.

Time: March 4, 2024, 5:28 p.m.

Status: Identified

Update: We have identified the source of the degradation, affecting the Advanced Bot Protection dashboard, and are working on remedial measures to mitigate the impact to customers at this time. Further updates will be provided as information becomes available.

Time: March 4, 2024, 5:16 p.m.

Status: Investigating

Update: We have discovered a potential service degradation affecting Advance Bot Protection dashboard, which may result in some customers experiencing latency when attempting to access the ABP dashboard. Customer sites are still fully protected by Advanced Bot Protection. Investigation into the cause of the service disruption is currently ongoing. Further updates will be provided as information becomes available.

Time: March 4, 2024, 6:10 p.m.

Status: Resolved

Update: The Advanced Bot Protection dashboard has remained stable and functioning normally. At this time this incident is being considered resolved. We apologize for any inconvenience this issue may have caused.

Time: March 4, 2024, 5:34 p.m.

Status: Monitoring

Update: We have completed completed the implementation of remedial measures, and Advanced Bot Protection dashboard has returned to normal service levels. We are continuing to monitor in order to ensure the continued stability of the service. Further updates will be provided as information becomes available.

Time: March 4, 2024, 5:28 p.m.

Status: Identified

Update: We have identified the source of the degradation, affecting the Advanced Bot Protection dashboard, and are working on remedial measures to mitigate the impact to customers at this time. Further updates will be provided as information becomes available.

Time: March 4, 2024, 5:16 p.m.

Status: Investigating

Update: We have discovered a potential service degradation affecting Advance Bot Protection dashboard, which may result in some customers experiencing latency when attempting to access the ABP dashboard. Customer sites are still fully protected by Advanced Bot Protection. Investigation into the cause of the service disruption is currently ongoing. Further updates will be provided as information becomes available.