Radware Cloud WAF incident

Radware Cloud WAF Asia Pacific (Hong Kong) Incident Notification

Radware Cloud WAF is currently experiencing a minor incident affecting Asia Pacific (Singapore) and Asia Pacific (Tokyo-2) and 1 more component, which began 15h ago. The vendor's full update timeline is below.

Started
May 30, 2026, 07:34 AM UTC
Resolved
Ongoing
Duration
● 14h 37m
Detected by Pingoru
May 30, 2026, 07:34 AM UTC

Affected components

Asia Pacific (Singapore)Asia Pacific (Tokyo-2)Asia Pacific (Hong Kong-2)Asia Pacific (Taipei)

Update timeline

  1. investigating May 30, 2026, 07:34 AM UTC

    Radware is investigating an issue with the Cloud WAF Asia Pacific (Hong Kong) infrastructure. Impact: Cloud WAF self-service and on-boarding of new applications are intermittently unavailable. No impact on traffic - routing and protection are 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. investigating May 30, 2026, 08:06 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 30, 2026, 09:03 AM UTC

    Radware is currently investigating an issue affecting the Cloud WAF Asia Pacific (Hong Kong) infrastructure. Impact: Cloud WAF Self-Service and onboarding of new applications may be intermittently unavailable. While traffic routing and protection services remain active, some customers may experience traffic-related issues. Radware is actively working to restore full service as quickly as possible and apologizes for any inconvenience this may cause. If you experience any service degradation or traffic-related issues, please contact Radware Support immediately and open a Priority 1 (P1) support case for prompt assistance. For additional questions, please contact us via the support portal at https://support.radware.com/.

  4. identified May 30, 2026, 10:08 AM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring May 30, 2026, 10:11 AM UTC

    The issue has been identified within the data center in HKG. As a mitigation measure, traffic was diverted from HKG to the redundant PoP.