Incapsula Outage History

Incapsula is up right now

Incapsula had 85 outages in the last 2 years totaling 332h 28m of downtime — averaging 3.5 incidents per month.

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

Source: https://status.incapsula.com

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 →

Major June 3, 2026

[INC-1062] Sao Paulo 2 Data Center Issue

Detected by Pingoru
Jun 03, 2026, 01:29 PM UTC
Resolved
Jun 03, 2026, 02:55 PM UTC
Duration
1h 25m
Affected: Sao Paulo, Brazil (SAO)
Timeline · 4 updates
  1. identified Jun 03, 2026, 01:29 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. Next update will be shared 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.

  2. investigating Jun 03, 2026, 01:59 PM UTC

    Technical teams are continuing to working on a fix for the data center issue. 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 will be shared no later than 14: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.

  3. monitoring Jun 03, 2026, 02:25 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. Next update will be shared no later than 14:56 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. resolved Jun 03, 2026, 02:55 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 June 3, 2026

[INC-1059] Latency Issue on the Management Console

Detected by Pingoru
Jun 03, 2026, 08:36 AM UTC
Resolved
Jun 03, 2026, 09:40 AM UTC
Duration
1h 4m
Affected: Cloud Security Management PlatformWeb Application Performance
Timeline · 4 updates
  1. investigating Jun 03, 2026, 08:36 AM UTC

    We are currently investigating an issue causing slowness on the Management Platform and Customers accessing onboarded sites from the APAC region may experience intermittent latency or delays when reaching their protected websites. Our teams are actively investigating the cause and working to restore normal service performance. We will provide additional updates as more information becomes available. Next update will be shared no later then 09:00 UTC.

  2. identified Jun 03, 2026, 08:59 AM UTC

    We have identified the source of the service degradation causing slowness on the Management Platform and customers accessing onboarded sites from the APAC region. Customer domains are still fully protected at this time. Technical teams are investigating. Next update will be shared no later then 09:30 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. monitoring Jun 03, 2026, 09:11 AM UTC

    Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. Technical teams will continue monitoring the system. Next update will be shared no later than 09:42 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. resolved Jun 03, 2026, 09:40 AM UTC

    The incident has been resolved and normal service levels have been restored for the 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 →

Minor May 28, 2026

[INC-1054] Connectivity issue in VAN POP.

Detected by Pingoru
May 28, 2026, 07:08 PM UTC
Resolved
May 29, 2026, 11:05 AM UTC
Duration
15h 57m
Affected: Vancouver, Canada (VAN)
Timeline · 7 updates
  1. identified May 28, 2026, 07:08 PM UTC

    We have identified connectivity issues affecting our Vancouver, Canada (VAN) data center. The next update will be provided no later than 19:38 UTC.

  2. identified May 28, 2026, 07:24 PM UTC

    We have identified connectivity issues in our Vancouver, Canada (VAN) data center. Traffic is being re-routed to an alternate data center. The next update will be provided no later than 19:54 UTC.

  3. identified May 28, 2026, 07:54 PM UTC

    We have identified intermittent connectivity issues affecting the Vancouver, Canada (VAN) data center. Our Network Engineering team is actively working on remediation efforts. In the meantime, network traffic has been redirected to an alternate regional data center. The next update will be provided no later than 20:24 UTC.

  4. identified May 28, 2026, 08:44 PM UTC

    As a precautionary measure, the Vancouver, Canada (VAN) data center will remain bypassed. Customer traffic continues to be served normally through an alternate PoP, and no customer action is required at this time. Engineering teams will continue investigating the issue, and additional updates will be provided as changes occur or once the PoP is restored to normal operation.

  5. identified May 28, 2026, 09:55 PM UTC

    The technical teams have identified an issue affecting the Vancouver, Canada (VAN) data center. As a precautionary measure, the PoP will remain bypassed to ensure service stability and is planned to be reactivated during off-peak hours. Customer traffic continues to be served normally through an alternate PoP. Engineering teams remain engaged in the investigation, and further updates will be shared as new information becomes available or once the PoP has been restored to normal operation.

  6. monitoring May 29, 2026, 10:18 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 next update will be provided no later than 11:18 UTC.

  7. resolved May 29, 2026, 11:05 AM UTC

    Service in the data center has been restored to normal.

Read the full incident report →

Minor May 27, 2026

[INC-1051] Imperva Management Portal ABP Dashboard Issue

Detected by Pingoru
May 27, 2026, 07:22 PM UTC
Resolved
May 27, 2026, 10:52 PM UTC
Duration
3h 29m
Affected: ABP ManagementAdvanced BOT Protection
Timeline · 5 updates
  1. investigating May 27, 2026, 07:22 PM UTC

    We have discovered a potential service degradation, affecting some ABP dashboards. Customer sites are still fully protected by Advanced Bot Protection at this time. Technical teams are investigating. Further updates to follow. Next update will be shared no later then 19:52 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.

  2. investigating May 27, 2026, 08:04 PM UTC

    Investigation and remediation activities are currently in progress, with engineering teams actively working to identify the root cause and restore service stability. Next update will be shared no later then 20:33 UTC.

  3. monitoring May 27, 2026, 08:47 PM UTC

    Technical teams have implemented mitigation measures and the ABP dashboards are now operating normally. Teams will continue to closely monitor the environment, and further updates will be shared as they become available.

  4. monitoring May 27, 2026, 10:23 PM UTC

    The technical team remains in the monitoring phase to ensure service stability and confirm that the issue does not recur. The next update will be shared no later then 22:53 UTC.

  5. resolved May 27, 2026, 10:52 PM UTC

    No abnormalities were observed during the monitoring period. The incident has been resolved, and normal service levels have been fully restored for the Imperva Advanced Bot Protection service.

Read the full incident report →

Major May 22, 2026

[INC-1049] Issue with creation of the site certificates.

Detected by Pingoru
May 22, 2026, 10:56 PM UTC
Resolved
May 22, 2026, 11:59 PM UTC
Duration
1h 3m
Affected: Cloud Security Management Platform
Timeline · 4 updates
  1. investigating May 22, 2026, 10:56 PM UTC

    We have discovered a potential issue affecting sites certificates validation. Technical teams are investigating. The next update will be shared no later then 23:25 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 May 22, 2026, 11:39 PM UTC

    Remediation efforts are ongoing and teams are actively working to stabilize the services. The next update will be communicated at 00:10 UTC.

  3. identified May 22, 2026, 11:53 PM UTC

    Investigation has identified a potential contributing factor to the issue. The team is continuing to analyze and validate this finding to better understand its impact on service performance.

  4. resolved May 22, 2026, 11:59 PM UTC

    A fix has been implemented and all services are operating normally. The incident has been successfully resolved,

Read the full incident report →

Notice May 15, 2026

Imperva Management Portal Slowness Issue

Detected by Pingoru
May 15, 2026, 07:16 PM UTC
Resolved
May 15, 2026, 07:14 PM UTC
Duration
Timeline · 1 update
  1. resolved May 15, 2026, 07:16 PM UTC

    We have discovered a potential service degradation, affecting customers ability to use the Imperva Management Portal. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 19:44UTC. 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.

Read the full incident report →

Minor May 15, 2026

[INC-1038] Imperva Management Portal UI Performance Degradation

Detected by Pingoru
May 15, 2026, 08:17 AM UTC
Resolved
May 15, 2026, 11:42 AM UTC
Duration
3h 24m
Affected: Account and User Management
Timeline · 5 updates
  1. investigating May 15, 2026, 08:17 AM UTC

    We have discovered a potential service degradation, affecting Imperva Management Portal. The Management Portal website is slow to respond to user actions and in some cases user login attempts may also fail. All customer websites remain 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 May 15, 2026, 08:53 AM UTC

    The impact has been identified as isolated to the India region. Technical teams are actively investigating the issue and working towards mitigation. The next update on the incident will be shared no later that 09:22 UTC

  3. investigating May 15, 2026, 09:21 AM UTC

    Technical teams are continuing to actively troubleshoot the issue and are working to restore normal service levels. The next update on the incident will be shared no later that 09:50 UTC

  4. monitoring May 15, 2026, 09:52 AM UTC

    The issue has been identified as ISP-related. Technical teams have taken mitigation actions, and we are observing improvements in service performance. Monitoring will continue to ensure stability.

  5. resolved May 15, 2026, 11:42 AM UTC

    The incident has been resolved and normal service levels have been restored for the Imperva Management Portal.

Read the full incident report →

Minor May 14, 2026

[INC-1036] Imperva Management Portal Slowness Issue

Detected by Pingoru
May 14, 2026, 05:26 PM UTC
Resolved
May 14, 2026, 06:28 PM UTC
Duration
1h 1m
Affected: Cloud Security Management Platform
Timeline · 3 updates
  1. investigating May 14, 2026, 05:26 PM UTC

    We have discovered a potential service degradation, affecting customers ability to use the Imperva Management Portal. Technical teams are investigating. The next Status Update on this Incident will be provided no later than 17:56 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.

  2. monitoring May 14, 2026, 05:58 PM UTC

    Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. 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.

  3. resolved May 14, 2026, 06:28 PM UTC

    The incident has been resolved and normal service levels have been restored for 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 →

Notice May 13, 2026

[INC-1035] Buenos Aires, Argentina (EZE) Data Center Issue

Detected by Pingoru
May 13, 2026, 01:57 AM UTC
Resolved
May 13, 2026, 01:57 AM UTC
Duration
Affected: Buenos Aires, Argentina (EZE)
Timeline · 1 update
  1. resolved May 13, 2026, 01:57 AM UTC

    We have discovered a service degradation that affected the EZE PoP which may have resulted in customers experiencing impact for Imperva Cloud WAF and DDoS for Networks traffic routed through the EZE PoP. Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts. Services has been restored for EZE PoP.

Read the full incident report →

Major May 12, 2026

[INC-1034] Imperva Management Portal Login Issue

Detected by Pingoru
May 12, 2026, 10:56 AM UTC
Resolved
May 12, 2026, 12:15 PM UTC
Duration
1h 18m
Affected: Cloud Security Management Platform
Timeline · 3 updates
  1. investigating May 12, 2026, 10:56 AM 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. 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 May 12, 2026, 11:23 AM UTC

    Technical teams have performed remedial actions and the Imperva Management Portal is returning to normal service levels. 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.

  3. resolved May 12, 2026, 12:15 PM UTC

    The incident has been resolved and normal service levels have been restored for 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 →

Notice May 12, 2026

[INC-1033] Retroactive: Vancouver, Canada (VAN) Data Center - Connectivity Issues

Detected by Pingoru
May 12, 2026, 07:49 AM UTC
Resolved
May 12, 2026, 07:49 AM UTC
Duration
Affected: Vancouver, Canada (VAN)
Timeline · 1 update
  1. resolved May 12, 2026, 07:49 AM UTC

    We have identified ISP-related connectivity issues in the Vancouver region which affected traffic at 07:03 UTC - 07:21 UTC that may have impacted Imperva Cloud WAF and DDoS for Networks traffic routed through the VAN PoP. Customers with affected traffic may have observed Cloud WAF Error Code 20 responses and/or TCP timeouts.

Read the full incident report →

Minor May 11, 2026

[INC-1031] Imperva Management Portal Cloud WAF Security Dashboard Degradation

Detected by Pingoru
May 11, 2026, 06:32 AM UTC
Resolved
May 11, 2026, 08:33 AM UTC
Duration
2h 1m
Affected: Cloud Security Management Platform
Timeline · 5 updates
  1. investigating May 11, 2026, 06:32 AM UTC

    We have discovered a potential service degradation, affecting the Imperva Management Portal. One or more Cloud WAF Dashboards are not responding or returning errors. 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 May 11, 2026, 06:56 AM UTC

    We have narrowed the issue down to the “WAF Sessions by Country” component in the Security dashboard, which is not functioning as expected. The technical teams are actively working on a fix. The next Status Update on this Incident will be provided no later than 07:26 UTC.

  3. investigating May 11, 2026, 07:22 AM UTC

    Our technical teams are actively working to resolve the issue and will share updates as progress is made. The next Status Update on this Incident will be provided no later than 07:52 UTC.

  4. monitoring May 11, 2026, 07:26 AM UTC

    A fix has been implemented for the issue impacting the Cloud WAF Dashboards component. The issue has been mitigated, and the team is actively monitoring to ensure continued stability.

  5. resolved May 11, 2026, 08:33 AM UTC

    The issue affecting the Cloud WAF Dashboards component has been resolved. All systems are operating normally.

Read the full incident report →