F5 Outage History

F5 is up right now

F5 had 77 outages in the last 2 years totaling 463h 26m of downtime — averaging 3.2 incidents per month.

There were 77 F5 outages since August 27, 2025 totaling 463h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.f5cloudstatus.com

Minor July 1, 2026

F5 Distributed Cloud - Service Degradation - Global Log Receiver (GLR) - INC-20260701-480

Detected by Pingoru
Jul 01, 2026, 09:03 PM UTC
Resolved
Jul 02, 2026, 01:03 PM UTC
Duration
16h
Affected: Global Log Receiver (GLR)
Timeline · 4 updates
  1. investigating Jul 01, 2026, 09:03 PM UTC

    The F5 Distributed Cloud is currently investigating a degradation affecting Global Log Receiver (GLR) in the EU region. Our engineering teams are actively working to identify the root cause. We are closely monitoring the environment to ensure continued platform stability and will provide additional updates as more information becomes available. Please note that there is no traffic interruption and all core Distributed Cloud Console services remain fully operational. We will share further updates as more information becomes available. We appreciate your patience and understanding.

  2. monitoring Jul 01, 2026, 10:58 PM UTC

    The issue has been identified and EU GLR log processing lag has been restored to normal levels. Our engineering teams are continuing to monitor closely to ensure the service returns to and remains at normal operating levels. We will provide additional updates as needed

  3. monitoring Jul 02, 2026, 10:07 AM UTC

    The F5 Distributed Cloud team has identified and mitigated the issue that was impacting Global Logs Receiver. Please note that all other Distributed Cloud Console services remain fully operational We will continue to monitor the platform to ensure ongoing service stability. If you have any questions or concerns, please contact us at [email protected].

  4. resolved Jul 02, 2026, 01:03 PM UTC

    The F5 Distributed Cloud team has successfully resolved the issue affecting GLR log streaming in the Distributed Cloud console. Live log visibility has now been restored. The system is currently operating normally, and no further impact is expected. We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues or have further questions, please don't hesitate to reach out to our support team.

Read the full incident report →

Minor June 9, 2026

F5 Distributed Cloud - Service Degradation - Delay in GLR logs - INC-20260609-470

Detected by Pingoru
Jun 09, 2026, 11:52 AM UTC
Resolved
Jun 10, 2026, 07:20 PM UTC
Duration
1d 7h
Affected: Global Log Receiver (GLR)
Timeline · 4 updates
  1. identified Jun 09, 2026, 11:52 AM UTC

    F5 Distributed Cloud customers may experience a delay in GLR log streaming. Our teams are actively investigating the Global Log Receiver functionality. Please note that there is no traffic interruption and all core XC Console services remain fully operational. We will share further updates as more information becomes available. We appreciate your patience and understanding.

  2. identified Jun 09, 2026, 04:01 PM UTC

    F5 Distributed Cloud customers may experience a delay in GLR log streaming. Our teams have identified the issue and are actively working to recover the service and restore normal log delivery as soon as possible. Please note that there is no traffic interruption, and all core XC Console services remain fully operational. We will continue to provide updates as recovery efforts progress and more information becomes available. We appreciate your patience and understanding.

  3. monitoring Jun 10, 2026, 07:15 AM UTC

    The F5 Distributed Cloud team has confirmed that Global Log Receiver processing has fully recovered and returned to normal operations. Both live logs and backfill logs are now being generated and accessible within the XC Console. This ensures users can effectively access and audit activities as needed. As previously communicated, all XC Console core services remained fully functional throughout the duration of this event. This maintained the reliability and integrity of the platform in a steady state. To further reinforce stability, proactive monitoring will continue to ensure Global Log Receiver services operate as usual. If any issues arise, users are encouraged to contact the F5 support team for assistance. We sincerely appreciate your continued trust in F5.

  4. resolved Jun 10, 2026, 07:20 PM UTC

    The issue affecting the F5 Distributed Cloud Global Log Receiver has been resolved. All XC Console core services remains fully operational, and the incident is now closed. Please contact support if you continue to experience any issues.

Read the full incident report →

Notice June 6, 2026

F5 Bot Defense - Service Degradation - Shared Rate Limiter - INC-20260606-469

Detected by Pingoru
Jun 06, 2026, 09:20 PM UTC
Resolved
Jun 07, 2026, 06:01 PM UTC
Duration
20h 41m
Affected: DCPM (WorldWide)
Timeline · 2 updates
  1. monitoring Jun 06, 2026, 09:20 PM UTC

    Following a scheduled maintenance window on June 6th 2026 at 14:00 UTC, we identified a performance degradation caused by false positives in rate-limiting policies. Our teams were immediately engaged, and corrective actions were taken to resolve the issue. The incident was resolved at 18:00 UTC and all systems are now operating normally. We sincerely apologize for any inconvenience caused and appreciate your patience as we worked to resolve the issue.

  2. resolved Jun 07, 2026, 06:01 PM UTC

    The F5 Distributed Cloud team has successfully resolved the issue that was causing the false positives in rate-limiting policies. Services are now functioning as expected, and we will continue to monitor to ensure ongoing stability. If you have any questions or continue to experience issues, please reach out to our support team through your established channels. This incident is now considered resolved. We appreciate your patience and understanding while we worked to restore service.

Read the full incident report →