Radware Cloud WAF Outage History

Radware Cloud WAF is up right now

Radware Cloud WAF had 24 outages in the last 2 years totaling 374h 18m of downtime — averaging 1 incident per month.

There were 24 Radware Cloud WAF outages since July 23, 2025 totaling 374h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://cwaf.status.radwarecloud.com

Minor June 16, 2026

Radware Cloud WAF Incident Notification

Detected by Pingoru
Jun 16, 2026, 07:48 PM UTC
Resolved
Jun 16, 2026, 08:28 PM UTC
Duration
40m
Affected: North America (Ashburn)North America – Dallas (Ashburn)
Timeline · 3 updates
  1. investigating Jun 16, 2026, 07:48 PM UTC

    Radware Cloud WAF service is currently experiencing an issue in the below PoPs: Dallas Ashburn 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. monitoring Jun 16, 2026, 08:19 PM UTC

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

  3. resolved Jun 16, 2026, 08:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 10, 2026

Radware Cloud WAF Incident Notification - South America (Santiago)

Detected by Pingoru
Jun 10, 2026, 08:40 AM UTC
Resolved
Jun 10, 2026, 10:41 AM UTC
Duration
2h
Affected: South America (Santiago)
Timeline · 4 updates
  1. investigating Jun 10, 2026, 07:38 AM UTC

    Radware Cloud WAF service is currently experiencing a service impact event in South America (Santiago) that might affect the region shown below: South America (Santiago) 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 Jun 10, 2026, 10:39 AM UTC

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

  3. monitoring Jun 10, 2026, 10:40 AM UTC

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

  4. resolved Jun 10, 2026, 10:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 1, 2026

Radware Cloud WAF Incident Notification - Ashburn

Detected by Pingoru
Jun 01, 2026, 04:54 PM UTC
Resolved
Jun 01, 2026, 06:51 PM UTC
Duration
1h 56m
Affected: North America (Ashburn)
Timeline · 4 updates
  1. investigating Jun 01, 2026, 04:54 PM UTC

    Radware Cloud WAF service is currently experienced a brief service impact event that might affect the region(s) shown below. ASHBURN CWAAP Radware is working to investigate, and apologizes for any inconvenience that may cause. For additional questions please contact us via the support portal at https://support.radware.com/

  2. identified Jun 01, 2026, 05:05 PM UTC

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

  3. monitoring Jun 01, 2026, 05:07 PM UTC

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

  4. resolved Jun 01, 2026, 06:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 1, 2026

Incident Notification in Radware Cloud Unified Portal

Detected by Pingoru
Jun 01, 2026, 08:47 AM UTC
Resolved
Jun 01, 2026, 09:26 AM UTC
Duration
38m
Affected: Global Cloud (Portal)
Timeline · 3 updates
  1. investigating Jun 01, 2026, 08:47 AM UTC

    Radware is investigating an issue with the Cloud Unified Portal. Impact: Cloud Unified Portal intermittent availability and actions might be taken longer. 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. monitoring Jun 01, 2026, 09:05 AM UTC

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

  3. resolved Jun 01, 2026, 09:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 30, 2026

Radware Cloud WAF Asia Pacific (Hong Kong) Incident Notification

Detected by Pingoru
May 30, 2026, 07:34 AM UTC
Resolved
May 31, 2026, 04:35 PM UTC
Duration
1d 9h
Affected: Asia Pacific (Singapore)Asia Pacific (Tokyo-2)Asia Pacific (Hong Kong-2)Asia Pacific (Taipei)
Timeline · 6 updates
  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.

  6. resolved May 31, 2026, 04:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

Radware Cloud WAF Portal - Incident Notification

Detected by Pingoru
May 20, 2026, 12:50 PM UTC
Resolved
May 20, 2026, 01:10 PM UTC
Duration
20m
Affected: Global Cloud (Portal)
Timeline · 4 updates
  1. investigating May 20, 2026, 12:42 PM UTC

    Radware is investigating a visibility issue with the Cloud WAF Portal. Impact: Cloud WAF Portal is experiencing a visibility issue. Certain sections of the Unified Portal such as Origin Server Status, Access Control, and others are not loading or displaying properly. 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 May 20, 2026, 12:57 PM UTC

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

  3. monitoring May 20, 2026, 12:57 PM UTC

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

  4. resolved May 20, 2026, 01:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 14, 2026

Radware Cloud WAF Portal - Self-Service Portal Issue Affecting MAA and BOM Applications

Detected by Pingoru
May 14, 2026, 10:15 AM UTC
Resolved
May 14, 2026, 10:40 AM UTC
Duration
24m
Affected: Global Cloud (Portal)
Timeline · 4 updates
  1. investigating May 14, 2026, 07:36 AM UTC

    Radware is currently investigating a self-service issue affecting applications utilizing MAA and BOM. Impact: Intermittent availability and accessibility issues within the self-service portal applications. No impact on customer traffic or protection services — mitigation and security services remain fully operational. Radware is actively working to restore full service functiona 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 May 14, 2026, 09:57 AM UTC

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

  3. monitoring May 14, 2026, 10:46 AM UTC

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

  4. resolved May 14, 2026, 10:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 12, 2026

Radware Cloud WAF Incident Notification - TAIPEI

Detected by Pingoru
May 12, 2026, 06:24 PM UTC
Resolved
May 13, 2026, 07:02 PM UTC
Duration
1d
Affected: Asia Pacific (Taipei)
Timeline · 5 updates
  1. investigating May 12, 2026, 06:24 PM UTC

    Radware Cloud WAF service is currently experiencing a service impact event in the region(s) shown below. TAIPEI (TPE) 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 May 12, 2026, 06:34 PM UTC

    Radware is investigating this issue, issue appears related only to managment and not to any data path. No service impact to customers has been detected.

  3. investigating May 12, 2026, 06:50 PM UTC

    Radware continues to investigate potential outage condition on Taipei CWAF PoP.

  4. monitoring May 12, 2026, 07:10 PM UTC

    Radware is seeing all devices inside the TPE PoP accessible and responding again at this time.

  5. resolved May 13, 2026, 07:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Radware Cloud WAF Middle East (Tel Aviv-5) Incident Notification

Detected by Pingoru
May 04, 2026, 08:24 PM UTC
Resolved
May 05, 2026, 03:33 PM UTC
Duration
19h 9m
Affected: Middle East (Tel Aviv-5)
Timeline · 4 updates
  1. investigating May 04, 2026, 08:24 PM UTC

    Radware is investigating an issue with a core device on the Middle East (Tel Aviv-5) pop shown below. Customers may observe non-service impacting global routing changes to the traffic of their applications. For additional questions please contact us via the support portal at https://support.radware.com/

  2. identified May 05, 2026, 02:51 AM UTC

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

  3. monitoring May 05, 2026, 02:58 PM UTC

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

  4. resolved May 05, 2026, 03:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

Radware Cloud WAF Incident Notification Asia Pacific (Hong Kong)

Detected by Pingoru
Apr 30, 2026, 08:51 AM UTC
Resolved
Apr 30, 2026, 01:30 PM UTC
Duration
4h 39m
Affected: Asia Pacific (Hong Kong)
Timeline · 4 updates
  1. investigating Apr 30, 2026, 08:51 AM UTC

    Radware Cloud WAF service in Asia Pacific (Hong Kong) is currently experiencing a service impact event. Radware is working with the service provider 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 Apr 30, 2026, 11:01 AM UTC

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

  3. monitoring Apr 30, 2026, 11:39 AM UTC

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

  4. resolved May 03, 2026, 05:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 23, 2026

Radware Cloud WAAP Incident Notification

Detected by Pingoru
Feb 23, 2026, 08:08 PM UTC
Resolved
Feb 24, 2026, 04:00 AM UTC
Duration
7h 52m
Affected: Europe (Amsterdam)Europe – Frankfurt (Amsterdam)
Timeline · 3 updates
  1. investigating Feb 23, 2026, 08:08 PM UTC

    Radware Cloud WAF service experienced a service impact event. Between 18:50-1900 UTC Cloud WAAP a subset of applications in the below region may have experienced high latency or degredation. Frankfurt/Amsterdam Radware is investigating the interruption and apologized for any inconvenience that may cause. For additional questions please contact us via the support portal at https://support.radware.com/

  2. monitoring Feb 23, 2026, 09:56 PM UTC

    This issue is currently under monitoring. No further impact is anticipated.

  3. resolved Feb 24, 2026, 04:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 4, 2026

Radware API for Unified Portal - Incident Notification

Detected by Pingoru
Feb 04, 2026, 04:43 PM UTC
Resolved
Feb 04, 2026, 05:16 PM UTC
Duration
33m
Affected: Global Cloud (Portal)
Timeline · 3 updates
  1. investigating Feb 04, 2026, 04:43 PM UTC

    Radware API for Unified Portal is currently unavailable. Radware is working to restore this functionality as soon as possible. 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 Feb 04, 2026, 05:08 PM UTC

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

  3. resolved Feb 04, 2026, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 4, 2026

Radware Cloud CSMS Portal - Incident Notification

Detected by Pingoru
Feb 04, 2026, 01:12 PM UTC
Resolved
Feb 04, 2026, 02:09 PM UTC
Duration
57m
Affected: Global Cloud (Portal)
Timeline · 4 updates
  1. investigating Feb 04, 2026, 01:12 PM UTC

    Radware is investigating an issue with the Cloud CSMS Portal. Impact: Cloud CSMS 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 Feb 04, 2026, 01:28 PM UTC

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

  3. monitoring Feb 04, 2026, 01:53 PM UTC

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

  4. resolved Feb 04, 2026, 02:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 16, 2026

Radware Cloud WAF/Unified Portal - Incident Notification

Detected by Pingoru
Jan 16, 2026, 03:41 PM UTC
Resolved
Jan 16, 2026, 05:26 PM UTC
Duration
1h 44m
Affected: Global Cloud (Portal)
Timeline · 7 updates
  1. investigating Jan 16, 2026, 03:41 PM UTC

    Radware is investigating an issue with the Cloud WAF Portal. Impact: Cloud WAF/Unified 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. investigating Jan 16, 2026, 03:58 PM UTC

    We are continuing to investigate this issue. Please note that the Unified Portal is currently impacted, and not accessible. For any urgent requests please open a support case or contact Radware for immediate support.

  3. identified Jan 16, 2026, 04:16 PM UTC

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

  4. monitoring Jan 16, 2026, 04:21 PM UTC

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

  5. monitoring Jan 16, 2026, 04:21 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Jan 16, 2026, 05:25 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jan 16, 2026, 05:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 14, 2026

Radware Cloud WAF South Africa (Kenya) Incident Notification

Detected by Pingoru
Jan 14, 2026, 10:20 AM UTC
Resolved
Jan 14, 2026, 11:30 AM UTC
Duration
1h 9m
Affected: South Africa (Kenya)
Timeline · 3 updates
  1. investigating Jan 14, 2026, 10:20 AM UTC

    Radware is scheduling a planned activity on the South Africa (Kenya) Cloud WAF infrastructure. Impact: The South Africa (Kenya) CWAF pop may not be visible in the portal under "Origin Server Status". No impact on traffic - protection is fully active. For additional questions please contact us via the support portal at https://support.radware.com/

  2. monitoring Jan 14, 2026, 10:45 AM UTC

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

  3. resolved Jan 14, 2026, 11:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 30, 2025

Radware Cloud WAF Middle East (Tel Aviv-4) Incident Notification

Detected by Pingoru
Dec 30, 2025, 12:49 PM UTC
Resolved
Dec 30, 2025, 02:10 PM UTC
Duration
1h 21m
Affected: Middle East (Tel Aviv-4)
Timeline · 2 updates
  1. investigating Dec 30, 2025, 12:49 PM UTC

    Radware Cloud WAF service is currently experiencing a service impact event in the Middle East (Tel Aviv-4). Radware is working with the service provider 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. resolved Dec 30, 2025, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 22, 2025

Radware Cloud WAF Europe – Frankfurt (Amsterdam) Incident Notification

Detected by Pingoru
Dec 22, 2025, 06:19 AM UTC
Resolved
Dec 30, 2025, 12:38 PM UTC
Duration
8d 6h
Affected: Europe – Frankfurt (Amsterdam)
Timeline · 6 updates
  1. investigating Dec 22, 2025, 06:19 AM UTC

    Radware Cloud WAF service is currently experiencing a service impact event in the Europe – Frankfurt (Amsterdam) that might affect the regions shown below. 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 Dec 22, 2025, 09:00 AM UTC

    We are continuing to investigate this issue.

  3. identified Dec 22, 2025, 10:11 AM UTC

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

  4. identified Dec 22, 2025, 12:23 PM UTC

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

  5. monitoring Dec 22, 2025, 01:02 PM UTC

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

  6. resolved Dec 30, 2025, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 17, 2025

Radware Cloud BotM - Incident Notification

Detected by Pingoru
Dec 17, 2025, 02:59 AM UTC
Resolved
Dec 17, 2025, 06:42 PM UTC
Duration
15h 42m
Affected: BotManager
Timeline · 4 updates
  1. identified Dec 17, 2025, 02:59 AM UTC

    Radware Cloud BotM service is currently experiencing a service impact event in Policy Control feature. 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 Dec 17, 2025, 06:53 AM UTC

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

  3. monitoring Dec 17, 2025, 06:37 PM UTC

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

  4. resolved Dec 17, 2025, 06:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2025

Radware Unified Portal - Incident Notification

Detected by Pingoru
Dec 09, 2025, 11:41 PM UTC
Resolved
Dec 09, 2025, 11:54 PM UTC
Duration
13m
Affected: Global Cloud (Portal)
Timeline · 2 updates
  1. investigating Dec 09, 2025, 11:41 PM UTC

    Radware is investigating an issue with the Unifed Portal. Impact: Cloud WAF assets and events pages are not displaying data. 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. resolved Dec 09, 2025, 11:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 6, 2025

Radware Cloud WAF self service - Incident Notification

Detected by Pingoru
Dec 06, 2025, 06:41 AM UTC
Resolved
Dec 06, 2025, 10:43 AM UTC
Duration
4h 1m
Affected: Global Cloud (Portal)
Timeline · 5 updates
  1. investigating Dec 06, 2025, 06:41 AM UTC

    Radware is investigating an issue with the Cloud WAF self-service 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 Dec 06, 2025, 06:43 AM UTC

    We are continuing to investigate this issue.

  3. identified Dec 06, 2025, 09:26 AM UTC

    Radware has identified the issue and i now 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/

  4. monitoring Dec 06, 2025, 10:01 AM UTC

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

  5. resolved Dec 06, 2025, 10:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 27, 2025

Security Events Visibility Issue

Detected by Pingoru
Nov 27, 2025, 10:50 AM UTC
Resolved
Nov 28, 2025, 09:53 AM UTC
Duration
23h 2m
Affected: Asia Pacific (Chennai)Middle East (Tel Aviv)Global Cloud (Portal)BotManagerNorth America (Ashburn)Asia Pacific (Hong Kong)Europe – Frankfurt (London)Middle East (Tel Aviv-2)North America (Ashburn – Legacy)Asia Pacific (Singapore)Europe (London)Middle East (Tel Aviv-3)North America (San Jose)Asia Pacific (Sydney)South Africa (Johannesburg)North America (Chicago)Asia Pacific (Tokyo)United Arab Emirates (Dubai)North America (Toronto)Asia Pacific (Sydney-2)Middle East (Tel Aviv-4)South America (Sao Paulo)Asia Pacific (Tokyo-2)Europe (Amsterdam)South Africa (Johannesburg-2)South America (Sao Paulo – Legacy)Asia Pacific (Hong Kong-2)Europe – Frankfurt (Amsterdam)Test componentSouth Africa (Kenya)Asia Pacific (Seoul)Europe (Paris)South America (Santiago)Middle East (Tel Aviv-5)Asia Pacific (Taipei)Europe (Milan)South America (Lima)Asia Pacific (Auckland)North America – Dallas (Ashburn)Asia Pacific (Sydney - Legacy)South America (Bogota)Asia Pacific (Mumbai)Asia Pacific – Taipei (Tokyo)
Timeline · 4 updates
  1. identified Nov 27, 2025, 10:50 AM UTC

    We are investigating an issue where Security Events are not visible in the Cloud Portal. Please note: Protection remains fully operational No other services are affected. The issue has been identified and a fix is being implemented. We will share updates as they become available.

  2. identified Nov 27, 2025, 11:48 AM UTC

    We are continuing to work on the fix.

  3. monitoring Nov 27, 2025, 12:46 PM UTC

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

  4. resolved Nov 28, 2025, 09:53 AM UTC

    This incident has been solved.

Read the full incident report →

Notice November 14, 2025

Radware Cloud WAF Asia Pacific (Tokyo-2) Incident Notification

Detected by Pingoru
Nov 14, 2025, 05:48 AM UTC
Resolved
Nov 14, 2025, 07:14 AM UTC
Duration
1h 25m
Affected: Asia Pacific (Tokyo-2)
Timeline · 3 updates
  1. investigating Nov 14, 2025, 05:48 AM UTC

    Radware Cloud WAF service is currently experiencing a service impact event in the Asia Pacific (Tokyo-2) CWAF pop. Impact: customers may observe global routing changes to the traffic of their applications. 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. monitoring Nov 14, 2025, 06:30 AM UTC

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

  3. resolved Nov 14, 2025, 07:14 AM UTC

    This incident has been solved.

Read the full incident report →

Notice November 1, 2025

Radware Cloud BOTM Service – Self-Service Disruption (US Region Only)

Detected by Pingoru
Nov 01, 2025, 06:09 AM UTC
Resolved
Nov 01, 2025, 02:15 PM UTC
Duration
8h 6m
Affected: BotManager
Timeline · 4 updates
  1. investigating Nov 01, 2025, 06:09 AM UTC

    Radware currently experiencing issues with the self-service functionality of the Radware Cloud BOTM service due to a disruption from a third-party provider. This issue is limited to the US region. Impact: Actions related to BOTM may fail within the portal. No impact on traffic - protection is fully active. Our engineering team is actively working with the third-party provider to restore full service as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. For additional questions please contact us via the support portal at https://support.radware.com/

  2. investigating Nov 01, 2025, 08:35 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 01, 2025, 01:07 PM UTC

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

  4. resolved Nov 01, 2025, 02:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 17, 2025

Radware Cloud WAF Europe – Frankfurt self service - Incident Notification

Detected by Pingoru
Aug 17, 2025, 09:06 AM UTC
Resolved
Aug 18, 2025, 07:27 AM UTC
Duration
22h 21m
Affected: Europe – Frankfurt (London)Europe – Frankfurt (Amsterdam)
Timeline · 3 updates
  1. investigating Aug 17, 2025, 09:06 AM UTC

    Radware is investigating an issue with the Europe – Frankfurt Cloud WAF self-service 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. monitoring Aug 17, 2025, 10:22 AM UTC

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

  3. resolved Aug 18, 2025, 07:27 AM UTC

    This incident has been resolved.

Read the full incident report →