Radware Cloud WAF incident

Radware Cloud WAF Portal - Incident Notification

Notice Resolved View vendor source →

Radware Cloud WAF experienced a notice incident on October 20, 2025 affecting Global Cloud (Portal), lasting 23h 10m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 08:16 AM UTC
Resolved
Oct 21, 2025, 07:27 AM UTC
Duration
23h 10m
Detected by Pingoru
Oct 20, 2025, 08:16 AM UTC

Affected components

Global Cloud (Portal)

Update timeline

  1. investigating Oct 20, 2025, 08:16 AM UTC

    Radware is investigating an issue with the Cloud WAF Portal. Impact: Cloud WAF Portal intermittent availability. No impact on traffic - protection is fully active. Radware is working to restore service as soon as possible and apologies for any inconvenience that may cause. For additional questions please contact us via the support portal at https://support.radware.com/

  2. identified Oct 20, 2025, 09:02 AM UTC

    Dear Customers, Radware has identified that the issue affecting the Cloud WAF Portal is due to a third-party service outage. As a result, self-service functions are temporarily unavailable. Impact: Unavailability of Cloud WAF Portal functionalities. No impact on protected traffic. Our teams are actively working with the third-party provider to restore full service as soon as possible. We will continue to share updates on our progress until the issue is fully resolved. We apologize for any inconvenience this may cause.

  3. monitoring Oct 20, 2025, 01:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Oct 20, 2025, 01:40 PM UTC

    We are continuing to monitor for any further issues.

  5. identified Oct 20, 2025, 04:13 PM UTC

    Radware is investigating an issue with the Cloud WAF Portal. Access Log visibility and API Analytics for Cloud WAF may be temporarily unavailable. Monitoring data for the CWAF application’s origin may not appear in the Unified Portal. There is no impact on traffic or protection — all security functions remain fully active. This is due to an ongoing partial outage with a third-party service provider. Radware is closely monitoring the situation and working to restore full service as quickly as possible. We apologize for any inconvenience this may cause. For further assistance, please contact us via the Radware Support Portal: https://support.radware.com/

  6. identified Oct 20, 2025, 05:05 PM UTC

    Radware is currently experiencing a partial service disruption due to an ongoing third-party AWS outage that is impacting multiple service providers. The following features may be affected: Access Log visibility and API Analytics are temporarily unavailable. Server-down notifications are not currently functioning due to a temporary impact on monitoring. Self-service features, including onboarding and configuration changes, remain fully operational. Our teams are closely monitoring the situation and coordinating with the third-party provider to restore full functionality as soon as possible. We appreciate your patience and understanding.

  7. identified Oct 20, 2025, 09:21 PM UTC

    Radware is seeing many services start to restore after a partial service disruption due to an ongoing third-party AWS outage that is impacting multiple service providers. The following features may still be affected, but are starting to show improvement: Access Log visibility and API Analytics are temporarily unavailable. Server-down notifications are not currently functioning due to a temporary impact on monitoring. Self-service features, including onboarding and configuration changes, remain fully operational. Our teams are closely monitoring the situation and coordinating with the third-party provider to restore full functionality as soon as possible. We appreciate your patience and understanding.

  8. monitoring Oct 20, 2025, 11:56 PM UTC

    Our 3rd party provider AWS, has implemented a fix and we are monitoring the result. At this time this issue is considered cleared.

  9. monitoring Oct 21, 2025, 07:26 AM UTC

    We are continuing to monitor for any further issues.

  10. resolved Oct 21, 2025, 07:27 AM UTC

    This incident has been resolved.